public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: thockin@hockin.org
To: Nix <nix@esperi.org.uk>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.15.1: UDP fragments >27208 bytes lost with ne2k-pci on DP83815
Date: Mon, 30 Jan 2006 11:32:24 -0800	[thread overview]
Message-ID: <20060130193224.GA21500@hockin.org> (raw)
In-Reply-To: <87vew1ttz7.fsf@amaterasu.srvr.nix>

On Mon, Jan 30, 2006 at 07:07:40PM +0000, Nix wrote:
> On Mon, 30 Jan 2006, thockin@hockin.org prattled cheerily:
> > I've never heard anything like that.  I don't have many of these cards
> > around, but Cobalt shipped tens of thousands, and I don't hear of anything
> > resembling this.
> 
> Ah, it's always nice to be first with a bug.
> 
> Any idea how I could go about diagnosing this? (I'm fairly sure it's
> not the server end that's at fault, because that end is sending to other
> machines fine and was sending to this machine fine before it had a
> motherboard and network card change.)
> 
> I've never really dealt with NIC-layer problems before so I don't know
> what beyond printk() is provided, if anything. (Some clues about where
> to stick the printk()s might be useful too, although I can probably find
> them myself in time).

I can't imagine what kind of hidden bug would lay dormant for 4 years and
then pop up for just one person.  I don't know what I can offer except
extra eyes  to vet any potential solutions.  Happt Hunting.


  reply	other threads:[~2006-01-30 19: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
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 [this message]
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=20060130193224.GA21500@hockin.org \
    --to=thockin@hockin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    --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