Description of problem: Booting with this SCSI card installed: 01:05.0 SCSI storage controller: Advanced Micro Devices [AMD] 53c974 [PCscsi] (rev 10) Flags: bus master, stepping, medium devsel, latency 64, IRQ 16 I/O ports at bc00 [size=128] [virtual] Expansion ROM at fdf00000 [disabled] [size=64K] Kernel driver in use: tmscsim I suspect that the driver didn't get modernized when something changed in the kernel a few years ago. Additional info: reporter: libreport-2.1.4 WARNING: at kernel/irq/handle.c:146 handle_irq_event_percpu+0x1de/0x1f0() Hardware name: Aspire E380 irq 16 handler do_DC390_Interrupt+0x0/0x9c0 [tmscsim] enabled interrupts Modules linked in: ata_generic pata_acpi usb_storage firewire_ohci nouveau mxm_wmi wmi video i2c_algo_bit drm_kms_helper ttm drm i2c_core sata_nv pata_amd firewire_core crc_itu_t tmscsim Pid: 0, comm: swapper/1 Not tainted 3.9.4-200.fc18.x86_64 #1 Call Trace: <IRQ> [<ffffffff8105f125>] warn_slowpath_common+0x75/0xa0 [<ffffffff8105f206>] warn_slowpath_fmt+0x46/0x50 [<ffffffffa0002430>] ? dc390_MsgIn_0+0x570/0x570 [tmscsim] [<ffffffff810efd3e>] handle_irq_event_percpu+0x1de/0x1f0 [<ffffffff810efd91>] handle_irq_event+0x41/0x70 [<ffffffff810f2fa9>] handle_fasteoi_irq+0x59/0x100 [<ffffffff810161af>] handle_irq+0xbf/0x150 [<ffffffff81665952>] ? __atomic_notifier_call_chain+0x12/0x20 [<ffffffff81665976>] ? atomic_notifier_call_chain+0x16/0x20 [<ffffffff8166bb9a>] do_IRQ+0x5a/0xe0 [<ffffffff81661bad>] common_interrupt+0x6d/0x6d <EOI> [<ffffffff81044136>] ? native_safe_halt+0x6/0x10 [<ffffffff8101c651>] default_idle+0x41/0x100 [<ffffffff8101c769>] amd_e400_idle+0x59/0x120 [<ffffffff8101d17e>] cpu_idle+0xfe/0x120 [<ffffffff81650d21>] start_secondary+0x24f/0x251
Created attachment 754193 [details] File: dmesg
*********** 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 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. 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 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** 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. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.
Created attachment 908293 [details] dmesg output with the same kernel warning This was from Fedora 20 on the same hardware. Look at line 766 for the start of the kernel report. [ 3.211359] WARNING: CPU: 1 PID: 0 at kernel/irq/handle.c:146 handle_irq_event_percpu+0x1bb/0x1d0() Kernel version 3.14.5-200.fc20.x86_64
Are you still seeing this with 3.16.7 or newer?
Sorry for the delay. I had to put together a new machine for this because the original machine died. I'm getting this error in F20 with kernel 3.17.2.fc20. Please reopen. ABRT takes me here and then says the bug is CLOSED CURRENTRELEASE. Consequently it won't upload a report. This is the same bug as bz 1087719. That's where ABRT takes me (but it wont upload a report because that bz is currently CLOSED CURRENTRELEASE).
Created attachment 958770 [details] dmesg output after booting 3.17.2-200.fc20 dmesg output after booting 3.17.2-200.fc20
*********** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.18.7-100.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 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.