Hide Forgot
Additional info: reporter: libreport-2.6.4 irq 34: nobody cared (try booting with the "irqpoll" option) CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.6-301.fc23.x86_64 #1 Hardware name: ASUSTeK Computer Inc. B23E/B23E, BIOS B23E.210 11/27/2012 0000000000000086 c91219f98f26651d ffff880235803e48 ffffffff813b542e ffff8800b98f6c00 ffff8800b98f6c9c ffff880235803e70 ffffffff810ff183 ffff8800b98f6c00 0000000000000000 0000000000000022 ffff880235803ea8 Call Trace: <IRQ> [<ffffffff813b542e>] dump_stack+0x63/0x85 [<ffffffff810ff183>] __report_bad_irq+0x33/0xc0 [<ffffffff810ff50e>] note_interrupt+0x23e/0x280 [<ffffffff810fc7b4>] handle_irq_event_percpu+0x164/0x1d0 [<ffffffff810fc84c>] handle_irq_event+0x2c/0x50 [<ffffffff810ffd1f>] handle_edge_irq+0x6f/0x130 [<ffffffff81019de3>] handle_irq+0x73/0x120 [<ffffffff810c35ea>] ? atomic_notifier_call_chain+0x1a/0x20 [<ffffffff817a2ffb>] do_IRQ+0x4b/0xd0 [<ffffffff817a1047>] common_interrupt+0x87/0x87 <EOI> [<ffffffff8163cefe>] ? cpuidle_enter_state+0x10e/0x2b0 [<ffffffff8163ceef>] ? cpuidle_enter_state+0xff/0x2b0 [<ffffffff8163d0d7>] cpuidle_enter+0x17/0x20 [<ffffffff810e65b2>] call_cpuidle+0x32/0x60 [<ffffffff8163d0b3>] ? cpuidle_select+0x13/0x20 [<ffffffff810e6870>] cpu_startup_entry+0x290/0x350 [<ffffffff817947bc>] rest_init+0x7c/0x80 [<ffffffff81d6201e>] start_kernel+0x498/0x4b9 [<ffffffff81d61120>] ? early_idt_handler_array+0x120/0x120 [<ffffffff81d61339>] x86_64_start_reservations+0x2a/0x2c [<ffffffff81d61485>] x86_64_start_kernel+0x14a/0x16d Potential duplicate: bug 1123669
Created attachment 1145985 [details] File: dmesg
How often has this been seen? It looks like the iwl hardware did not start properly
This happens once today, but I don't know whether it will happen again. When it happened, the Wi-Fi status became 'unavailable' or 'disabled by hardware' and I had to restart NetworkManager one or more times to get it connected. It became disconnected after using for a few minutes and I had to restart NetworkManager again to get the connection.
*********** 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 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. 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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
This issue is hard to reproduce, so I am able to provide the requested information unless it really happens again.
This issue is hard to reproduce, so I am not able to provide the requested information unless it really happens again.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.