Bug 875859 - Call trace logged on Macmini5,1, __report_bad_irq
Summary: Call trace logged on Macmini5,1, __report_bad_irq
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-12 17:11 UTC by Mads Kiilerich
Modified: 2013-03-28 15:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-28 15:00:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg (94.26 KB, application/octet-stream)
2012-11-12 17:11 UTC, Mads Kiilerich
no flags Details

Description Mads Kiilerich 2012-11-12 17:11:53 UTC
Created attachment 643634 [details]
dmesg

abrt wanted to report this ... but failed. Bug 875852.

[    8.211067] irq 17: nobody cared (try booting with the "irqpoll" option)
[    8.211071] Pid: 0, comm: swapper/0 Not tainted 3.6.6-1.fc17.x86_64 #1
[    8.211072] Call Trace:
[    8.211073]  <IRQ>  [<ffffffff810e9dad>] __report_bad_irq+0x3d/0xe0
[    8.211081]  [<ffffffff810ea0a9>] note_interrupt+0x1a9/0x200
[    8.211085]  [<ffffffff8106c480>] ? run_timer_softirq+0x180/0x350
[    8.211087]  [<ffffffff810e78d7>] handle_irq_event_percpu+0xa7/0x1f0
[    8.211089]  [<ffffffff810e7a61>] handle_irq_event+0x41/0x70
[    8.211091]  [<ffffffff810eaba9>] handle_fasteoi_irq+0x59/0x100
[    8.211094]  [<ffffffff810150ff>] handle_irq+0xbf/0x150
[    8.211097]  [<ffffffff81621732>] ? __atomic_notifier_call_chain+0x12/0x20
[    8.211099]  [<ffffffff81621756>] ? atomic_notifier_call_chain+0x16/0x20
[    8.211102]  [<ffffffff8162730a>] do_IRQ+0x5a/0xe0
[    8.211104]  [<ffffffff8161dbea>] common_interrupt+0x6a/0x6a
[    8.211105]  <EOI>  [<ffffffff813373fd>] ? intel_idle+0xed/0x150
[    8.211110]  [<ffffffff813373de>] ? intel_idle+0xce/0x150
[    8.211114]  [<ffffffff814ca599>] cpuidle_enter+0x19/0x20
[    8.211115]  [<ffffffff814cac29>] cpuidle_idle_call+0xa9/0x250
[    8.211118]  [<ffffffff8101c52f>] cpu_idle+0xaf/0x120
[    8.211120]  [<ffffffff815fa37e>] rest_init+0x72/0x74
[    8.211123]  [<ffffffff81cfbc3a>] start_kernel+0x3c7/0x3d4
[    8.211125]  [<ffffffff81cfb672>] ? repair_env_string+0x5e/0x5e
[    8.211127]  [<ffffffff81cfb356>] x86_64_start_reservations+0x131/0x135
[    8.211129]  [<ffffffff81cfb45a>] x86_64_start_kernel+0x100/0x10f
[    8.211130] handlers:
[    8.211133] [<ffffffffa0130c60>] sdhci_irq [sdhci]
[    8.211134] Disabling IRQ #17

See also
Bug 728916 - Call Trace __report_bad_irq on irq 17 on Mac mini Core i5 EFI
which seemed to have gone away.

Comment 1 Josh Boyer 2013-03-12 18:54:07 UTC
Are you still seeing this with 3.7.9 or 3.8.2 in updates-testing?

Comment 2 Josh Boyer 2013-03-28 15:00:43 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 weeks.  If you are still experiencing this issue,
please reopen and attach the relevant data from the latest kernel you are
running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.