Strange network behavior

Bug #85520 reported by Daniel Comşa
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

My wired network card stops working from time to time. Bringing the interface down then up again doesn't solve the problem. Rebooting the laptop does solve the problem sometimes. This is really random, and I don't know yet how to reproduce it.

Here's a sniff from kernel log:
Feb 16 10:49:25 daniel-laptop kernel: [17179732.132000] NETDEV WATCHDOG: eth0: transmit timed out
Feb 16 10:49:28 daniel-laptop kernel: [17179735.144000] eth0: Transmit timeout, status 0d 0000 c07f media d0.
Feb 16 10:49:28 daniel-laptop kernel: [17179735.144000] eth0: Tx queue start entry 4 dirty entry 0.
Feb 16 10:49:28 daniel-laptop kernel: [17179735.144000] eth0: Tx descriptor 0 is 0008206e. (queue head)
Feb 16 10:49:28 daniel-laptop kernel: [17179735.144000] eth0: Tx descriptor 1 is 0008206e.
Feb 16 10:49:28 daniel-laptop kernel: [17179735.144000] eth0: Tx descriptor 2 is 0008206e.
Feb 16 10:49:28 daniel-laptop kernel: [17179735.144000] eth0: Tx descriptor 3 is 0008204e.
Feb 16 10:49:28 daniel-laptop kernel: [17179735.144000] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

I have also seen a similar behavior on bug# 76489. Just when I wanted to try the workaround suggested there, the network card started working again.

Here are the specs:

# uname -a
Linux daniel-laptop 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux

# lspci -v // wired network part only
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
        Subsystem: ASUSTeK Computer Inc. Unknown device 1045
        Flags: bus master, medium devsel, latency 64, IRQ 201
        I/O ports at d800 [size=256]
        Memory at fe8fdc00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2

If you need other informations, please let me know

Revision history for this message
Daniel Comşa (daniel-comsa) wrote :

i have attached the kernel log

Revision history for this message
Rog (roger-mindsocket) wrote :

This happens for me too since upgrading to feisty (kernel 2.6.20-8), on a machine with an RL-8139 onboard NIC. The one major difference is that the behaviour always happens and occurs immediately on boot up.

Revision history for this message
Rog (roger-mindsocket) wrote :

More info...

uname -a
Linux cheese 2.6.20-8-generic #2 SMP ...

lspci -v excerpt
01:09.0 Ethernet controller: Realtek Semiconductor Cp., Ltd. RTL-8139/8139C/8139C+ (rev 10)
        Subsystem: Unknown device 1919:1001
        Flags: bus master, medium devsel, latency 32, IRQ 18
        I/O ports at b800 [size=256]
        Memory at fe5ff800 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2

Kernel log matches the pattern reported by Daniel.

Revision history for this message
Martey Dodoo (martey) wrote :

Can confirm on 2.6.20. Issue occurs with both wired and wireless.

uname -a:
Linux imperium 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

sudo lspci -v excerpt:
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 11)
        Subsystem: IBM Unknown device 0577
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at b0200000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable-
        Capabilities: [d0] Express Endpoint IRQ 0
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel

0b:02.0 Network controller: Intel Corporation PRO/Wireless 2915ABG Network Connection (rev 05)
        Subsystem: Intel Corporation Unknown device 1010
        Flags: bus master, medium devsel, latency 64, IRQ 22
        Memory at b4001000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2

Changed in linux-source-2.6.20:
status: Unconfirmed → Confirmed
Revision history for this message
Martey Dodoo (martey) wrote :

Unconfirming - my issue seems to be with DNS resolution, and not with the cards themselves.

Changed in linux-source-2.6.20:
status: Confirmed → Unconfirmed
Revision history for this message
Kyle McMartin (kyle) wrote :

What about modprobe -r the module, and then reloading it? Does that help at all? Unfortunately this might just be bad hardware, or a bad driver. r8139 is a rather old driver, so it's more likely that your hardware just sporadically fails.

Cheers,
  Kyle

Changed in linux-source-2.6.20:
status: Unconfirmed → Needs Info
Revision history for this message
Rog (roger-mindsocket) wrote : Re: [Bug 85520] Re: Strange network behavior

I'll give it a go and report back , but I don't expect much to change. It has worked absolutely flawlessly from Warty
through Edgy, and a Dapper live CD confirms that this is still the case.

* On Thu, Mar 08, 2007 at 12:40:46AM -0000, Kyle McMartin <email address hidden> wrote:
> What about modprobe -r the module, and then reloading it? Does that help
> at all? Unfortunately this might just be bad hardware, or a bad driver.
> r8139 is a rather old driver, so it's more likely that your hardware
> just sporadically fails.
>
> Cheers,
> Kyle
>
> ** Changed in: linux-source-2.6.20 (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> Strange network behavior
> https://launchpad.net/bugs/85520

--
- Rog

Revision history for this message
Rog (roger-mindsocket) wrote :

I dist-upgraded last night (via a live CD), and booted with the irqpoll option this morning and the network card is now working. Not an ideal workaround, but I'm happier for it.

This also resolved my SATA disk issue as per bug 78288, so it seems my issue is around interrupts in 2.6.20, the 2.6.17 issue may be a different one.
https://launchpad.net/bugs/78288

Revision history for this message
Ben Collins (ben-collins) wrote :

There's a very good chance this is a bug in your BIOS. Maybe check for an update.

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Changed in linux-source-2.6.17:
status: Confirmed → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

However, please note that this report will remain open against the actively developed kernel. Thank you for your continued support and help as we debug this issue.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result we are closing the linux-source-2.6.20 task. Additionally, we have not received any feedback to any of the previous inquiries. I'm closing the "linux" task until we hear back. Thanks.

Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Changed in linux:
status: Incomplete → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.