I'm trying to do an AI install on a SPARC T5220 system, using the latest 
software in the gate. I am getting this panic when booting off of the 
miniroot. Note that a different SPARC system (Ultra 45) boots and 
installs fine from the same image. Any clues or advice? I can give 
access to the AI server and system for people within SWAN.

-- Alan

-------------

{0} ok boot net:dhcp
Boot device: /pci at 0/pci at 0/pci at 1/pci at 0/pci at 2/network at 0:dhcp  
File and args:
1000 Mbps full duplex  Link up
Timed out waiting for BOOTP/DHCP reply
<time unavailable> wanboot info: WAN boot messages->console
<time unavailable> wanboot info: configuring 
/pci at 0/pci at 0/pci at 1/pci at 0/pci at 2/network at 0:dhcp

1000 Mbps full duplex  Link up
<time unavailable> wanboot info: Starting DHCP configuration
1000 Mbps full duplex  Link up

Requesting Ethernet address for: 10.4.164.1
<time unavailable> wanboot info: DHCP configuration succeeded
<time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%)
<time unavailable> wanboot info: wanbootfs: Download complete
Mon Aug 17 23:11:07 wanboot progress: miniroot: Read 167873 of 167873 kB 
(100%)
Mon Aug 17 23:11:07 wanboot info: miniroot: Download complete
WARNING: mmu-#ra-bits property not found in MD
WARNING: Memory DR disabled
SunOS Release 5.11 Version snv_121 64-bit
Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
\
panic[cpu0]/thread=180e000: BAD TRAP: type=31 rp=180b780 addr=50 
mmu_fsr=0 occurred in module "unix" due to a NULL pointer dereference

: trap type = 0x31
addr=0x50
pid=0, pc=0x104afa4, sp=0x180b021, tstate=0x4480001605, context=0x0
g1-g7: 0, 0, 0, 11864537b76b35, 5, 10, 180e000

000000000180b490 unix:die+74 (10c9400, 180b780, 50, 0, 8, 180b550)
  %l0-3: 000000000104afa4 0000000000000000 0000000000100000 0000000001000000
  %l4-7: 0000000000002000 00000000010c95c8 00000000010c9400 000000000000000b
000000000180b570 unix:trap+9e8 (180b780, 1fff, 31, da5c2050, 1828540, 5)
  %l0-3: 0000000000000000 0000000000000000 0000000000010000 000000000185f1c0
  %l4-7: 0000000000000001 000000000180c000 0000000000000001 0000000000000000
000000000180b6d0 unix:ktl0+64 (1, 0, 300015c7bc0, 180b818, 80000000, 
300015c7bc0)
  %l0-3: 000000000180c000 0000000000000000 0000004480001605 000000000101f0c0
  %l4-7: 0000000000000000 0000030003619808 0000000000000000 000000000180b780
000000000180b820 unix:unmap_prom_mappings+118 (6080200, 119, f0000000, 
18605f0, 18, 60012b94240)
  %l0-3: 0000000000000000 000000000fffffff 0000000000002000 000000000180b938
  %l4-7: 00000000fed0c000 0000000000000000 0000000000000010 0000000001861680
000000000180b940 unix:cif_init+b4 (20000, 1866800, 104b000, 60012b94000, 
10cd400, 3)
  %l0-3: 0000000001000000 000000000104ad34 0000000001881800 000000000104ac00
  %l4-7: 00000000f025cc58 0000000001829000 0000000000000000 0000000000000000
000000000180ba00 genunix:main+21c (1902000, 1, 182b800, 185f1c0, 2, 18f5400)
  %l0-3: 000000000180e000 0000000000000000 00000000018a7400 0000000001866800
  %l4-7: 0000000000000000 0000000001902000 000000004a89e32f 0000000001902000

syncing file systems... done
skipping system dump - no dump device configured


Reply via email to