From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA Rhine ethernet driver bug
Date: Mon, 17 Jan 2005 10:04:27 -0200 [thread overview]
Message-ID: <20050117120427.GA20370@logos.cnet> (raw)
In-Reply-To: <001001c4faf7$71a26230$450aa8c0@hierzo>
On Sat, Jan 15, 2005 at 12:43:33PM +0100, Udo van den Heuvel wrote:
> Hello,
>
> On my firewall (VIA EPIA CL-6000 with VIA Rhine network chips running FC3
> and custom kernels) I see messages like:
>
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
> buffers, entry 0x4 length 0 status 00000600!
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame ccf80040 vs
> ccf80040.
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
> buffers, entry 0x5 length 0 status 00000400!
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame ccf80050 vs
> ccf80050.
>
> [...]
>
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
> buffers, entry 0xf length 0 status 00000400!
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame ccf800f0 vs
> ccf800f0.
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
> buffers, entry 0x0 length 0 status 00000400!
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame ccf80000 vs
> ccf80000.
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
> buffers, entry 0x1 length 0 status 00000400!
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame ccf80010 vs
> ccf80010.
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
> buffers, entry 0x2 length 0 status 00000400!
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame ccf80020 vs
> ccf80020.
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame spanned multiple
> buffers, entry 0x3 length 0 status 00000581!
> Jan 13 19:35:46 epia kernel: eth1: Oversized Ethernet frame ccf80030 vs
> ccf80030.
>
> every 3 or 4 days or so when I really use the card. (please notice all 16
> entries are used and the length is 0)
> Eth1 is connected to an Alcatel Speedtouch Home at 10 Mbits, Half Duplex.
> This problem did not occur when I wsa using other hardware for the firewall.
>
> While googlin' I saw that this is an old bug which was not fixed for years.
> I am in contact with the maintainer and currently am trying to see what
> effect a smaller mtu and/or older driver versions might have.
>
> Because of the impact of this nasty bug (many users have these chips in
> their hardware) I would like to ask if others could have a look into this
> problem as well. Please email me your experiences (2.6.x kernel? Same bug or
> no problem? Fixes? Etc).
> PLEASE help!
What kernel version are you using? Its important to inform that.
next prev parent reply other threads:[~2005-01-17 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 11:43 VIA Rhine ethernet driver bug Udo van den Heuvel
2005-01-17 12:04 ` Marcelo Tosatti [this message]
2005-01-17 15:45 ` Luc Saillard
2005-01-18 16:55 ` Udo van den Heuvel
2005-03-09 20:49 ` jerome lacoste
-- strict thread matches above, loose matches on Subject: below --
2005-01-16 15:31 Udo van den Heuvel
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=20050117120427.GA20370@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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