Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type FAB (standard) Sure Solution 1001194.1 : Applications using large memory page sizes on UltraSPARC IV+ CPUs may hang or core dump.
PreviouslyPublishedAs 201589 Product Sun Fire E20K Server Sun Fire E6900 Server Sun Fire V490 Server Sun Fire V890 Server Sun Fire E2900 Server Sun Fire E4900 Server Sun Fire E25K Server Bug Id <SUNBUG: 6287398> <SUNBUG: 6313025> Xoption
Impact Software applications using 32M or 256M memory page sizes, running on UltraSPARC IV+ CPUs, can hang or core dump. Contributing Factors This issue can occur if all of the following are true.
This issue can be triggered by one of the following actions.
In diagnosing this issue, it helps to identify if the application has used any Multiple Page Size Support (MPSS) options during invocation, or if the application calls memcntl(2) to use large pages internally. Root Cause The UltraSPARC IV+ IMMU does not support the 32M or 256M page sizes. If the processor cannot translate a virtual address to a physical address, it takes a trap known as a tlb miss. Solaris will execute the appropriate trap handler and try to load the correct translation for that virtual address. If a tlb miss occurs on an instruction which came from a segment mapped with either of these large pages, the corresponding application will execute improperly, most likely resulting in a core dump or hang. The final resolution for this issue (CR 6287398) is now available in patch 118822-20 or higher. A partial resolution is available in patch 118822-18, which turns off USIV+ 32M and 256M page size support. Resolution If an application is core dumping on an UltraSPARC IV+ system, the following steps should be taken.
Workaround Disable 32M/256M pages by setting the following variables in the /etc/system file. You must reboot the system for the changes to take affect. set disable_large_pages = 0x30 set disable_ism_large_pages = 0x34 set mmu_ism_pagesize = 4194304
Note: If the above contributing factors are not present, this could be a different application issue. During diagnosis, it can be helpful to look at the /etc/system file on the customer's system to see if any changes were made to this file. Modification History Date: 20-SEP-2005
Date: 29-SEP-2005
Date: 27-OCT-2005
Previously Published As 101909 Internal Comments None. Internal Eng Business Unit Group KE Authors Internal Resolution Patches 118822-18 118822-20 Internal Kasp FAB Legacy ID 101909 Internal Sun Alert & FAB Admin Info Critical Category: Significant Change Date: Avoidance: Patch Responsible Manager: null Original Admin Info: null Product_uuid 1404a2d3-059a-11d8-84cb-080020a9ed93|Sun Fire E20K Server 4fe39727-0599-11d8-84cb-080020a9ed93|Sun Fire E6900 Server 5c71fc02-5e51-11d7-8add-8938754df22a|Sun Fire V490 Server 5d2816fe-5e51-11d7-8de2-d7bc0dd226fc|Sun Fire V890 Server 63ff680d-0598-11d8-84cb-080020a9ed93|Sun Fire E2900 Server bed24aa9-0598-11d8-84cb-080020a9ed93|Sun Fire E4900 Server d842dd03-059b-11d8-84cb-080020a9ed93|Sun Fire E25K Server Attachments This solution has no attachment |
||||||||||||
|