mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* VIA Rhine ethernet driver bug (any progress?)
@ 2005-04-08 17:13 Udo van den Heuvel
  0 siblings, 0 replies; only message in thread
From: Udo van den Heuvel @ 2005-04-08 17:13 UTC (permalink / raw)
  To: linux-kernel

Hello,

Did anyone make progress in the case of the VIA Rhine ethernet bug?

It gives messages like:

Apr  8 18:51:08 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x9 length 0 status 00000600!
Apr  8 18:51:08 epia kernel: eth1: Oversized Ethernet frame cca77090 vs
cca77090.
Apr  8 18:51:08 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0xa length 0 status 00000400!
Apr  8 18:51:08 epia kernel: eth1: Oversized Ethernet frame cca770a0 vs
cca770a0.

[....]

Apr  8 18:51:08 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x7 length 0 status 00000400!
Apr  8 18:51:08 epia kernel: eth1: Oversized Ethernet frame cca77070 vs
cca77070.
Apr  8 18:51:08 epia kernel: eth1: Oversized Ethernet frame spanned multiple
buffers, entry 0x8 length 24436 status 5f748d10!
Apr  8 18:51:08 epia kernel: eth1: Oversized Ethernet frame cca77080 vs
cca77080.


Most of the time the ethernet connection is gone and needs and ifconfig
down/up or reboot to make it work again.
I see this error on a VIA EPIA CL-6000 board. Using google I see the
mentionings of the error messages in relation to VIA Rhine go back to 1999.
The other side of eth1 is an Alcatel Speedtouch Home. With different
firewall hardware (Tulip DT5/xxx but same Alcatel) I did not see the errors.

Any ideas? A patch to gather more info so the bug can be fixed?
Etc?

Please post!

Info:

eth0: VIA Rhine III at 0x1d000, 00:40:63:d6:xx:xx, IRQ 11.
eth1: VIA Rhine II at 0x1e800, 00:40:63:d6:xx:xx, IRQ 9.

Linux epia 2.6.11-rc1-mm2 #2 Sat Jan 22 10:51:45 CET 2005 i686 i686 i386
GNU/Linux

00:0f.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev
8b)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev
74)

# cat /proc/interrupts
           CPU0
  0:    5739616          XT-PIC  timer
  1:         78          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  3:         12          XT-PIC  serial
  4:         12          XT-PIC  serial
  8:          1          XT-PIC  rtc
  9:     804990          XT-PIC  VIA8233, uhci_hcd, uhci_hcd, eth1
 11:     493428          XT-PIC  HiSax, ehci_hcd, uhci_hcd, eth0
 12:        512          XT-PIC  i8042
 14:     453632          XT-PIC  ide0
 15:      50784          XT-PIC  ide1
NMI:          0
ERR:          1

(the ERR value has a relation to the bug? I just rebooted the box and the
error occurred once...)

# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10Mb/s
        Duplex: Half
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000001 (1)
        Link detected: yes


Kind regards,
Udo



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-04-08 17:15 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-04-08 17:13 VIA Rhine ethernet driver bug (any progress?) Udo van den Heuvel

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®