[lkml]   [2000]   [Dec]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectrtl8139 driver broken? (2.2.16)

[please CC replies; I am not on the list]

I have a 2.2.16 kernel on an HP Omnibook 800 CT with docking station. That
docking station contains an Allied Telesyn 2500TX NIC, identified by lspci
as "Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10)". Versions 1.07
(RedHat 7.0) and 1.08 (SuSE 7.0) exhibit the same behaviour.

The network is set up correctly - I can ping without problems,
but the connection to the external network simply "stops working" after a
while as soon as I do something more exciting.

Examples of failure when the rtl8139 driver is used:

// (sometimes) works for ages

ping -s 5000
// makes network die almost instantaneously
// after that, all outbound traffic just does
// not get through

get <largish file>
// makes network die almost instantaneously

The network is resurrected by /etc/rc.d/[init.d/]network restart. This
happens both with the stock kernel + modules shipped with RedHat 7.0, a
default SuSE 7.0 setup, and a self-built kernel + modules based on SuSE

I do not see any kernel messages indicating any failure anywhere; only on
boot do I get "neighbour table overflow" (4x), but the NIC works

When I insert a PCMCIA NIC and use the network over *that* card,
everything works fine forever ("ifconfig eth0 down", then "ifconfig eth1

Fiddling with BIOS options (PnP, PCI bridge configuration) does not seem
to have any effect.

* Is the rtl8139 driver broken?
* Is there some kind of problem with the docking station (bridge)?

FWIW, this combination ran perfectly fine with Windows NT4 SP3...

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.042 / U:30.996 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site