Subject: SS20 SMP panic
To: None <port-sparc@NetBSD.org>
From: Tillman Hodgson <tillman@seekingfire.com>
List: port-sparc
Date: 01/16/2005 00:02:45
The last thing logged in /var/log/messages:

Jan 15 23:17:06 surya /netbsd: Async registers (mid 9): afsr=3c00<SE,UC,TO,BE,AFA=0>; afva=0x00
Jan 15 23:17:06 surya /netbsd: Async registers (mid 8): afsr=3c00<SE,UC,TO,BE,AFA=0>; afva=0x00
Jan 15 23:17:06 surya /netbsd: nmi_hard: SMP botch.cpu0: NMI: system interrupts: 10090000<VME=0,SBUS=0,E,T,M>

The system looks like this:

NetBSD 2.0_BETA (GENERIC.MP) #0: Sat Sep  4 22:50:21 UTC 2004 autobuild@tgm.netbsd.org:/autobuild/netbsd-2-0/sparc/OBJ/autobuild/netbsd-2-0/src/sys/arch/sparc/compile/GENERIC.MP
total memory = 223 MB
avail memory = 214 MB
bootpath: /iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@0,0
mainbus0 (root): SUNW,SPARCstation-20: hostid 72375554
cpu0 at mainbus0: mid 8: RT620/625 @ 125 MHz, on-chip FPU
cpu0: 512K byte write-back, 32 bytes/line, sw flush: cache enabled
cpu1 at mainbus0: mid 9: RT620/625 @ 125 MHz, on-chip FPU
cpu1: 512K byte write-back, 32 bytes/line, sw flush: cache enabled

I was running "[root@surya /usr/src]# time ./build.sh tools" at the
time, as this machine is a transfer of my harddrive from a SS10 (that
had the power suppy a few days ago, sadly) that I'm trying to get going
again. The SS10 acted as my Kerberos KDC. Everything seemed to boot and
run fine until it paniced (including the KDC service, an `openssl speed`
benchmark run, and general poking around).

-T


-- 
One day, a student asked a master, "Master, there is conflict between the
suits and the sysadmins. Which group has the Zen nature, and which group is
grieviously disturbing the stillness of the Tao?" And the master said nothing,
but installed an operating system. And the student was enlightened. 
    - A.S.R. quote (Anthony DeBoer)