Asset ID:	1-72-1020195.1
Update Date:	2009-03-10
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1020195.1 :   eeprom command causes panic due to a spelling error of the parameter .  


PreviouslyPublishedAs
253989

Symptoms
When misspelling the value of the parameter of eeprom command such as "eeprom auto-boot?=flase" ( instead of "false" ), a the following panic reboot might occur.

panic[cpu0]/thread=30003ad0d60:
bad stack overflow at TL 2
%tl %tpc              %tnpc             %tstate           %tt
1  000000000101b958  000000000101b95c  0000001606        068
%ccr: 00  %asi: 00  %cwp: 6  %pstate: 16<PEF,PRIV,IE>
2  00000000010073dc  00000000010073e0  9100001507        068
%ccr: 91  %asi: 00  %cwp: 7  %pstate: 15<PEF,PRIV,AG>
%g0-3: 0000000000000000 000000000000000a 000000123eb40b30 000000123eb40b30
%g4-7: 0000000015080a0d 0000000000000002 000000000180e580 0000000000000068
Register window 7, caller callback_handler+20
	:
	:
* This panic can occur even after one typo.
* This panic can occur on any sun4u system with OBP revision older than 4.27. (not include 4.27)

Resolution
Upgrade OBP revision later than 4.27 .

Relief/Workaround
* use OBP command instead of eeprom command
or
* don't misspell the value of the parameter of eeprom command

Product
Sun Fire V215 Server
Sun Fire V245 Server

Internal Comments
This document is based on CR 6750765.

This CR ( 6750765 ) is a duplicate of CR 6510676. Currently, only patch 140685-01 for V215 / V245 has been released, there is no plan to release for other platforms.

Received the following comments form engineering.

6510676 was fixed 2 years ago (Feb 2007) and first became available in OBP 4.27.   
Looking at the OBP/POST Platform Patch Summary page http://re.west/SunWeb/Patches/obp/index.html ,
it looks like Seattle's previous release was based on 4.25.  The jump from 4.25 to 4.30 (which
inherited any fixes at the 4.27 level) would have involved a sizable list of CR's.
However, what is clearly true is that moving from 4.25 to 4.30 involved getting the fix for 6510676.

Most pre-CMT platforms are at or near EOL, so no new qualifications are planned.  But, for any platforms operating at an OBP revision older than 4.27, the solution is to get a release on anything 4.27 or higher.

Unless there is a customer request, there is no plan to make obp releases for other non-CMT platforms just to get the fix for CR 6510676.

Attachments

This solution has no attachment