Bug 751637
Summary: | NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christopher Murtagh <christopher.murtagh> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | fredericg_99, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-11-07 17:46:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christopher Murtagh
2011-11-06 18:21:41 UTC
Ok, after disabling IPv6 (and ip6tables), I still had the same problem several hours later: [39816.520107] irq 17: nobody cared (try booting with the "irqpoll" option) [39816.520114] Pid: 0, comm: swapper Tainted: G W 2.6.40.8-4.fc15.x86_64 #1 [39816.520116] Call Trace: [39816.520119] <IRQ> [<ffffffff810af848>] __report_bad_irq+0x38/0xc3 [39816.520131] [<ffffffff810afadf>] note_interrupt+0x173/0x1f0 [39816.520135] [<ffffffff810ae116>] handle_irq_event_percpu+0x15d/0x1a5 [39816.520138] [<ffffffff810ae196>] handle_irq_event+0x38/0x56 [39816.520145] [<ffffffff810754dc>] ? sched_clock_cpu+0x42/0xc6 [39816.520148] [<ffffffff810b0278>] handle_fasteoi_irq+0x77/0x9b [39816.520153] [<ffffffff8100ab6d>] handle_irq+0x88/0x8e [39816.520157] [<ffffffff81490a9d>] do_IRQ+0x4d/0xa5 [39816.520162] [<ffffffff81488cd3>] common_interrupt+0x13/0x13 [39816.520164] <EOI> [<ffffffff8100e975>] ? paravirt_read_tsc+0x9/0xd [39816.520174] [<ffffffff812848a0>] ? intel_idle+0xd8/0x100 [39816.520177] [<ffffffff81284882>] ? intel_idle+0xba/0x100 [39816.520183] [<ffffffff813b0169>] cpuidle_idle_call+0xd7/0x168 [39816.520188] [<ffffffff81008307>] cpu_idle+0xa5/0xdf [39816.520193] [<ffffffff81467c8e>] rest_init+0x72/0x74 [39816.520198] [<ffffffff81b66b8b>] start_kernel+0x3ca/0x3d5 [39816.520203] [<ffffffff81b662c4>] x86_64_start_reservations+0xaf/0xb3 [39816.520207] [<ffffffff81b66140>] ? early_idt_handlers+0x140/0x140 [39816.520210] [<ffffffff81b663ca>] x86_64_start_kernel+0x102/0x111 [39816.520213] handlers: [39816.520223] [<ffffffffa01cc292>] rtl8169_interrupt [39816.520226] Disabling IRQ #17 [39840.635863] r8169 0000:04:01.0: eth1: link up [39870.591319] r8169 0000:04:01.0: eth1: link up So, it looks like reverting back to 2.6.38 is what I'm going to have to do (I can't afford to have this particular machine go down like that). *** This bug has been marked as a duplicate of bug 715137 *** |