This ooops happened while trying to nfsboot a 386, and restarting nfsd
halfway through the boot process. I bet it's not a common problem...
Server is 2.4.2-ac23, client (the Oopser) is 2.4.2-ac24.
The oops is partial because I had to hand-copy from the console, and
it blanked after a few minutes. The client was trying to mount its
root fs at the time (it failed).
-Eric
------
ksymoops 2.4.1 on i586 2.4.2-ac23. Options used
-V (default)
-K (specified)
-L (specified)
-O (specified)
-m /packages/linux/2.4.2-ac24/i386-nfsroot/boot/System.map (specified)
*pde = 00000000
Oops: 0000
EIP: 0010:[<00000000>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 00000000 ebx: fffffff4 ecx: c0095420 edx: c0095380
Call Trace: [<c0139c37> <c0139fe7> <c013aa2f> <c012fb22> <c012fe25> <e0108d73>]
Code: Bad EIP value
>>EIP; 00000000 Before first symbol
Trace; c0139c37 <real_lookup+53/c4>
Trace; c0139fe7 <path_walk+223/77c>
Trace; c013aa2f <open_namei+73/570>
Trace; c012fb22 <filp_open+3e/4c>
Trace; c012fe25 <sys_open+45/b8>
Trace; e0108d73 <END_OF_CODE+1fe129ff/????>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
