I have had four crashes in the last few weeks, the last two yesterday. I
have crash dumps for the last three. The relevant lines from the dumps seem
to be the following. The pc and ra contents are invariant, so this is bound
to be the same bug. The machine is a AlphaStation 2100 4/275 running DU 4.0
with two processors. The last two crashes were on cpu 1, the one before
that on cpu 0.
trap: invalid memory read access from kernel mode
faulting virtual address: 0x0000000100001ff0
pc of faulting instruction: 0xfffffc000050460c
ra contents at time of fault: 0xfffffc0000504608
sp contents at time of fault: 0xffffffffa16db710
trap: invalid memory read access from kernel mode
faulting virtual address: 0x0000000200011ff0
pc of faulting instruction: 0xfffffc000050460c
ra contents at time of fault: 0xfffffc0000504608
sp contents at time of fault: 0xffffffffa194b710
trap: invalid memory read access from kernel mode
faulting virtual address: 0x0000000300041ff4
pc of faulting instruction: 0xfffffc000050460c
ra contents at time of fault: 0xfffffc0000504608
sp contents at time of fault: 0xffffffffa1303710
I understand that 4.0a has been released but we don't have it here in NZ
yet. In the past there have been multi-processor patches that need to be
applied (but that we are not told about). Searching the archive, I found a
similar query but no summary. My machine has several user file systems that
are rather tight for space, so the crash dumps also lists many errors like
these:
/users/studs/ugrad: write failed, user disk quota exceeded too long
/users/studs/ugrad: warning, user disk quota exceeded
/users/studs/grada: warning, fileset disk quota exceeded
one which I don't know the meaning of is this:
chk_bf_quota: user/group underflow
If anyone can point me in the right direction that would be appreciated. I
need some evidence before I can get an order number to open a call to
Digital, if that is required. If anyone wants to look at the crash dumps, I
can mail them to them.
This crash is particularly annoying because my machine seems to hang at the
"syncing disks..." stage until the halt button is pressed. Perhaps this is
related to my disk space shortage.
Thanks in advance
clare
--
Clare West, Rm 107, Ext 8266
clare_at_cs.auckland.ac.nz
Received on Fri Oct 11 1996 - 00:08:13 NZDT