I have a Sun Ultra 10 440Mhz 512MB RAM running Solaris 8 (reinstalled less than 1 month ago). I can boot into the OS OK. But as soon as I start anything such as installing software, listing files etc. the Sun panics and reboots. This happens very often, once it crashes it can crash upto 4 or 5 times when restarting before it stabilizes. But without fail as soon as I do something it crashes again. Some of the messages output to the screen include: 1. Last login: Tue Feb 10 14:34:28 from 169.254.53.1 Feb 10 16:42:05 apac-sun01 login: ROOT LOGIN /dev/console Sun Microsystems Inc. SunOS 5.8 Generic February 2000 # cd /var/crash/apac-sun01 # pwd /var/crash/apac-sun01 # ls bounds unix.1 unix.23 vmcore.1 vmcore.23 unix.0 unix.22 vmcore.0 vmcore.22 # panic[cpu0]/thread=2a1000fdd40: BAD TRAP: type=10 rp=2a1000fd2b0 addr=101527c8 m mu_fsr=0 sched: illegal instruction fault: addr=0x101527c8 pid=0, pc=0x101527c8, sp=0x2a1000fcb51, tstate=0x4480001602, context=0x0 g1-g7: 1041c400, 1, 1041c670, ffffffffffff8000, 21ce, 0, 2a1000fdd40 2. syncing file systems... done dumping to /dev/dsk/c0t0d0s1, offset 107479040 100% done: 5023 pages dumped, compression ratio 4.60, dump succeeded rebooting... Resetting ... Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz), Keyboard Present OpenBoot 3.25, 512 MB (50 ns) memory installed, Serial #16312341. Ethernet address 8:0:20:f8:e8:15, Host ID: 80f8e815. Rebooting with command: boot Boot device: disk File and args: SunOS Release 5.8 Version Generic_108528-03 64-bit Copyright 1983-2000 Sun Microsystems, Inc. All rights reserved. | panic[cpu0]/thread=10408000: BAD TRAP: type=10 rp=10406930 addr=100dbf78 mmu_fsr =0 : illegal instruction fault: addr=0x100dbf78 pid=0, pc=0x100dbf78, sp=0x104061d1, tstate=0x80001602, context=0x0 g1-g7: 1, 100ec000, 7, 57, 6d, 1041be18, 10408000 Does anyone know what could be the problem?

looks like pid=0 is not having fun... (sched) (that is your core of unix..) You can try patching in single user mode. (recommended cluster of solaris 8... But I expect you might reinstall the system again. (and patch afterwards,) Hth

cd /var/adm do a more on messages and grab 10 to 15 lines before the panic[cpu0]/thread=10408000: BAD TRAP: type=10. This seems like a harware error to me. If we can't figure it out with info you post you can email a zip file of your messages and I can look at them for you. I have a Ultra 60 running solaris 9. I am a Manager For a Sun Reman Company. You can trust me. Thanks

Here is the 15 lines before today's crash: Feb 12 11:50:41 apac-sun01 ebus: [ID 521012 kern.info] power0 at ebus0: offset 14,724000 Feb 12 11:50:41 apac-sun01 genunix: [ID 936769 kern.info] power0 is /pci@1f,0/pci@1,1/ebus@1/power@14,724000 Feb 12 11:50:41 apac-sun01 ebus: [ID 521012 kern.info] su0 at ebus0: offset 14,3083f8 Feb 12 11:50:41 apac-sun01 genunix: [ID 936769 kern.info] su0 is /pci@1f,0/pci@1,1/ebus@1/su@14,3083f8 Feb 12 11:50:41 apac-sun01 ebus: [ID 521012 kern.info] su1 at ebus0: offset 14,3062f8 Feb 12 11:50:41 apac-sun01 genunix: [ID 936769 kern.info] su1 is /pci@1f,0/pci@1,1/ebus@1/su@14,3062f8 Feb 12 11:50:41 apac-sun01 ebus: [ID 521012 kern.info] se0 at ebus0: offset 14,400000 Feb 12 11:50:41 apac-sun01 genunix: [ID 936769 kern.info] se0 is /pci@1f,0/pci@1,1/ebus@1/se@14,400000 Feb 12 11:50:42 apac-sun01 unix: [ID 987524 kern.info] cpu0: SUNW,UltraSPARC-IIi (upaid 0 impl 0x12 ver 0x91 clock 440 MHz) Feb 12 11:50:43 apac-sun01 hme: [ID 517527 kern.info] SUNW,hme0 : PCI IO 2.0 (Rev Id = c1) Found Feb 12 11:50:43 apac-sun01 simba: [ID 370704 kern.info] PCI-device: network@1,1, hme0 Feb 12 11:50:43 apac-sun01 genunix: [ID 936769 kern.info] hme0 is /pci@1f,0/pci@1,1/network@1,1 Feb 12 11:50:44 apac-sun01 genunix: [ID 454863 kern.info] dump on /dev/dsk/c0t0d0s1 size 512 MB Feb 12 11:50:46 apac-sun01 hme: [ID 517527 kern.info] SUNW,hme0 : Internal Transceiver Selected. Feb 12 11:50:46 apac-sun01 hme: [ID 517527 kern.info] SUNW,hme0 : Auto-Negotiated 100 Mbps Full-Duplex Link Up Feb 12 11:51:07 apac-sun01 unix: [ID 836849 kern.notice] Feb 12 11:51:07 apac-sun01 panic[cpu0]/thread=30000b432a0: Feb 12 11:51:07 apac-sun01 unix: [ID 695590 kern.notice] CPU0 Ecache SRAM Data Parity Error: AFSR 0x00000000.804000b0 AFAR 0x0000017e.ffffff78 Feb 12 11:51:07 apac-sun01 unix: [ID 100000 kern.notice]

this is the error I needed kern.notice] CPU0 Ecache SRAM Data Parity Error We would replace your CPU. There is a slight possibility it is your memory but usually you would get ECC errors on a UE Ecache error with that. Sorry to give you the bad news. Patching will not help Thanks Chris

Thanks cndcadams. I've come across a few posts on the net re Ultra 10's crashing and nearly every one was caused by faulty CPU. Time to sell up the house in order to pay Sun to replace the CPU! FYI, Just received the following error: # fsck -y panic[cpu0]/thread=30000dcc800: BAD TRAP: type=10 rp=2a1003ab770 addr=10157bb8 m mu_fsr=0 fsck: illegal instruction fault: addr=0x10157bb8 pid=291, pc=0x10157bb8, sp=0x2a1003ab011, tstate=0x1606, context=0x1071 g1-g7: 0, 10462a00, 0, ff360000, 30000d8d690, 0, 30000dcc800