and later [Release: N/A and later ]
Information in this document applies to any platform.
Purpose
This document addresses common panics that can occur while booting a 10K ( Sun Enterprise[TM] 10000 ) Domain.
Last Review Date
April 7, 2011
Instructions for the Reader
A Troubleshooting Guide is provided to assist
in debugging a specific issue. When possible, diagnostic tools are included in the document
to assist in troubleshooting.
Troubleshooting Details
Cannot allocate IOMMU TSB arrays
Symptom:
Boot device: /sbus@40,0/SUNW,qfe@0,8c00000 File and args:
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
23a00 X
Requesting Internet address for 0:0:be:l6:28:1b
Internet address is 129.153.49.24 = 81993118
hostname: chef
domainname: SD_Lab.West.COM
root server: venus
root directory: /export/install/7/base.s998s_u3smccServer-11/Solaris_2.7/Tools/Boot
Alloc of 0x2140000 bytes at 0x10b80000 refused.
panic[cpu0]/thread=10404040: Cannot allocate IOMMU TSB arrays
rebooting...
Resolution:
The system is trying to boot Solaris 7, but Solaris 2.6 is specified in the domain_config file. Correct the domain_config file.
Fast Data Access MMU Miss
Symptom:
KERNEL dropped into OBP due to following trap at trap level = 1
Fast Data Access MMU Miss
Normal Alternate MMU Vector
0: 0 0 0 0
1: 0 1ff00000000 ffe916d0 40
2: 0 0 f1000000 12800003808
3: 0 0 0 0
4: 0 1fff0008d1c 0 1ff00000000
5: 0 f0008d1c f 0
6: 0 0 fff00000 0
Resolution:
There are some likely possibilities:
- inetboot file in /tftpboot on the SSP is incorrect. See <Document 1003020.1> for details.
- 400/8MB processors involved and boot image does not have the latest kernel patch. Install the latest kernel patch to the jumpstart image.
- dr-max-mem set too large or incorrectly on Solaris 2.5.1. Upgrade to SSP 3.5.
- A hardware problem. Run an hpost -l32 or hpost -l64 on the domain. A bringup -D on can also done.
lock_set_spl: 70222069 lock held and only one CPU
Symptom:
Rebooting with command: boot net -v
It took 741 milli seconds to do mailbox callback
Boot device: /sbus@44,0/SUNW,qfe@0,8c00000 File and args: -v
Using Onboard transceiver - Link Up.
2ee00
Server IP address: xxx.xx.xxx.xx
Client IP address: xxx.xx.xxx.xx
Using Onboard transceiver - Link Up.
hostname: lime
domainname: bob.madeup.com
root server: beans-ssp
root directory: /cdrom/sol_2_6_598_sparc_smcc_svr/s0/Solaris_2.6/Tools/Boot
Size: 335983+72325+449939 Bytes
cpu0: SUNW,UltraSPARC (upaid 4 impl 0x11 ver 0xa0 clock 400 MHz)
cpu1: SUNW,UltraSPARC (upaid 5 impl 0x11 ver 0xa0 clock 400 MHz)
cpu2: SUNW,UltraSPARC (upaid 6 impl 0x11 ver 0xa0 clock 400 MHz)
cpu3: SUNW,UltraSPARC (upaid 7 impl 0x11 ver 0xa0 clock 400 MHz)
It took 916 milli seconds to do mailbox callback
SunOS Release 5.6 Version Generic_105181-05 [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1997, Sun Microsystems, Inc.
Using default device instance data
mem = 4194304K (0x100000000)
avail mem = 4156407808
panic[cpu4]/thread=0x10404040: lock_set_spl: 70222069 lock held and only one CPU
rebooting...
BAD TRAP: cpu=4 type=0x31 rp=0x104035b8 addr=0x17 mmu_fsr=0x0 : trap type = 0x31
Resolution:
The CPUs in the domain being booted have an 8MB cache size, and the patch level of Solaris being booted does not recognize the cache. Apply the latest domain OS kernel patch.
munged memory list
Symptom:
Boot device: /sbus@64,0/SUNW,hme@0,8c00000 File and args: - install
2ee00 hostname: foo
domainname: bag.com
root server: foobar
root directory: /export/install/sparc/os/2.6-598-419+/Solaris_2.6/Tools/Boot
panic[cpu38]/thread=0x10404000: munged memory list = 0x10403914
Resolution:
The system is trying to boot Solaris 2.6, but Solaris 2.5.1 is specified in the domain_config file. Correct the domain_config file. See also <Document 1004475.1>.
Attachments
This solution has no attachment
