Document Audience: | INTERNAL |
Document ID: | I0708-1 |
Title: | Newly installed X-6748 or FRUs may cause a panic message on Serengeti |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2001-08-03 |
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
FIN #: I0708-1
Synopsis: Newly installed X-6748 or FRUs may cause a panic message on SerengetiCreate Date: Aug/03/01
Keywords:
Newly installed X-6748 or FRUs may cause a panic message on Serengeti
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Serengeti Sun Fire X800
Product Category: Server / Service
Product Affected:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- S24 ALL Sun Fire 6800 -
- S12i ALL Sun Fire 4810 -
- S12 ALL Sun Fire 4800 -
- S8 ALL Sun Fire 3800 -
X-Options Affected
------------------
X6748 - - cPCI DUAL FC-AL HBA -
Parts Affected:
Part Number Description Model
----------- ----------- -----
375-0118-02 cPCI Dual FC Network Adapter -
F375-0118-02 FRU cPCI Dual FC Network Adapter -
References:
BugId: 4461405 - panic[cpu0]/thread=10408000: CPU0 Privileged Bus
Error: AFSR 0x00100800.00000000.
ECO: WO_21386
LEAP: 1647
WW StopShip: WSS001#00022
Issue Description:
Sun Fire x800 systems are subject to a "panic" problem at boot time
when a cPCI Dual FC Network Adapter (FRU or X-option) is installed for
the first time. If a customer installs this board and boots the
system, they will see panic messages on the console and the boot will
fail. However, any subsequent reboots will be successful. This may
result in an unnecessary service call.
This cPCI board (P/N 370-0118-02) has been shipped with Sun Fire X800
systems and as an X-option. The current estimate is that less than
1000 boards have been installed in systems and 1200 boards are in field
stock (FRUs and x-options) as of 7/12/01.
Here's the sample error message:
{0} ok boot /ssm@0,0/pci@18,700000/pci@2/SUNW,isptwo@4/sd@0,0 kadb -rv
Size: 159078+397112+855184 Bytes
kadb: kernel/sparcv9/unix
Size: 344336+156426+483038 Bytes
/platform/SUNW,Sun-Fire/kernel/sparcv9/unix loaded - 0x150000 bytes used
SunOS Release 5.8 Version Sun_Fire_DR_BETA_2001-04-05 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
Ethernet address = 50:0:14:a4:dd:4e
mem = 4192960K (0xffeb0000)
avail mem = 4076118016
root nexus = Sun Fire 3800
ssm0 at root: SSM Node 0
ssm0 is /ssm@0,0
pci108e,80010 at ssm0: Node 0 Safari id 24 0xc700000
pcisch0 is /ssm@0,0/pci@18,700000
pci108e,80011 at ssm0: Node 0 Safari id 24 0xc600000
pcisch1 is /ssm@0,0/pci@18,600000
pci108e,80012 at ssm0: Node 0 Safari id 25 0xcf00000
pcisch2 is /ssm@0,0/pci@19,700000
pci108e,80013 at ssm0: Node 0 Safari id 25 0xce00000
pcisch3 is /ssm@0,0/pci@19,600000
pci108e,80014 at ssm0: Node 0 Safari id 28 0xe700000
pcisch4 is /ssm@0,0/pci@1c,700000
pci108e,80015 at ssm0: Node 0 Safari id 28 0xe600000
pcisch5 is /ssm@0,0/pci@1c,600000
pci108e,80016 at ssm0: Node 0 Safari id 29 0xef00000
pcisch6 is /ssm@0,0/pci@1d,700000
pci108e,80017 at ssm0: Node 0 Safari id 29 0xee00000
pcisch7 is /ssm@0,0/pci@1d,600000
PCI-device: pci@2, db215540
db215540 is /ssm@0,0/pci@18,700000/pci@2
panic[cpu0]/thread=10408000: CPU0 Privileged Bus Error: AFSR
0x00100800.00000000 AFAR 0x00000638.08000020
0000000010406a20 SUNW,UltraSPARC-III:cpu_async_error+630 (10080000000000,
63808000020, 0, 10406c20, 0, 219)
%l0-3: 0000000000000000 0000000000000001 0000000000000000 0000000000000000
%l4-7: 0000000000000000 0000000000000000 0010080003200000 0000000000000000
0000000010406b70 unix:prom_rtt+0 (30000814008, 30000a5a026, e0000000,
3000081d188, 300000ac000, 300000ac130)
%l0-3: 0000000000000007 0000000000001400 0000000080001606 000000001013dab8
%l4-7: 0000000000000103 0000000000000000 0000000000000000 0000000010406c20
0000000010406cc0 db21554:db_enable_io+2a8 (40000000, 30000820088, 2, 40, 0,
10406e6c)
%l0-3: 00000000104fcc00 000003000097b198 000003000097b198 0000000000ff0000
%l4-7: 000000000000ff00 0000000001010000 0000000000000000 0000000000000000
0000000010406d80 db21554:db_attach+328 (104fd400, 80000000, 300008200e0,
300008200d8, 300008200e8, 30000820088)
%l0-3: 00000300019b48d0 00000000100a8d18 000003000097b198 0000000000000004
%l4-7: 0000000000000000 0000000000000000 0000000000000001 00000000f08067f0
0000000010406e70 genunix:devi_attach+cc (0, 10210ad0, 3000097b198, 0,
300000a2000, 30000818648)
%l0-3: 000003000097b830 00000000104d4c08 000000001005abbc 0000030000814408
%l4-7: 0000000078002000 0000030000967f8b 0000000000000000 0000000000000000
0000000010406f50 unix:impl_probe_attach_devi+78 (3000097b198, 0, 3000082d488,
104d5220, 1, 104d522c)
%l0-3: 000003000082c660 000003000097b198 0000000000000098 000000007fffffff
%l4-7: 0000030000aa3378 0000030000814418 0000000000000000 0000000000000000
0000000010407030 unix:impl_initdev+14 (104fd058, 3000097b198, 20, 300008b7440,
104aaea8, 98)
%l0-3: 0000030000827cc0 0000000000003440 0000000000000001 00000000109a46a0
%l4-7: 0000000000000016 000000000000000e 0000000000000016 00000300018d44a0
00000000104070e0 unix:impl_proto_to_cf2+b4 (300008b7458, 300008b7440, 98,
3000097b198, 0, 300019b4d30)
%l0-3: 0000030000814408 0000000078000000 00000000ff000000 0000000000ff0000
%l4-7: 000000000000ff00 00000000ff1eff03 0000000000000002 0000000000000000
00000000104071a0 genunix:attach_driver_to_hw_nodes+a4 (3000097b200,
3000097a398, 0, 104aaea8, 3000097b198, 0)
%l0-3: 0000000000000098 0000000000003440 0000000000000000 000000000000006d
%l4-7: 0000000000000000 0000000010422a50 0000000000000000 0000000000000001
0000000010407250 genunix:ddi_hold_installed_driver+184 (104fd058, 300008b7458,
300008b7440, 98, 104fd058, 104073e5)
%l0-3: 0000000010152ea4 00000000104ac9e8 000000000184a000 00000000104a9620
%l4-7: 0000000000000000 0000000010423ac8 00000000000c8560 0000000000000560
0000000010407310 genunix:i_ddi_resolve_pathname+e8 (3000081b718, 0, 104075b8,
0, 104d8960, 104ab9d0)
%l0-3: 00000000104075b8 0000000000000000 ffffffffffffffff 0000000000000000
%l4-7: 000003000097cc50 000000000000006d 0000000000000098 0000000000000540
0000000010407500 genunix:ddi_pathname_to_dev_t+c (10456ef8, 10408000, 20, 0,
0, 30000969c98)
%l0-3: 0000000010456eeb 000000001013ab0d 0000000000000000 000000007fffffff
%l4-7: 0000000010983e80 0000030000969cae 0000000000000000 0000000000000000
00000000104075c0 swapgeneric:getrootdev+c (104a9670, 10456ef8, 20,
30000964ec0, 300000a6000, 300000a6130)
%l0-3: 000003000009e380 0000030000aa2c78 0000000000000000 00000000104be9b8
%l4-7: 00000000104bdb10 00000000104bdaf0 0000000000000000 0000000010983e80
0000000010407670 unix:stubs_common_code+70 (104a9670, 104ac170, 20,
30000964ec0, 300000a6000, 300000a6130)
%l0-3: 0000000010406f39 0000000010407011 0000000000000000 0000000000002000
%l4-7: 0000000000000000 0000000010422ac8 0000000000002000 00000000104c6ee0
0000000010407740 ufs:ufs_mountroot+130 (104b7f60, 0, 104b7f60, 10, 0, 0)
%l0-3: 0000000000000000 000000001012f044 0000000000010000 ffffffffffffffff
%l4-7: 00000000000000b0 0000000010423e58 00000300019be000 00000300018d44a0
0000000010407810 swapgeneric:rootconf+2b8 (104d6800, 104a9400, 104cfd28,
10456ee8, 6, 1)
%l0-3: 00000000101573f4 000000000000000a 0000000000000000 0000000000000000
%l4-7: 0000000000000000 0000000010457110 00000300019cb688 00000000104c24f8
00000000104078c0 unix:stubs_common_code+70 (300019bd000, 300019bd000, 1000,
300000e2000, 300019bd000, 1)
%l0-3: 0000000010139368 0000000000000000 0000030000ad4380 0000000000000008
%l4-7: 00000000000000b0 0000000010422a50 0000000000000000 0000000000000001
0000000010407970 genunix:vfs_mountroot+54 (104cc588, 0, 0, 10420df8, 10, 14)
%l0-3: 00000000104a9400 00000000104ac9e8 000000000184a000 00000000104a9620
%l4-7: 0000000000000000 0000000010423ac8 00000000000c8560 0000000000000560
0000000010407a20 genunix:main+94 (10420640, 2000, 10407ec0, 10408030, fff2,
100504d4)
%l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000e83
%l4-7: 000000001049c628 00000000104d5960 00000000000e2820 0000000000000540
The above panic condition occurs due to the system OBP code detecting
an incompatible value in the EEPROM of the new X-6748 board. The OBP
code will proceed to reprogram this EEPROM to the correct value. In
the process, some register values in the X6748A board are momentarily
changed and these interim contents will cause the boot process to
complain and panic. The system will reset and then reboot, and the
problem will go away permanently.
An ECO has been generated to bring the board to 375-0118-03 since July
18, 2001. The manufacturer (QLogic) will program the EEPROM with the
compatible values so that the system OBP will not have to go through
the reprogram sequence. Host adapters with part number 370-0118-03 or
greater will not have this problem.
Implementation:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
Corrective Action:
The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives who may encounter the above
mentioned problem:
For all Sun Fire x800 systems that have cPCI Dual FC Network Adapter
boards with part number 370-0118-03, no action is required.
For all Sun Fire x800 systems that have cPCI Dual FC Network Adapter
boards with part number 370-0118-02 must be installed into a Sun Fire
x800 system in order to have their EEPROM code corrected. This can
be done as part of a normal installation at a customer site, or can be
done on a test or non-production system prior to an actual production
installation.
The host adapter can be fixed by adhering to the following guideline.
1) Powering down an available Sun Fire system.
2) Installing the host adapter into an empty cPCI slot.
3) Booting Solaris with "boot -rv".
4) Remove the board after power down.
5) Board is now fixed.
Comments:
None
----------------------------------------------------------------------------
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist. Edist can be
accessed internally at the following URL: http://edist.corp/.
* From there, follow the hyperlink path of "Enterprise Services Documenta-
tion" and click on "FIN & FCO attachments", then choose the appropriate
folder, FIN or FCO. This will display supporting directories/files for
FINs or FCOs.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
---------------------------------------------------------------------------