On Fri, 2008-08-22 at 11:23 +0100, Ian Campbell wrote: > On Mon, 2008-08-18 at 15:20 -0400, Trond Myklebust wrote: > > Please try to reproduce the hang, then do > > > > echo 0 >/proc/sys/sunrpc/rpc_debug > > > > and send the output from 'dmesg'... > > I've also been seeing some NFS related lockups, although I'm not sure if > they are the same as the one in this thread or not. Client is 2.6.26 > (Debian's kernel) and Server is 2.6.25 (also a Debian kernel, but from > backports.org). > > rpc_debug on the server gives nothing, on the client gives: > [144741.637997] -pid- proc flgs status -client- -prog- --rqstp- -timeout -rpcwait -action- ---ops-- > [144741.637997] 3439 0004 0080 -11 f3f48200 100003 f7770000 0 xprt_sending fa0ae88e fa0bddf4 > [144741.637997] 3438 0001 00a0 0 f77f2a00 100003 f77700d0 15000 xprt_pending fa0ae88e fa0bddf4 That's probably also a networking device driver issue candidate: your RPC task is queued up waiting to be sent. What networking card+device driver are you using here? > There are no processes running with pid 3439 3438 (I don't think it's > that sort of pid though). The 'pid' is an internal RPC cookie that just serves to identify and track specific RPC requests. Cheers Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
