About half an hour ago (while absent for lunch !) my Alpha 255 with DU 3.2
panicked and crashed. AFAIK it was idle (but could have been processing mail,
or httpd requests).
In crash-data.4 I see, among other, the following stuff :
_panic_string: 0xfffffc0000657588 = "kernel memory fault"
<4>intr: stray interrupt: present_ipl:0x6 vector:0x10b
trap: invalid memory read access from kernel mode
faulting virtual address: 0xb67e0080b41e0028
pc of faulting instruction: 0xfffffc0000391a78
ra contents at time of fault: 0xfffffc00004f2fec
sp contents at time of fault: 0x000000011ffefc70
panic (cpu 0): kernel memory fault
Also if interpret correctly the "_current_pid: 18317" the machine was just
excuting the X server (pid 18317 was Xdec).
I had another crash in August (but at the time there was a "machine check"
message). In such case I called DEC, and they examined the crash data, and
concluded that : (a) they could not go any further because DU 3.2 is old, (b)
there were no signs of hardware problems.
I'm inclined to do nothing this time (and surely I do not intend to upgrade
from 3.2), but I'd wnat to know :
- anybody got an idea of what the "stray interrupt" is ?
- should I worry about the status of my memory banks ?
- is there any diagnostic commands I could use to check my memory ?
Thanks in advance
----------------------------------------------------------------------------
Lucio Chiappetti - IFCTR/CNR - via Bassini 15 - I-20133 Milano (Italy)
For more info :
http://www.ifctr.mi.cnr.it/~lucio/personal.html
----------------------------------------------------------------------------
Received on Tue Oct 06 1998 - 12:23:52 NZDT