Realtek 8139 ethernet card defect (acpi related)

[Manfred]

Pentium 5
Ubuntu 5.1 32bit PC
Ethernet Card: Realtek Semiconductor Co., Ltd. RTL-8139

After a fresh installation of ubuntu the the ethernet stack is not working. (Same for live CD).

The ethernet card works under other OSs on the same HW (debian, windows XP).

-------- PCI info --------
root@ubuntu:~# lspci | grep -i eth
0000:00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

-------- physical layer --------
root@ubuntu:~# mii-tool eth0
eth0: negotiated 100baseTx-FD flow-control, link ok

-------- software driver --------
root@ubuntu:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:E0:7D:74:1C:17
          inet addr:10.1.1.2 Bcast:10.1.1.255 Mask:255.255.255.0
          inet6 addr: fe80::2e0:7dff:fe74:1c17/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0xa000

-------- driver loaded --------
root@ubuntu:~# lsmod | grep mii
mii 5248 2 8139too,8139cp

-------- find router --------
root@ubuntu:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth0

-------- ping router --------
root@ubuntu:~# ping 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
From 10.1.1.2 icmp_seq=2 Destination Host Unreachable
From 10.1.1.2 icmp_seq=3 Destination Host Unreachable
From 10.1.1.2 icmp_seq=4 Destination Host Unreachable
From 10.1.1.2 icmp_seq=6 Destination Host Unreachable
From 10.1.1.2 icmp_seq=7 Destination Host Unreachable
From 10.1.1.2 icmp_seq=8 Destination Host Unreachable

--- 10.1.1.1 ping statistics ---
9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8000ms
, pipe 3

-------- ping 10.1.1.2 --------
works

-------- ifconfig after ping --------
root@ubuntu:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:7D:74:1C:17
          inet addr:10.1.1.2 Bcast:10.1.1.255 Mask:255.255.255.0
          inet6 addr: fe80::2e0:7dff:fe74:1c17/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0xa000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:8547 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8547 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:546915 (534.0 KiB) TX bytes:546915 (534.0 KiB)

-------- /etc/network/interface --------
root@ubuntu:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
        script grep
        map eth0

# The primary network interface
iface eth0 inet static
        address 10.1.1.2
        netmask 255.255.255.0
        network 10.1.1.0
        broadcast 10.1.1.255
        gateway 10.1.1.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 10.1.1.1

booting with kernel option pci=noacpi solves the problem

[Sitsofe Wheeler (sitsofe)]

First of all, are you sure that 10.1.1.1 isn't firewalling ping packets (is it running a firewall at all?)

Secondly does doing
ping -I eth0 10.1.1.1
yield a different result?

Is there anything interesting in
dmesg | tail

[Manfred (manfred-nzbox)]

 > First of all, are you sure that 10.1.1.1 isn't firewalling ping packets
 > (is it running a firewall at all?)
Yes I am sure there is no firewalling ping packets, because the card works proper after
booting with option pci=noacpi

 > Secondly does doing
 > ping -I eth0 10.1.1.1
 > yield a different result?
no - same result

 > Is there anything interesting in
 > dmesg | tail
-------- dmesg --------
mf@ubuntu:~$ dmesg | grep eth0
[4294676.337000] eth0: RealTek RTL8139 at 0xa000, 00:e0:7d:74:1c:17, IRQ 11
[4294676.337000] eth0: Identified 8139 chip type 'RTL-8139A'
[4294703.536000] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[4294787.536000] NETDEV WATCHDOG: eth0: transmit timed out
[4294787.536000] eth0: Transmit timeout, status 0c 0005 c07f media 80.
[4294787.536000] eth0: Tx queue start entry 4 dirty entry 0.
[4294787.536000] eth0: Tx descriptor 0 is 0008a03c. (queue head)
[4294787.536000] eth0: Tx descriptor 1 is 0008a03c.
[4294787.536000] eth0: Tx descriptor 2 is 0008a03c.
[4294787.536000] eth0: Tx descriptor 3 is 0008a03c.
[4294787.536000] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

mf@ubuntu:~$ dmesg | grep 8139
[4294676.335000] 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
[4294676.335000] 8139cp: pci dev 0000:00:06.0 (id 10ec:8139 rev 10) is not an 8139C+
compatible chip
[4294676.335000] 8139cp: Try the "8139too" driver instead.
[4294676.337000] 8139too Fast Ethernet driver 0.9.27
[4294676.337000] eth0: RealTek RTL8139 at 0xa000, 00:e0:7d:74:1c:17, IRQ 11
[4294676.337000] eth0: Identified 8139 chip type 'RTL-8139A'

Sitsofe Wheeler wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35683
>
> Comment:
> First of all, are you sure that 10.1.1.1 isn't firewalling ping packets
> (is it running a firewall at all?)
>
> Secondly does doing
> ping -I eth0 10.1.1.1
> yield a different result?
>
> Is there anything interesting in
> dmesg | tail

[gmlion (gm-l)]

Try using the "irqpoll" kernel option

[Sebastian Rode (sebastian-ro-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Manfred (manfred-nzbox)]

Hi Sebastian,

> We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release?
No - hardware is not longer available, therefore I can't test with
latest ubuntu.

Cheers
Manfred

On 3/01/2008, at 10:48 PM, Sebastian Rode wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in advance.
>
> ** Changed in: gnome-network (Ubuntu)
> Status: New => Incomplete
>
> --
> Realtek 8139 ethernet card defect (acpi related)
> https://bugs.launchpad.net/bugs/35683
> You received this bug notification because you are a direct subscriber
> of the bug.

[parkblock (parkblock)]

I receive the 'try the "8139too" driver instead' message in the logs when attempting to install gutsy gibbon (7.10) on my system. I have tried adding the "irqpoll" option without success. I have found other forums/threads that indicate that there is a conflict between the 8139cp driver and the 8139too driver - is there any way from the ubuntu setup options screen to specify one over the other?

My current windows install shows my network adapter to be "Realtek 8139/810x Family Fast Ethernet NIC"

Thanks in advance -

Parkblock

[Leann Ogasawara (leannogasawara)]

Hi Parkblock,

Care to open a new bug report. It seems you are experiencing a different bug. I'll be closing this report for now as the original bug reporter no longer has hardware available to test. Thanks.