SP Resets on T5xx0, T3, T4, T5 and M5 Systems May Overwrite a User-Land Solaris Memory Page Causing In-Memory Corruption
(Doc ID 1580033.1)
Last updated on MARCH 25, 2019
Applies to:SPARC T5-8 - Version All Versions and later
SPARC T3-4 - Version Not Applicable and later
SPARC T5-1B - Version All Versions and later
Sun SPARC Enterprise T5240 Server - Version Not Applicable and later
Sun SPARC Enterprise T5440 Server - Version Not Applicable and later
Oracle Solaris on SPARC (64-bit)
See also Alert 1587769.1
Should the issue be encountered, some of the symptoms you may expect to find include, but are not limited to:
- Applications may fail to start and/or core dump due to 'missing symbols' in linked libraries when the corruption occurs within the in-memory copy of the library. Applications currently running will not suffer any problems.
- pkgchk(1M) may fail the checksum for a file. If the file in question resides in-memory or within the filesystem cache this potentially corrupt version will be used rather than the on-disk copy which remains in tact and un-harmed.
Running pkgchk(1M) will show an error caused by the checksum failure of a file, eg:
The Service Processor (SP) may have been manually reset by the System Administrator or reset/paniced due to a problem on the SP itself. The trigger for the described issue is an SP reset no matter what the cause.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document