public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sun, 29 Jan 2006 14:24:55 +0000	[thread overview]
Message-ID: <87slr79knc.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <1138499957.8770.91.camel@lade.trondhjem.org> (Trond Myklebust's message of "Sat, 28 Jan 2006 20:59:17 -0500")

On Sat, 28 Jan 2006, Trond Myklebust stipulated:
> On Sat, 2006-01-28 at 22:52 +0000, Nix wrote:
> 
>> tcpdumps and the kernel's packet counters on both sides show NFS packets
>> flowing, and being retried, over and over again:
> 
> Are you using an Intel motherboard? If so, it could be the IPMI bug

The motherboard's an ASUS CUV4X, with VIA almost-everything. I think
this is the first mobo I've had in a decade that doesn't even have an
Intel PIIX bridge on it.

(One other machine in the house has VIA almost-everything as well, and
exhibits none of these problems.)

> http://blogs.sun.com/roller/page/shepler?entry=port_623_or_the_mount

That's specific to one port. As the capture (from the server side this
time) shows, the NFS client is using all sorts of ports on the client,
and port 2049 on the server; acks are not required, this being UDP.

I'm going to rebuild with NFS-over-TCP support and see if that changes
anything next. A bit pointless on a clean switched network, but it's
hardly going to be noticeable...

I'll get another network card on Monday and swap out the DP83815, and
see if *that* changes anything.

-- 
`I won't make a secret of the fact that your statement/question
 sent a wave of shock and horror through us.' --- David Anderson

  reply	other threads:[~2006-01-29 14:25 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 [this message]
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
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=87slr79knc.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