IRQ problem with RTL-8139/8139C/8139C+ ethernet controller

[Marc Tardif]

After installing Feisty Herd 1 on an Intel motherboard model BOXD102GGC2L, the onboard Realtek RTL-8139/8139C/8139C+ ethernet controller is recognized and a network interface eth0 is provided. However, when dhclient attempts to assign a dynamic IP address to the interface, the following error appears in /var/log/syslog:

eth0: link down
irq 20: nobody cared (try booting with the "irqpoll" option)
 [dump_trace+402/448] dump_trace+0x192/0x1c0
 [show_trace_log_lvl+24/48] show_trace_log_lvl+0x18/0x30
 [show_trace+15/32] show_trace+0xf/0x20
 [dump_stack+21/32] dump_stack+0x15/0x20
 [__report_bad_irq+36/128] __report_bad_irq+0x24/0x80
 [note_interrupt+536/592] note_interrupt+0x218/0x250
 [handle_fasteoi_irq+192/208] handle_fasteoi_irq+0xc0/0xd0
 [do_IRQ+105/192] do_IRQ+0x69/0xc0
 [common_interrupt+26/32] common_interrupt+0x1a/0x20
 [phys_startup_32+-1210686939/-1073741824] 0xb7e66225
 =======================
handlers:
[pg0+474102400/1068778496] (rtl8139_interrupt+0x0/0x480 [8139too])
Disabling IRQ #20

So, as mentionned in the error, I tried rebooting with the "irqpoll" kernel option and the network interface worked!

[Ben Collins (ben-collins)]

Please update to the latest kernel in feisty. Currently that is 2.6.20-4

[Cristian Aravena Romero (caravena)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested from https://wiki.ubuntu.com/DebuggingIRQProblems as separate attachments.

[Phillip Lougher (phillip-lougher)]

Ignore the message from Cristian, it's a stock post which doesn't apply here.

Can you test the latest kernel in Feisty, and report whether you've still got the problem? Thanks.

[Ben Collins (ben-collins)]

Marc, here's another one that wasn't sub'd to hw-esc.

[Marc Tardif (cr3)]

Thanks again for catching this bug. I have tested again with the 20070319.1 daily release and the network works as expected:

1. When booting, the network interface is detected and an IP address is assigned by the DHCP server.
2. Running the dhclient command works as expected.

I also checked /var/log/syslog and the message mentionned in my original bug report no longer appears.

[Tim Gardner (timg-tpi)]

Thanks for the update. I'm marking this one fixed.

[Launchpad Janitor (janitor)]

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.