mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James E Lucas <jelucas@utdallas.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: natsemi.c: Oversized(?) ethernet frame message w/ card hang
Date: 04 Feb 2003 22:44:43 +0000	[thread overview]
Message-ID: <1044398683.29825.2.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <4280608.1044393822565.JavaMail.jelucas@utdallas.edu>

On Tue, 2003-02-04 at 21:23, James E Lucas wrote:
> 
> And, my kernel ring buffer (dmesg) is showing messages like this:
> 
> eth0: Oversized(?) Ethernet frame spanned multiple buffers, entry 
> 0x00ba8b status 0xe0000bd5.

By strange co-incidence I saw this with natsemi on one of my boxes
today. 

> numbers of large UDP packets at the card to reproduce the breakage.  If 
> anyone's interested in it I could post it up somewhere, though it's not 
> very pretty ;)

I'd love a copy

> from National Semiconductor *seems* to indicate to me that this message 
> results from a packet spanning multiple descriptors in the hardware.  
> This *is* legal for the chip according to National's docs, but I can't 
> find anything in the driver that seems to acknowledge this beyond the 
> warning message.  My current working theory is that this doesn't happen

Our drivers post buffers larger than an ethernet packet to the card so
it means the card thinks it received a frame larger than anything it
should have accepted.

> very often, but when it does, the driver's not handling it properly.  
> What I'm not so sure on is why that hangs the card.  Perhaps it's 
> throwing the driver into an infinite loop or something.  Not really 

If it got stuck in a loop the box would hang. It appears to stop the
chip and it never restarts.

My card that did this is also an FA-311. I've only ever seen this once
however so I guess my network isnt loaded enough 8)




  reply	other threads:[~2003-02-04 21:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 21:23 James E Lucas
2003-02-04 22:44 ` Alan Cox [this message]
2003-02-04 23:22 James E Lucas

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=1044398683.29825.2.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jelucas@utdallas.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®