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
> 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)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 07 2003 - 22:00:15 EST