[50] in netbsd-help mailing list archive
Re: installing NetBSD 1.0; AFS probs
daemon@ATHENA.MIT.EDU (John Kohl)
Wed Feb 8 16:03:17 1995
Date: Wed, 8 Feb 1995 16:02:40 -0500
From: John Kohl <jtkohl@MIT.EDU>
To: Eric Ding <ericding@MIT.EDU>
Cc: Greg Hudson <ghudson@MIT.EDU>, netbsd-help@MIT.EDU
In-Reply-To: "[48] in netbsd-help mailing list archive"
>>>>> "Eric" == Eric Ding <ericding@MIT.EDU> writes:
Eric> trap type 0 code 0 eip f870fb9d cs f81b0008 eflags 10202 cr2 100340b8 cpl 0
The 'eip' number is the instruction pointer at which the system
failed--it's the most useful of the numbers.
There are two things to try here to figure out what's going on.
(a) run a kernel with a debugger built in (options DDB). If you don't
have a kernel source tree and/or need help, contact either Greg
<ghudson> or John <jhawk> or John <jtkohl> and one of us could build you
such a kernel. If you run such a kernel, we can get a kernel stack
trace (type 'tr' to its prompt) when the fault occurs and probably
figure out what's going on.
(b) boot up single user, fsck, mount the disks, start your network, and
then _by hand_ run the module loading command as seen in the Athena
startup file. Then copy/FTP the file /usr/vice/etc/dkload/netbsd_afs to
Athena somewhere and tell me where it is. [This file will have a symbol
table to help translate the 'eip' (instruction pointer) to a faulty
routine.]
After you've copied the file, run the remaining AFS commands one by one,
and let us know which one causes the failure.
==John
