| Summary: | [abrt] kernel: irq 10: nobody cared (try booting with the "irqpoll" option) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sylvain Arth <sylvain> | ||||
| 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 | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:ad0987033674dc7746ee58edbb779127ad7cb8d9 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-07-12 15:45:32 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
Sylvain Arth
2011-11-26 19:39:39 UTC
Created attachment 536893 [details]
File: smolt_data
It seems that the interrupt for the sound card got stuck and then disabled. Can you provide the full dmesg and /proc/interrupts output fro this machine? You might want to look for a BIOS update for your machine as well. Frankly apart the trace above nothing bad happened to my box. Needless to say I don't own any more any copy of the dmesg and /proc/interrupts output relative to. Maybe next time I will catch them. Updating the BIOS is no more an issue to me, because it's an old MB. At least I can say I had no such outputs with 2.6 Kernels Can you attach the output of dmesg and /proc/interrupts? Also, do you see this on the 3.1.9 or 3.2.1 kernel updates? I thought I already attached a dmesg output at least I will do again with a /proc/interrupts as well when I fix the hard drive failure I had since (Murphy's law probably). That means I could not see wiith the latest kernels. But what I'm sure of, I still got the "crash" with the irqpoll set at boot time. I checked the BIOS settings too. IRQ 10 isn't relative to any device at all but lokked both "Reserved" and "Disabled" If you can still reproduce this in 3.4, please reopen. We believe this should be fixed with the current updates. |