Bug 1388220 - [abrt] irq 7: nobody cared (try booting with the "irqpoll" option) [NEEDINFO]
Summary: [abrt] irq 7: nobody cared (try booting with the "irqpoll" option)
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:2cc633c9ccec3bbd9f1b499e10e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-24 18:58 UTC by kermgraham
Modified: 2017-04-28 17:28 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:28:42 UTC
Type: ---
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (58.25 KB, text/plain)
2016-10-24 18:58 UTC, kermgraham
no flags Details
JPG image of console at time of crash (179.91 KB, image/jpeg)
2016-11-02 05:37 UTC, Michael Carney
no flags Details

Description kermgraham 2016-10-24 18:58:16 UTC
Description of problem:
Cinnamon desktop crashed on startup. Rebooted and started correctly.

Additional info:
reporter:       libreport-2.7.1
irq 7: nobody cared (try booting with the "irqpoll" option)
CPU: 0 PID: 1432 Comm: gdbus Not tainted 4.5.5-300.fc24.x86_64 #1
Hardware name: HP Pavilion 061 RJ181AA-ABA a1600n/NODUSM3, BIOS  3.06 07/14/2006
 0000000000000086 00000000e9c18fe7 ffff8800bfa03e48 ffffffff813d35af
 ffff8800bf42d800 ffff8800bf42d89c ffff8800bfa03e78 ffffffff811018f5
 ffff8800bf42d800 0000000000000000 0000000000000000 0000000000000000
Call Trace:
 <IRQ>  [<ffffffff813d35af>] dump_stack+0x63/0x84
 [<ffffffff811018f5>] __report_bad_irq+0x35/0xc0
 [<ffffffff81101c74>] note_interrupt+0x234/0x270
 [<ffffffff810feed6>] handle_irq_event_percpu+0x156/0x1c0
 [<ffffffff810fef6c>] handle_irq_event+0x2c/0x50
 [<ffffffff811023b3>] handle_level_irq+0x83/0x100
 [<ffffffff81019e13>] handle_irq+0x73/0x120
 [<ffffffff810aac4d>] ? irq_exit+0x8d/0x110
 [<ffffffff817d18eb>] do_IRQ+0x4b/0xd0
 [<ffffffff817cf78c>] common_interrupt+0x8c/0x8c

Potential duplicate: bug 1213013

Comment 1 kermgraham 2016-10-24 18:58:26 UTC
Created attachment 1213545 [details]
File: dmesg

Comment 2 Michael Carney 2016-11-02 05:37:15 UTC
Created attachment 1216345 [details]
JPG image of console at time of crash

Comment 3 Michael Carney 2016-11-02 05:54:15 UTC
Additional info to go with console image:

I started seeing this problem only after I booted 4.8.4. It occurs as the system is going down as part of a reboot.

Details: F24, Dell Precision T1700 Workstation, 16 GB memory, Nvidia Quadro K600,
Adaptec 29320 ALP scsi, SATA disk drives.

Other info: I have a HP DAT 72 scsi tape drive attached to the 29320; this equipment is unusable under 4.8.4 -- works on previous versions of the kernel. Common thread here is 4.8.4. Symptoms: mt commands hang, tape drive won't load/unload tape.

Comment 4 Justin M. Forbes 2017-04-11 15:03:10 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are 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 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  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 5 Justin M. Forbes 2017-04-28 17:28:42 UTC
*********** MASS BUG UPDATE **************
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.