Messages in this thread | | | Date | Wed, 28 Jul 1999 09:55:41 +0200 (MDT) | From | Ulf Jaenicke-Roessler <> | Subject | Re: knfs, 2.2.10-ac12 oops |
| |
Hi,
following up to my own message with some new data.
I used modutils-2.2.2pre6 with Keith Owens ksymoops patch (thanks for the hint) to get nfsd symbols. I hope this helps to find the cause of the trouble.
Greetings,
Ulf
On Tue, 27 Jul 1999, it was written:
> using kernel 2.2.10-ac12 I get an reproducible oops when I stop knfsd. > It's done by an /etc/init.d script which calls 'killall -2 nfsd' > (Debian 2.1 + a lot of packages from "unstable", knfs 1.4.6 but I checked > 1.4.4 which shows the same problem) It started around 2.2.10-ac10. I > cannot tell it more precisely, sorry. > > /etc/exports contains two entries. The oops doesn't occur with only one > entry: > /home pc1 > / pc2 > (It doesn't seem to depend on the actual contents of the lines) > > I'm sorry if this is a known problem. I haven't read the kernel list lately.
ksymoops 0.7c on i586 2.2.10-ac12. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.10-ac12/ (default) -m /boot/System.map-2.2.10-ac12 (default)
Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options.
Unable to handle kernel paging request at virtual address 5a5a5e72 current->tss.cr3 = 00101000, %cr3 = 00101000 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c2879654>] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010206 eax: 0000001c ebx: 00000307 ecx: c156a800 edx: 5a5a5a5a esi: c14d1c50 edi: c14d1c50 ebp: c287ecc0 esp: c14b3f80 ds: 0018 es: 0018 ss: 0018 Process nfsd (pid: 186, process nr: 25, stackpage=c14b3000) Stack: 00000307 00000000 00000007 c2879c30 c14d1000 c14d1800 000000ac 0000002b c287a6e1 c14d1800 c14d1800 000000ac c287a8ba c14d1800 c14b2000 c14b2000 c14b2000 c14bfc00 c2875330 c287c4e3 00000100 c17a9f34 c14bfd60 c14bfc00 Call Trace: [<c2879c30>] [<c287a6e1>] [<c287a8ba>] [<c2875330>] [<c287c4e3>] [<c0106523>] Code: 66 39 9a 18 04 00 00 74 06 8b 12 85 d2 75 f1 85 d2 74 09 b8
>>EIP; c2879654 <[nfsd]exp_device_in_use+24/4c> <===== Trace; c2879c30 <[nfsd]exp_unexport_all+48/5c> Trace; c287a6e1 <[nfsd]exp_freeclient+11/24> Trace; c287a8ba <[nfsd]nfsd_export_shutdown+62/a0> Trace; c2875330 <[nfsd]nfsd+218/250> Trace; c287c4e3 <[nfsd].rodata.start+143/2384> Trace; c0106523 <kernel_thread+23/30> Code; c2879654 <[nfsd]exp_device_in_use+24/4c> 00000000 <_EIP>: Code; c2879654 <[nfsd]exp_device_in_use+24/4c> <===== 0: 66 39 9a 18 04 00 00 cmpw %bx,0x418(%edx) <===== Code; c287965b <[nfsd]exp_device_in_use+2b/4c> 7: 74 06 je f <_EIP+0xf> c2879663 <[nfsd]exp_device_in_use+33/4c> Code; c287965d <[nfsd]exp_device_in_use+2d/4c> 9: 8b 12 movl (%edx),%edx Code; c287965f <[nfsd]exp_device_in_use+2f/4c> b: 85 d2 testl %edx,%edx Code; c2879661 <[nfsd]exp_device_in_use+31/4c> d: 75 f1 jne 0 <_EIP> Code; c2879663 <[nfsd]exp_device_in_use+33/4c> f: 85 d2 testl %edx,%edx Code; c2879665 <[nfsd]exp_device_in_use+35/4c> 11: 74 09 je 1c <_EIP+0x1c> c2879670 <[nfsd]exp_device_in_use+40/4c> Code; c2879667 <[nfsd]exp_device_in_use+37/4c> 13: b8 00 00 00 00 movl $0x0,%eax
1 warning issued. Results may not be reliable.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |