NFS oops with 2.3.99-pre3

From: Albert D. Cahalan (acahalan@cs.uml.edu)
Date: Fri Oct 20 2000 - 16:14:04 EST


While copying a file to an NFS filesystem, cp got stuck and I later
found an oops on the console.

These are mounted:

pc-sw8:(pid282) on /net type auto (intr,rw,port=1023,timeo=8,retrans=110,indirect,map=/etc/amd/amd.net)
inxs4:/export/home on /amd/inxs4/root/export/home type nfs (rw)

This seems to be the hung process. There is no PID 6569, and there
were no messages about PID 6571. Anyway, cp is stuck in __down().

  F STAT PID PPID %CPU PRI WCHAN WCHAN COMMAND
000 D 6571 1 0.0 39 down 107ab0 cp

Running "uname -a" on the server called inxs4 reports:

SunOS inxs4 5.6 Generic_105181-11 sun4u sparc

I'm using an "amd" that comes from Debian, and it reports:

Unofficial patch level 102.
amd 5.2.2.2 of 1992/05/31 16:53:21 bsd44-beta #0: Wed Aug 9 14:16:02 PDT 2000

Here is everything I could get off the console. Since gpm is still
working, this ought to be accurate.

nfs warning: mount version newer than kernel
nfs_read_super: get root fattr failed
INIT: version 2.78 reloading
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c015cc28
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c015cc28>]
EFLAGS: 00010286
eax: 00000000 ebx: c0a8e064 ecx: c0b0e818 edx: c1f03dd0
esi: c1b36780 edi: c015cc18 ebp: c0a8e064 esp: c1f03c9c
ds: 0018 es: 0018 ss: 0018
Process cp (pid: 6569, stackpage=c1f03000)
Stack: c1f03d1c c01f5be6 c0a8e064 c0b0e818 c1f03dd0 00000246 c1f03cec c1f03d1c
       00000286 c01f86c3 c1f03d1c c1f03d14 00000000 c1f03d1c c1b36780 c1f02000
       c01f5232 c1f02000 c1f03d84 c1f03d84 c1f03cec c01f84a4 c01f8a02 c1f03d1c
Call Trace: [<c01f5be6>] [<c01f86c3>] [<c01f5232>] [<c01f84a4>] [<c01f8a02>] [<c01f5242>] [<c01f6e78>]
       [<c01f9a3d>] [<c015bb1a>] [<c0157f79>] [<c015a8c1>] [<c015a9a5>] [<c0159270>] [<c0157775>] [<c0122aca>]
       [<c013bb28>] [<c0157829>] [<c012a2fc>] [<c01094bc>]
Code: c7 00 02 00 00 00 8b 02 50 51 53 e8 fc fc ff ff 83 c4 0c 5b

First column is the address from above, second is the function:

c01094bc system_call
c0122aca generic_file_write
c012a2fc sys_write
c013bb28 update_atime
c0157775 nfs_commit_write
c0157829 nfs_file_write
c0157f79 nfs_writepage_sync
c0159270 nfs_updatepage
c015a8c1 nfs_instantiate
c015a9a5 nfs_create
c015bb1a nfs_proc_write
c015cc18 nfs_xdr_writeres
c015cc28 nfs_xdr_writeres
c01f5232 rpc_call_sync
c01f5242 rpc_call_sync
c01f5be6 call_decode
c01f6e78 xprt_timer
c01f84a4 __rpc_wake_up
c01f86c3 __rpc_execute
c01f8a02 rpc_execute
c01f9a3d rpc_init_task

These didn't map to anything. (many are stack addresses)

c0a8e064 ?
c0b0e818 ?
c1b36780 ?
c1f02000 ?
c1f03000 ?
c1f03c9c ?
c1f03cec ?
c1f03d14 ?
c1f03d1c ?
c1f03d84 ?
c1f03dd0 ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon Oct 23 2000 - 21:00:17 EST