Bug#408446: (no subject)
Well, after swapping all the CPU modules around (modules which also hold
the memory for each CPU)
it still comes up "RED State Exception" with the daily installer from
31st of January:
I'm no expert, but I assume that since each CPU and memory have changed
place another CPU/memory than previously
is used for booting. Since it still comes up faulty it indicates to me
that at least it's not a CPU or memory error ?
And if I go back to Solaris it works fine, and with Debian
testing/unstable netboot image initial boot works fine.
(With Debian testing/unstable it croaks with the Oops in the Cassini
driver..)
Please let me know if there are more things I can test, the SunFire box
is available for testing for quite a while :-)
{3} ok boot net:dhcp
Boot device: /pci@1c,600000/network@2:dhcp File and args:
/pci@1c,600000/network@2: 100 Mbps full duplex link up
|
Remapping the kernel... done.
Booting Linux...
RED State Exception
Error enable reg: 0000.0001.00f0.001f
CPU: 0000.0000.0000.0003
TL=0000.0000.0000.0005 TT=0000.0000.0000.0020
TPC=0000.0000.0041.4404 TnPC=ffff.ffff.91e6.f9b4
TSTATE=0000.0000.8000.9506
TL=0000.0000.0000.0004 TT=0000.0000.0000.0020
TPC=0000.0000.0041.4404 TnPC=ffff.ffff.91e6.f9b4
TSTATE=0000.0000.8000.9506
TL=0000.0000.0000.0003 TT=0000.0000.0000.0020
TPC=0000.0000.0041.4204 TnPC=ffff.ffff.91e6.f7b4
TSTATE=0000.0000.8000.9506
TL=0000.0000.0000.0002 TT=0000.0000.0000.0010
TPC=0000.0000.0041.11c8 TnPC=0000.0000.0041.11cc
TSTATE=0000.0000.8000.9506
TL=0000.0000.0000.0001 TT=0000.0000.0000.0010
TPC=0000.0000.0041.ac58 TnPC=0000.0000.0041.ac5c
TSTATE=0000.0000.8000.9604
Reply to: