Asset ID:	1-71-1012587.1
Update Date:	2011-04-18
Keywords:

---

Solution Type  Technical Instruction Sure

Solution  1012587.1 :   A Workaround for CR 6293881 when forcing a core dump on Sun Fire[TM] V20z/V40z  


PreviouslyPublishedAs
217327

Oracle Confidential (INTERNAL). Do not distribute to customers
Reason: Migrated distribution from Sun

Description
This document outlines a simple procedure on V20z/40z
systems to allow a break sequence to be sent to the Solaris[TM]
debugger via the serial over LAN feature whilst protecting
the server against the consequences of a reboot of the Service
Processor sending a break to Solaris[TM]

Steps to Follow
A Workaround for CR 6293881 when forcing a core dump on Sun Fire[TM] V20z/V40z
    The procedure to force a dump on a hung x86 system is outlined in <Document: 1003085.1> "Forcing a kernel core dump on a Solaris[TM] 2.x x86 system" This involves booting Solaris with kadb (Solaris 9) or kmdb (Solaris 10) enabled and sending a break via the console port. If the Service Processor reboots on a Sun Fire[TM] V20z/V40z with the serial over LAN feature enabled then the serial connection is turned off and on which can be interpreted as a break signal by Solaris with kadb or kmdb enabled which will then drop the server into debug mode. This behaviour is considered normal and will not be changed. The workaround suggested by Newisys is not to use the Serial Over LAN feature and connect directly to the serial port rather than use the serial over LAN feature. The following workaround protects the server against interpreting a Service Processor reboot as a break and also preserves the ability to send a break sequence to the Solaris[TM] debugger via the Service Processor.

 1) Serial Over Lan must be enabled see <Document: 1003869.1> "How to setup platform serial console for Sun Fire[TM] V20z / Sun Fire[TM] V40z"

 2) Enable the alternate break sequence on the server. Use the command kbd -a alternate and to ensure the alternate break sequence is enabled over a reboot uncomment the line KEYBOARD_ABORT=alternate in /etc/default/kbd

3) System is booted with debugger enabled see <Document: 1003085.1>

4) The break sequence to use in the event of a hang is now ^ecl2. (instead of ^ecl1) (control-e typed together at one time, c, l, 2 which is a lowercase L followed by a "two" keystroke). Note on some older NSV/BIOS versions the break sequence is ^Exl2 control-shift-e together at one time, c, l, 2 which is a lowercase L followed by a "two" keystroke).

    The ^Exl2 sequence will work on all versions of NSV/BIOS. This sequence typed in the console connection to the server on the SP will drop Solaris[TM] into the debugger prompt and a reboot of the Service Processor will not interpreted as a break sequence. References and related documents. <Document: 1003085.1> Forcing a kernel core dump on an Solaris[TM] 2.x x86 system <Document: 1001950.1> When to Force a Solaris[TM] System Core File <Document: 1003869.1> How to setup platform serial console for Sun Fire[TM] V20z / Sun Fire[TM] V40z CR 6293881 sp reboot sends break sequence to server http://pts-platform.uk/twiki/bin/view/Products/ProdIssuesV20z

Product
Sun Fire V20z Server
Sun Fire V40z Server

Stinger, V20z, V40z, x86, kadb, kmdb, service processor, break sequence, 6293881
Previously Published As
82530

Change History
Date: 2005-10-04
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok
Verified audience - currently set to internal
Checked review date 2006-09-06
Checked for TM - no new ones needed
Publishing
Version: 4
Date: 2005-10-03
User Name: 31620
Action: Accept
Comment:
Version: 0
Date: 2005-10-03
User Name: 83378
Action: Approved
Comment: Sumitting for final review
Version: 0
Date: 2005-09-26
User Name: 83378
Action: Accept
Comment:
Version: 0




Attachments

This solution has no attachment