[e-nsp] Suggestions?

[Peter Kranz]

Greetings,
	Our Extreme Blackdiamond 6808 crashed last night in a manner where
it could not be reached via serial ports of IP addresses. We would
appreciate any suggestions on how to prevent this from re-occuring. The
following information was collected:

<A Hard crash occured about 20 minutes later than the next error>
03/16/2006 03:04:52.01 <Crit:SYST> Sys-health-check [EDP] checksum error
(slow-path) on MSM-A, port 0xb
03/16/2006 03:04:29.77 <Crit:KERN> Sys-health-check [INT] checksum error
(fast-path) on MSM-A. prev=56 cur=5b
03/16/2006 03:04:28.01 <Crit:SYST> Sys-health-check [DIAG] First 16 bytes of
unknown pkt (slow-path) on slot 7
03/16/2006 03:04:15.00 <Crit:SYST> Sys-health-check [DIAG] First 16 bytes of
unknown pkt (slow-path) on slot 2
03/16/2006 03:04:07.01 <Crit:SYST> Sys-health-check [DIAG] First 16 bytes of
unknown pkt (slow-path) on slot 1
03/16/2006 03:04:04.79 <Crit:KERN> Sys-health-check [INT] checksum error
(fast-path) on MSM-B. prev=0 cur=7
03/16/2006 03:04:04.77 <Crit:KERN> Sys-health-check [INT] checksum error
(fast-path) on MSM-A. prev=4c cur=51
03/16/2006 03:03:55.02 <Crit:KERN> Sys-health-check [CPU] checksum error
(slow-path) on slot 8
03/16/2006 03:03:00.01 <Crit:SYST> Sys-health-check [DIAG] First 16 bytes of
unknown pkt (slow-path) on slot 7
03/16/2006 03:02:58.77 <Crit:KERN> Sys-health-check [INT] checksum error
(fast-path) on MSM-A. prev=47 cur=4c

Also the following hidden errors were seen:
03/16/2006 03:56:07.23 <Crit:ENG> PBUS SYNC ERROR (2) got=100ff expected=ff
on MSM-A 
03/16/2006 03:56:02.23 <Crit:ENG> PBUS SYNC ERROR (1) got=100ff expected=ff
on MSM-A 
03/16/2006 03:55:57.23 <Crit:ENG> PBUS SYNC ERROR (0) got=100ff expected=ff
on MSM-A 

Peter Kranz
Founder/CEO - Unwired Ltd
www.UnwiredLtd.com
Desk: 510-868-1614 x100
Mobile: 510-207-0000
Fax: 510-217-6031
pkranz at unwiredltd.com