[SunHELP] Advice requested on UltraSPARC-III reboot problem

[Mike's List]

What machine is it that contains the 750Mhz?  Is it the right machine for
the CPU?  Is the CPU just replaced? and the kernel compiled with different
CPU/architecture? was there any new software upgrade?

> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 185311 kern.warning]
> WARNING:
>  [AFT1] Uncorrectable system bus (UE) Event on CPU0 User Data Access at
> TL=0,

The above lines would indicate the kernel panic due to problem with the
system bus and rebooted, happens on CPU0 (multiple processors system?)

Just guessing on my part from the errors, you should provide more
information to see if anyone else can figure it out...like system arch.
(do uname -X) upgrade machine? new hardware/software added? which OS
version you're running, etc.


- Mike


On Thu, 8 Nov 2001, Kent Fitch wrote:

> Hi,
> 
> We have a UltraSPARC III single CPU 750Mhz, 1GB machine which has
> rebooted itself 3 times in the past 4 months.  We've applied the
> latest patch set recommended by Sun.  Yesterday it rebooted
> again, and for the first time generated some messages immediately
> before rebooting.  Our local Sun people think they do not contain
> enough information to diagnose the problem, so I'm looking for
> references to information which can help me understand going on.
> 
> Here are the messages written just before the reboot:
> 
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 185311 kern.warning]
> WARNING:
>  [AFT1] Uncorrectable system bus (UE) Event on CPU0 User Data Access at
> TL=0,
>  errID 0x0005e6e9.b8efe820
> Nov  7 16:37:52 aserv AFSR 0x00000004<UE>.0000007b AFAR
> 0x00000000.04e37e10
> Nov  7 16:37:52 aserv Fault_PC 0xfe6313c4 Esynd 0x007b J0100 J0202 J0304
> J0406
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 565897 kern.notice]
> [AFT1] errID
>  0x0005e6e9.b8efe820 Two Bits were in error
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 369837 kern.info] [AFT2]
> errID
>  0x0005e6e9.b8efe820 PA=0x00000000.04e37e00
> Nov  7 16:37:52 aserv     E$tag 0x00000000.09492492 E$state_0 Exclusive
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 895151 kern.info] [AFT2]
> E$Data
> (0x00) 0x0000002c.00000000 0x00000000.00000000 ECC 0x178
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 819380 kern.info] [AFT2]
> E$Data
> (0x10) 0x0000002d.00000000 0x00000000.05000000 ECC 0x050 *Bad*
> Esynd=0x07b
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 895151 kern.info] [AFT2]
> E$Data
> (0x20) 0x0000002e.00000000 0x00000000.00000000 ECC 0x059
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 895151 kern.info] [AFT2]
> E$Data
> (0x30) 0xeee9002f.f8ce4a48 0x00000011.80000014 ECC 0x042
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 929717 kern.info] [AFT2]
> D$ data
>  not available
> Nov  7 16:37:52 aserv unix: [ID 321153 kern.notice] NOTICE: Scheduling
> clearing
>  of error on page 0x00000000.04e36000
> Nov  7 16:37:52 aserv SUNW,UltraSPARC-III: [ID 584495 kern.info] [AFT3]
> errID
>  0x0005e6e9.b8efe820 Above Error is in User Mode
> Nov  7 16:37:52 aserv     and is fatal: will reboot
> Nov  7 16:37:52 aserv unix: [ID 855177 kern.warning] WARNING: [AFT1]
> initiating
>  reboot due to above error in pid 19265 (java)
> Nov  7 16:37:54 aserv unix: [ID 221039 kern.notice] NOTICE: Previously
> reported
>  error on page 0x00000000.04e36000 cleared
> 
> The file systems were then synced at the machine rebooted.
> 
> Any pointers are welcome.
> 
> Kent Fitch
> AustLit gateway project http://www.austlit.edu.au
> 
> _______________________________________________
> SunHELP maillist  -  SunHELP at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/sunhelp
>