Re: VIA Rhine ethernet driver bug

[Marcelo Tosatti]

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/