[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
I think I'm seeing the same issue, but not sure. Let me know if I should file a new bug: ``` [31816.378948] bad: scheduling from the idle thread! [31816.378950] CPU: 19 PID: 0 Comm: swapper/19 Tainted: GW OEL 4.4.0-21-generic #37-Ubuntu [31816.378950] Hardware name: Supermicro SYS-F618R2-RC0PT+/X10DRFR-NT, BIOS 2.0 01/27/2016 [31816.378952] 0286 43008b208dbadff6 882fa6283e18 813e93c3 [31816.378953] 885fbec56d00 882fa6283e30 810b1d2c [31816.378954] 885fbec56d00 882fa6283e58 810aacc1 0001ff10 [31816.378954] Call Trace: [31816.378956] [] dump_stack+0x63/0x90 [31816.378958] [] dequeue_task_idle+0x2c/0x40 [31816.378959] [] deactivate_task+0x81/0xa0 [31816.378961] [] __schedule+0x5cf/0xa10 [31816.378961] [] schedule+0x35/0x80 [31816.378962] [] schedule_preempt_disabled+0xe/0x10 [31816.378964] [] cpu_startup_entry+0x191/0x350 [31816.378965] [] start_secondary+0x154/0x190 ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: Triaged Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] []
[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
That patch was released in Ubuntu-4.4.0-35.54 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: Triaged Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478379] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478383] [] blk_mq_rq_timer+0x41/0xf0 Sep 22 15:51:46 ubuntu kernel: [ 97.478389] [] call_timer_fn+0x35/0x120 Sep 22 15:51:46 ubuntu kernel: [ 97.478393] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478397] [] run_timer_softirq+0x23a/0x2f0 Sep 22 15:51:46 ubuntu kernel: [ 97.478403] [] __do_softirq+0x101/0x290 Sep 22 15:51:46 ubuntu kernel: [ 97.478407] [] irq_exit+0xa3/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478413] [] smp_apic_timer_interrupt+0x42/0x50 Sep 22 15:51:46 ubuntu kernel: [ 97.478417] [] apic_timer_interrupt+0x82/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478419][] ? cpuidle_enter_state+0x111/0x2b0 Sep 22 15:51:46 ubuntu kernel: [ 97.478428] [] cpuidle_enter+0x17/0x20 Sep 22
[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
A couple issues here. The nvme driver was ported from 4.5, but the block layer was based on 4.4, so there was a mismatch in how to handle timeouts. That was this launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908 But also, there is a bug handling legacy IRQ that only affected the 4.5 version of this driver, and that was fixed in commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=a5229050b69cfffb690b546c357ca5a60434c0c8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: Triaged Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478379] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478383] [] blk_mq_rq_timer+0x41/0xf0 Sep 22 15:51:46 ubuntu kernel: [ 97.478389] [] call_timer_fn+0x35/0x120 Sep 22 15:51:46 ubuntu kernel: [ 97.478393] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478397] [] run_timer_softirq+0x23a/0x2f0 Sep 22 15:51:46 ubuntu kernel: [ 97.478403] []
[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
Paul - have you confirmed that you are no longer seeing the issue? If yes, please update this bug with the info. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: Triaged Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478379] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478383] [] blk_mq_rq_timer+0x41/0xf0 Sep 22 15:51:46 ubuntu kernel: [ 97.478389] [] call_timer_fn+0x35/0x120 Sep 22 15:51:46 ubuntu kernel: [ 97.478393] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478397] [] run_timer_softirq+0x23a/0x2f0 Sep 22 15:51:46 ubuntu kernel: [ 97.478403] [] __do_softirq+0x101/0x290 Sep 22 15:51:46 ubuntu kernel: [ 97.478407] [] irq_exit+0xa3/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478413] [] smp_apic_timer_interrupt+0x42/0x50 Sep 22 15:51:46 ubuntu kernel: [ 97.478417] [] apic_timer_interrupt+0x82/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478419][] ? cpuidle_enter_state+0x111/0x2b0 Sep 22 15:51:46
[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
There isn't a kernel in proposed at the moment, but I've tested using the latest in yakkety and it seems to be working fine. I don't have a simple replication case for the bug, unfortunately. It just seems to happen for (hand-wavey guess) 50% of boots. So far I've got this 4.8.0-19-generic kernel to boot several times over without problem. I'll keep rebooting and rebooting the server in the background today, just in case, while I focus on other stuff. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: Triaged Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478379] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478383] [] blk_mq_rq_timer+0x41/0xf0 Sep 22 15:51:46 ubuntu kernel: [ 97.478389] [] call_timer_fn+0x35/0x120 Sep 22 15:51:46 ubuntu kernel: [ 97.478393] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478397] [] run_timer_softirq+0x23a/0x2f0 Sep 22 15:51:46 ubuntu kernel: [ 97.478403] [] __do_softirq+0x101/0x290 Sep 22
[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
Can you test the Yakkety proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: Triaged Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478379] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478383] [] blk_mq_rq_timer+0x41/0xf0 Sep 22 15:51:46 ubuntu kernel: [ 97.478389] [] call_timer_fn+0x35/0x120 Sep 22 15:51:46 ubuntu kernel: [ 97.478393] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478397] [] run_timer_softirq+0x23a/0x2f0 Sep 22 15:51:46 ubuntu kernel: [ 97.478403] [] __do_softirq+0x101/0x290 Sep 22 15:51:46 ubuntu kernel: [ 97.478407] [] irq_exit+0xa3/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478413] [] smp_apic_timer_interrupt+0x42/0x50 Sep 22 15:51:46 ubuntu
[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: Confirmed Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478379] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478383] [] blk_mq_rq_timer+0x41/0xf0 Sep 22 15:51:46 ubuntu kernel: [ 97.478389] [] call_timer_fn+0x35/0x120 Sep 22 15:51:46 ubuntu kernel: [ 97.478393] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478397] [] run_timer_softirq+0x23a/0x2f0 Sep 22 15:51:46 ubuntu kernel: [ 97.478403] [] __do_softirq+0x101/0x290 Sep 22 15:51:46 ubuntu kernel: [ 97.478407] [] irq_exit+0xa3/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478413] [] smp_apic_timer_interrupt+0x42/0x50 Sep 22 15:51:46 ubuntu kernel: [ 97.478417] [] apic_timer_interrupt+0x82/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478419][] ? cpuidle_enter_state+0x111/0x2b0 Sep 22 15:51:46 ubuntu kernel: [ 97.478428] []
[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
gzip'd copy of the kern.log showing the error. ** Attachment added: "kern.log.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626679/+attachment/4746377/+files/kern.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: New Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478379] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478383] [] blk_mq_rq_timer+0x41/0xf0 Sep 22 15:51:46 ubuntu kernel: [ 97.478389] [] call_timer_fn+0x35/0x120 Sep 22 15:51:46 ubuntu kernel: [ 97.478393] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478397] [] run_timer_softirq+0x23a/0x2f0 Sep 22 15:51:46 ubuntu kernel: [ 97.478403] [] __do_softirq+0x101/0x290 Sep 22 15:51:46 ubuntu kernel: [ 97.478407] [] irq_exit+0xa3/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478413] [] smp_apic_timer_interrupt+0x42/0x50 Sep 22 15:51:46 ubuntu kernel: [ 97.478417] [] apic_timer_interrupt+0x82/0x90 Sep 22 15:51:46 ubuntu kernel: [
