Bug 771119

Summary:	[abrt] kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Product:	[Fedora] Fedora	Reporter:	Thomas Meyer <thomas.mey>
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:	x86_64
OS:	Unspecified
Whiteboard:	abrt_hash:90cd6bd707a78da3c406a797c7bda3387a503a78
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-12 15:44:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Thomas Meyer 2012-01-01 16:49:39 UTC

libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        BOOT_IMAGE=/vmlinuz-3.1.6 root=/dev/sda2 rootfstype=ext4 rootflags=data=writeback ro quiet rhgb
comment:        Resumed from ram.
kernel:         3.1.6
reason:         irq 16: nobody cared (try booting with the "irqpoll" option)
time:           Sa 31 Dez 2011 18:53:37 CET

backtrace:
:irq 16: nobody cared (try booting with the "irqpoll" option)
:Pid: 2329, comm: upowerd Not tainted 3.1.6 #14
:Call Trace:
: <IRQ>  [<ffffffff8107fdf4>] __report_bad_irq+0x24/0xb0
: [<ffffffff81080026>] note_interrupt+0x156/0x200
: [<ffffffff8107e946>] handle_irq_event_percpu+0x86/0x150
: [<ffffffff8107ea33>] handle_irq_event+0x23/0x40
: [<ffffffff81080876>] handle_fasteoi_irq+0x46/0xc0
: [<ffffffff8148753a>] ? call_softirq+0x1a/0x30
: [<ffffffff8100387d>] handle_irq+0x1d/0x30
: [<ffffffff81003772>] do_IRQ+0x52/0xd0
: [<ffffffff81480e69>] common_interrupt+0x69/0x69
: <EOI>  [<ffffffff811a1557>] ? mls_range_isvalid+0x67/0x70
: [<ffffffff81195313>] ? sidtab_context_to_sid+0x93/0x420
: [<ffffffff8119c17a>] ? string_to_context_struct+0x1ba/0x2f0
: [<ffffffff8119c3e4>] security_context_to_sid_core+0x134/0x210
: [<ffffffff8119dcdf>] security_context_to_sid_default+0xf/0x20
: [<ffffffff8118f11d>] inode_doinit_with_dentry+0x32d/0x5e0
: [<ffffffff8118f3e7>] selinux_d_instantiate+0x17/0x20
: [<ffffffff811858b6>] security_d_instantiate+0x16/0x30
: [<ffffffff810e1d86>] d_instantiate+0x36/0x50
: [<ffffffff810e1de4>] d_splice_alias+0x44/0xc0
: [<ffffffff81144116>] ext4_lookup+0xb6/0x120
: [<ffffffff810d7ee0>] d_alloc_and_lookup+0x40/0x80
: [<ffffffff810e3610>] ? d_lookup+0x30/0x50
: [<ffffffff810d8461>] do_lookup+0x2b1/0x3a0
: [<ffffffff810da342>] ? link_path_walk+0x62/0x800
: [<ffffffff810db9e0>] do_last+0xe0/0x8f0
: [<ffffffff810dc2fc>] path_openat+0xcc/0x3a0
: [<ffffffff810dc6dd>] do_filp_open+0x3d/0xa0
: [<ffffffff81188f6a>] ? selinux_cred_prepare+0x1a/0x40
: [<ffffffff8104f766>] ? prepare_creds+0x86/0x170
: [<ffffffff81186421>] ? security_prepare_creds+0x11/0x20
: [<ffffffff810d3f5d>] open_exec+0x2d/0xf0
: [<ffffffff810d465e>] do_execve_common+0x11e/0x330
: [<ffffffff810d48ef>] compat_do_execve+0x3f/0x50
: [<ffffffff81025292>] sys32_execve+0x42/0x70
: [<ffffffff81487b85>] ia32_ptregs_common+0x25/0x4b

Comment 1 Josh Boyer 2012-01-24 19:11:25 UTC

This seems to have been generated with a self-compiled kernel.  However, we have a number of similar reports in Fedora for the 3.1.[23456] kernel vintage.

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?

Comment 2 Dave Jones 2012-03-22 16:41:42 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 3 Dave Jones 2012-03-22 16:46:23 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 4 Dave Jones 2012-03-22 16:55:44 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 5 Dave Jones 2012-07-12 15:44:36 UTC

If you can still reproduce this in 3.4, please reopen. We believe this should be fixed with the current updates.