Bug 1383820

Summary: [abrt] irq 19: nobody cared (try booting with the "irqpoll" option)
Product: [Fedora] Fedora Reporter: Giulio 'juliuxpigface' <juliux.pigface>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: candan, chabot.daniel.01, fomink, gansalmon, ichavero, itamar, jonathan, jripolles, juliux.pigface, kernel-maint, luca, madhu.chinakonda, maskimko, mchehab, mwc, psmis
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/84cb24dc35e91fd54b7f0926c155a5fcab895eed
Whiteboard: abrt_hash:fa5c546feb6a336830525066603acf60e9867537;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-23 23:01:48 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 Flags
File: dmesg none

Description Giulio 'juliuxpigface' 2016-10-11 21:00:16 UTC
Description of problem:
I found the abrt's notify after a reboot, I'm not sure when did this *exactly* occur.

Additional info:
reporter:       libreport-2.8.0
irq 19: nobody cared (try booting with the "irqpoll" option)
CPU: 0 PID: 468 Comm: (mount) Not tainted 4.8.1-1.fc25.i686+PAE #1
Hardware name: Acer             Extensa 5200    /Grapevine, BIOS V3.50 02/13/2007
 d8638967 7513003e 00000086 f483ff7c d7f5c840 f4ad6c00 f4ad6c60 f483ff9c
 d7ccbabf d85405d4 00000013 d86a9f00 f77cfa94 f4ad6c00 00000000 f483ffc0
 d7ccbe2d d1f6d6ee 00000008 00000000 00000013 f4ad6c00 00000000 d7ccc480
Call Trace:
 [<d7f5c840>] dump_stack+0x58/0x78
 [<d7ccbabf>] __report_bad_irq+0x2f/0xd0
 [<d7ccbe2d>] note_interrupt+0x20d/0x250
 [<d7ccc480>] ? handle_untracked_irq+0xb0/0xb0
 [<d7cc925a>] handle_irq_event_percpu+0x4a/0x70
 [<d7cc92a7>] handle_irq_event+0x27/0x40
 [<d7ccc4f8>] handle_fasteoi_irq+0x78/0x140
 [<d7c24b33>] handle_irq+0xa3/0xd0
 <IRQ>  [<d7c242cc>] do_IRQ+0x3c/0xc0
 [<d8357573>] common_interrupt+0x33/0x38
 [<d7de007b>] ? SyS_chdir+0x7b/0xc0
 [<d7deea0f>] ? link_path_walk+0xaf/0x500
 [<d7decd3e>] ? path_init+0x19e/0x330
 [<d7de3ecf>] ? get_empty_filp+0xbf/0x1c0
 [<d7defc82>] path_openat+0xc2/0x10b0
 [<d7df0dc4>] ? putname+0x54/0x60
 [<d7df0dc4>] ? putname+0x54/0x60
 [<d821deb6>] ? pci_conf1_read+0xa6/0xf0
 [<d7c71ace>] ? irq_exit+0x6e/0xb0
 [<d7c242d5>] ? do_IRQ+0x45/0xc0
 [<d8221980>] ? pci_read+0x30/0x40
 [<d7df1de8>] do_filp_open+0x68/0xe0
 [<d7dff37e>] ? __alloc_fd+0x2e/0x130
 [<d7de0ae2>] do_sys_open+0x112/0x1f0
 [<d7c4acb9>] ? irq_complete_move+0x19/0x20
 [<d7c4b81b>] ? ioapic_ack_level+0x5b/0x110
 [<d7de0be2>] SyS_open+0x22/0x30
 [<d7c037ad>] do_fast_syscall_32+0x8d/0x140
 [<d8356df2>] sysenter_past_esp+0x47/0x75

Potential duplicate: bug 1098621

Comment 1 Giulio 'juliuxpigface' 2016-10-11 21:00:27 UTC
Created attachment 1209322 [details]
File: dmesg

Comment 2 krdondon 2016-11-28 09:24:30 UTC
Description of problem:
Full computer shutdown ..
First boot ..

Version-Release number of selected component:
kernel-core-4.8.10-300.fc25

Additional info:
reporter:       libreport-2.8.0
cmdline:        BOOT_IMAGE=/boot/vmlinuz-4.8.10-300.fc25.x86_64 root=UUID=0fd6922b-eb91-4b8d-a3aa-8050dce83379 ro rhgb quiet LANG=ko_KR.UTF-8
kernel:         4.8.10-300.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
irq 16: nobody cared (try booting with the "irqpoll" option)
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.8.10-300.fc25.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. B85M-HD3-A/B85M-HD3-A, BIOS F2 08/10/2015
 0000000000000086 aaeb5bebde4a9256 ffff887edf203e60 ffffffffb03e5ead
 ffff887ed26a1c00 ffff887ed26a1c9c ffff887edf203e90 ffffffffb01001a5
 ffff887ed26a1c00 0000000000000000 ffff887ed26a1c00 0000000000000071
Call Trace:
 <IRQ>  [<ffffffffb03e5ead>] dump_stack+0x63/0x86
 [<ffffffffb01001a5>] __report_bad_irq+0x35/0xc0
 [<ffffffffb0100524>] note_interrupt+0x234/0x270
 [<ffffffffb00fd6d4>] handle_irq_event_percpu+0x54/0x80
 [<ffffffffb00fd72c>] handle_irq_event+0x2c/0x50
 [<ffffffffb0100c7a>] handle_fasteoi_irq+0x8a/0x150
 [<ffffffffb0028df3>] handle_irq+0x73/0x120
 [<ffffffffb00c1c5a>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffffb08053eb>] do_IRQ+0x4b/0xd0
 [<ffffffffb080328c>] common_interrupt+0x8c/0x8c
 <EOI>  [<ffffffffb06893f2>] ? cpuidle_enter_state+0x122/0x2c0
 [<ffffffffb06895c7>] cpuidle_enter+0x17/0x20
 [<ffffffffb00e534a>] call_cpuidle+0x2a/0x50
 [<ffffffffb00e5730>] cpu_startup_entry+0x2a0/0x350
 [<ffffffffb07f52c7>] rest_init+0x77/0x80
 [<ffffffffb0f7ffeb>] start_kernel+0x45f/0x480
 [<ffffffffb0f7f120>] ? early_idt_handler_array+0x120/0x120
 [<ffffffffb0f7f2ca>] x86_64_start_reservations+0x24/0x26
 [<ffffffffb0f7f419>] x86_64_start_kernel+0x14d/0x170

Comment 3 krdondon 2016-12-06 00:51:02 UTC
*** Bug 1401747 has been marked as a duplicate of this bug. ***

Comment 4 Maksym Sh 2017-01-01 22:19:26 UTC
*** Bug 1409437 has been marked as a duplicate of this bug. ***

Comment 5 Laura Abbott 2017-01-17 01:11:54 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 6 Laura Abbott 2017-02-23 23:01:48 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 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.

Comment 7 Giulio 'juliuxpigface' 2017-05-01 16:46:16 UTC
Sorry for the delay... For the record, I'm not hitting this anymore. It's solved here.