| Summary: | [abrt] kernel: irq 18: nobody cared (try booting with the "irqpoll" option) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tommi R. <tra> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, ofbugsandmen | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:ca3961d2e0102b5f26f5af1935c88e5f611e3157 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-07-12 15:46:20 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Tommi R.
2012-03-10 23:12:00 UTC
Created attachment 569137 [details]
File: smolt_data
More information to this: after updating to newer kernel: Linux anjo 3.2.9-2.fc16.x86_64 #1 SMP Mon Mar 5 20:55:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux this behavior went away. But there are very often messages in /var/log/messages like: Mar 14 16:05:59 anjo kernel: [88737.586287] Disabling IRQ 18 Mar 14 16:05:59 anjo kernel: [88737.596030] Polling IRQ 18 Mar 14 16:06:00 anjo kernel: [88738.596262] Reenabling IRQ 18 The period how often this happens is now typically less than 1 minute! And disabling IRQ message is emergency message, as default to wall everybody, so I needed to change this behavior to get emergency messages to go only one file. However, everything seems to work, even also the external network, and interrupt of this network interface card pin A is routed to IRQ 18! MB has the latest bios, I updated it already about 2 weeks ago from original, but not seeing any difference. (In reply to comment #2) > More information to this: after updating to newer kernel: > Linux anjo 3.2.9-2.fc16.x86_64 #1 SMP Mon Mar 5 20:55:39 UTC 2012 x86_64 x86_64 > x86_64 GNU/Linux > this behavior went away. > But there are very often messages in /var/log/messages like: > Mar 14 16:05:59 anjo kernel: [88737.586287] Disabling IRQ 18 > Mar 14 16:05:59 anjo kernel: [88737.596030] Polling IRQ 18 > Mar 14 16:06:00 anjo kernel: [88738.596262] Reenabling IRQ 18 These messages will be gone in the kernel that is in updates-testing. Created attachment 570007 [details]
/proc/interrupts
Created attachment 570010 [details]
lspci -vvv output
Right now I can not boot computer and test the later kernel from testing reposity, but I can attach these two files if they can be helpful to investigate this. I'm not sure if this is duplicate of other bug, I saw similar ones.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. Hello, It seems that I'm hitting the same bug running F17 Linux hex 3.4.4-3.fc17.x86_64 #1 SMP Tue Jun 26 20:54:56 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux I have a Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) in one of PCI slots of Asus E45M1-M PRO motherboard and see plentiful IRQ 19 might be stuck. Polling messages in dmesg output. Also the card seems to be periodically loosing link. I access the machine remotely and after I get disconnected and re-connect I see 8139too 0000:06:01.0: p5p1: link up, 100Mbps, full-duplex, lpa 0x41E1 message in dmesg. This bug is tagged with NEEDINFO, but I do not see any information requests. What can I do to help you to squash this bug? Pawel, That sounds like a different bug. Please file a separate report for it. If you can still reproduce this in 3.4, please reopen. We believe this should be fixed with the current updates. |