From: Nix <nix@esperi.org.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org, thockin@hockin.org
Subject: Re: 2.6.15.1: persistent nasty hang in sync_page killing NFS (ne2k-pci / DP83815-related?), i686/PIII
Date: Mon, 30 Jan 2006 16:55:47 +0000 [thread overview]
Message-ID: <874q3lwt7w.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <1138572140.8711.82.camel@lade.trondhjem.org> (Trond Myklebust's message of "Sun, 29 Jan 2006 17:02:20 -0500")
On Sun, 29 Jan 2006, Trond Myklebust stipulated:
> As a general rule of thumb: if tcpdump/ethereal can see the reply on the
> client, then the engine socket should see it too. If tcpdump is indeed
> seeing those replies, you should check the RPC code by
> setting /proc/sys/sunrpc/rpc_debug to 1.
tcpdump is seeing them.
... have a pile of messages in the midst of a locked-up transfer:
Jan 30 16:50:57 loki warning: kernel: -pid- proc flgs status -client- -prog- --rqstp- -timeout -rpcwait -action- --exit--
Jan 30 16:50:57 loki warning: kernel: 15046 0006 0021 -00011 c1a11600 100003 c801f000 00000000 xprt_resend c02c3798 c01c0e4d
Jan 30 16:50:57 loki warning: kernel: 15047 0006 0021 000000 c1a11600 100003 c801f0b8 00000070 xprt_pending c02c3869 c01c0e4d
Jan 30 16:50:57 loki warning: kernel: 15048 0006 0021 -00011 c1a11600 100003 c801f170 00000000 xprt_resend c02c3798 c01c0e4d
Jan 30 16:50:57 loki warning: kernel: 15049 0006 0001 -00011 c1a11600 100003 c801f228 00000000 xprt_sending c02c3798 c01c0e4d
Jan 30 16:50:57 loki warning: kernel: RPC: 15047 xprt_timer
Jan 30 16:50:57 loki warning: kernel: RPC: cong 256, cwnd was 256, now 256
Jan 30 16:50:57 loki warning: kernel: RPC: 15048 xprt_cwnd_limited cong = 0 cwnd = 256
Jan 30 16:50:57 loki warning: kernel: RPC: 15048 xprt_prepare_transmit
Jan 30 16:50:57 loki warning: kernel: RPC: 15048 xprt_transmit(116)
Jan 30 16:50:57 loki warning: kernel: RPC: 15048 xmit complete
Jan 30 16:50:57 loki warning: kernel: RPC: 15047 xprt_prepare_transmit
Jan 30 16:50:57 loki warning: kernel: RPC: 15047 xprt_cwnd_limited cong = 256 cwnd = 256
Jan 30 16:50:57 loki warning: kernel: RPC: 15047 failed to lock transport c1a11800
Jan 30 16:50:58 loki warning: kernel: RPC: 15048 xprt_timer
Jan 30 16:50:58 loki warning: kernel: RPC: cong 256, cwnd was 256, now 256
Jan 30 16:50:58 loki warning: kernel: RPC: 15046 xprt_cwnd_limited cong = 0 cwnd = 256
Jan 30 16:50:58 loki warning: kernel: RPC: 15046 xprt_prepare_transmit
Jan 30 16:50:58 loki warning: kernel: RPC: 15046 xprt_transmit(116)
Jan 30 16:50:58 loki warning: kernel: RPC: 15046 xmit complete
Jan 30 16:50:58 loki warning: kernel: RPC: 15048 xprt_prepare_transmit
Jan 30 16:50:58 loki warning: kernel: RPC: 15048 xprt_cwnd_limited cong = 256 cwnd = 256
Jan 30 16:50:58 loki warning: kernel: RPC: 15048 failed to lock transport c1a11800
Jan 30 16:50:59 loki warning: kernel: RPC: 15046 xprt_timer
Jan 30 16:50:59 loki warning: kernel: RPC: cong 256, cwnd was 256, now 256
Jan 30 16:50:59 loki warning: kernel: RPC: 15047 xprt_cwnd_limited cong = 0 cwnd = 256
Jan 30 16:50:59 loki warning: kernel: RPC: 15047 xprt_prepare_transmit
Jan 30 16:50:59 loki warning: kernel: RPC: 15047 xprt_transmit(116)
Jan 30 16:50:59 loki warning: kernel: RPC: 15047 xmit complete
Jan 30 16:50:59 loki warning: kernel: RPC: 15046 xprt_prepare_transmit
Jan 30 16:50:59 loki warning: kernel: RPC: 15046 xprt_cwnd_limited cong = 256 cwnd = 256
Jan 30 16:50:59 loki warning: kernel: RPC: 15046 failed to lock transport c1a11800
Jan 30 16:51:00 loki warning: kernel: RPC: 15047 xprt_timer
[repeats indefinitely]
Jan 30 16:51:38 loki warning: kernel: -pid- proc flgs status -client- -prog- --rqstp- -timeout -rpcwait -action- --exit--
Jan 30 16:51:38 loki warning: kernel: 15046 0006 0021 -00011 c1a11600 100003 c801f000 00000000 xprt_resend c02c3798 c01c0e4d
Jan 30 16:51:38 loki warning: kernel: 15047 0006 0021 000000 c1a11600 100003 c801f0b8 00000140 xprt_pending c02c3869 c01c0e4d
Jan 30 16:51:38 loki warning: kernel: 15048 0006 0021 -00011 c1a11600 100003 c801f170 00000000 xprt_resend c02c3798 c01c0e4d
The RPC messages are emitted at pretty much exactly the same frequency
as the ACKs.
I *guess* that the `failed to lock transport' is the underlying error...
time to add some debugging and find out what task is locking the
transport. Back soon, must rebuild the kernel and reboot to clear this
lock ;)
--
`I won't make a secret of the fact that your statement/question
sent a wave of shock and horror through us.' --- David Anderson
next prev parent reply other threads:[~2006-01-30 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 22:52 2.6.15.1: persistent nasty hang in sync_page killing NFS (ne2k-pci / DP83815-related?), i686/PIII Nix
2006-01-29 1:59 ` Trond Myklebust
2006-01-29 14:24 ` Nix
2006-01-29 19:56 ` Nix
2006-01-29 20:21 ` Trond Myklebust
2006-01-29 21:54 ` Nix
2006-01-29 22:02 ` Trond Myklebust
2006-01-30 16:55 ` Nix [this message]
2006-01-30 17:09 ` Trond Myklebust
2006-01-30 17:31 ` 2.6.15.1: UDP fragments >27208 bytes lost with ne2k-pci on DP83815 (was Re: persistent nasty hang in sync_page killing NFS (ne2k-pci / DP83815-related?), i686/PIII) Nix
2006-01-30 19:03 ` thockin
2006-01-30 19:07 ` 2.6.15.1: UDP fragments >27208 bytes lost with ne2k-pci on DP83815 Nix
2006-01-30 19:32 ` thockin
2006-01-30 19:49 ` Nix
2006-01-30 22:18 ` Nix
2006-01-30 19:36 ` 2.6.15.1: persistent nasty hang in sync_page killing NFS(ne2k-pci / DP83815-related?), i686/PIII Roger Heflin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874q3lwt7w.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@hockin.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox