Fedora 20 CPU soft lockup under load #2679
Comments
|
Although I haven't looked closely, this immediately reminds me of #2523. |
|
Yes, this looks very much like a duplicate of #2523. @greg-hydrogen By chance have you been able to consistently reproduce this? I've had a terrible time reproducing so we can get it resolved. |
|
@behlendorf - I haven't tried actually but when I get back from vacation (Monday) I will try again, I did see something like this before so we may be lucky in that I can reproduce... before I try do you want me to add the debug patch? |
|
@greg-hydrogen if you could add the debugging patches that would be very helpful. That way we'll learn something if you're able to hit it again. |
|
ok will do ... I will let you know if anything turns up... |
|
I had another lockup as well, but I haven't had the chance to add the debug patch, I will do that today, but for completeness here is the stack output... Sep 16 10:42:10 zfs-storage kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 |
|
ok debug patch has been installed... @behlendorf is there anything I need to do when this locks up to grab all the debug info? |
|
ok I had another failure, unfortunately the picture I took didn't come out, I did manage to get a sysreq wlt so hopefully this is enough info to go by.... |
|
@greg-hydrogen Thanks for the additional information. I'm still working on determining the root cause here, but I definitely plan to treat this is a blocker for 0.6.4. |
|
Hello Everyone, just had another crash... and here is the dump I have left the machine in its current state so I can dump further information if needed... I will need to reboot tomorrow night though.. dmesg journalctl |
|
@greg-hydrogen Thanks, any additional debugging is always helpful. In the last case I think it was pretty clear this is somehow a use-after-free bug so I'm going to pursue that angle. Feel free to put your machine back in service. |
|
Hi, We're seeing several issues with lockups/oops with stacks that look similar the ones in this issue (above). We have a Ceph cluster of 6 machines, all running ZFS with around 10 spindles per zpool (configured with xattr=sa). The machines are running RHEL. I have tried experimenting with kernel versions 2.6.32 and 3.17, using zfs/spl from git. After some load, we observe either these lockups (which lead to deadlock of any FS activity, even non-zfs file-systems, requiring hard boot), or we observe the machine self rebooting. Below are some samples of stacks. Let me know if you'd like me to try something or more information: another case: |
|
This is yet another duplicate of #2523 which is targeted to be addressed in the next tag. |
It is known that mutexes in Linux are not safe when using them to synchronize the freeing of object in which the mutex is embedded: http://lwn.net/Articles/575477/ The known places in ZFS which are suspected to suffer from the race condition are zio->io_lock and dbuf->db_mtx. * zio uses zio->io_lock and zio->io_cv to synchronize freeing between zio_wait() and zio_done(). * dbuf uses dbuf->db_mtx to protect reference counting. This patch fixes this kind of race by forcing serialization on mutex_exit() with a spin lock, making the mutex safe by sacrificing a bit of performance and memory overhead. This issue most commonly manifests itself as a deadlock in the zio pipeline caused by a process spinning on the damaged mutex. Similar deadlocks have been reported for the dbuf->db_mtx mutex. And it can also cause a NULL dereference or bad paging request under the right circumstances. This issue any many like it are linked off the openzfs/zfs#2523 issue. Specifically this fix resolves at least the following outstanding issues: openzfs/zfs#401 openzfs/zfs#2523 openzfs/zfs#2679 openzfs/zfs#2684 openzfs/zfs#2704 openzfs/zfs#2708 openzfs/zfs#2517 openzfs/zfs#2827 openzfs/zfs#2850 openzfs/zfs#2891 openzfs/zfs#2897 openzfs/zfs#2247 openzfs/zfs#2939 Signed-off-by: Chunwei Chen <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Signed-off-by: Richard Yao <[email protected]> Closes #421
|
This issue which is a duplicate of #2523 was resolved by the following commit. Full details can be found in the commit message and related lwn article. openzfs/spl@a3c1eb7 mutex: force serialization on mutex_exit() to fix races |
Commit: openzfs/zfs@a3c1eb7 From: Chunwei Chen <[email protected]> Date: Fri, 19 Dec 2014 11:31:59 +0800 Subject: mutex: force serialization on mutex_exit() to fix races It is known that mutexes in Linux are not safe when using them to synchronize the freeing of object in which the mutex is embedded: http://lwn.net/Articles/575477/ The known places in ZFS which are suspected to suffer from the race condition are zio->io_lock and dbuf->db_mtx. * zio uses zio->io_lock and zio->io_cv to synchronize freeing between zio_wait() and zio_done(). * dbuf uses dbuf->db_mtx to protect reference counting. This patch fixes this kind of race by forcing serialization on mutex_exit() with a spin lock, making the mutex safe by sacrificing a bit of performance and memory overhead. This issue most commonly manifests itself as a deadlock in the zio pipeline caused by a process spinning on the damaged mutex. Similar deadlocks have been reported for the dbuf->db_mtx mutex. And it can also cause a NULL dereference or bad paging request under the right circumstances. This issue any many like it are linked off the openzfs/zfs#2523 issue. Specifically this fix resolves at least the following outstanding issues: openzfs/zfs#401 openzfs/zfs#2523 openzfs/zfs#2679 openzfs/zfs#2684 openzfs/zfs#2704 openzfs/zfs#2708 openzfs/zfs#2517 openzfs/zfs#2827 openzfs/zfs#2850 openzfs/zfs#2891 openzfs/zfs#2897 openzfs/zfs#2247 openzfs/zfs#2939 Signed-off-by: Chunwei Chen <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Signed-off-by: Richard Yao <[email protected]> Backported-by: Darik Horn <[email protected]> Closes #421 Conflicts: include/sys/mutex.h
It is known that mutexes in Linux are not safe when using them to synchronize the freeing of object in which the mutex is embedded: http://lwn.net/Articles/575477/ The known places in ZFS which are suspected to suffer from the race condition are zio->io_lock and dbuf->db_mtx. * zio uses zio->io_lock and zio->io_cv to synchronize freeing between zio_wait() and zio_done(). * dbuf uses dbuf->db_mtx to protect reference counting. This patch fixes this kind of race by forcing serialization on mutex_exit() with a spin lock, making the mutex safe by sacrificing a bit of performance and memory overhead. This issue most commonly manifests itself as a deadlock in the zio pipeline caused by a process spinning on the damaged mutex. Similar deadlocks have been reported for the dbuf->db_mtx mutex. And it can also cause a NULL dereference or bad paging request under the right circumstances. This issue any many like it are linked off the openzfs/zfs#2523 issue. Specifically this fix resolves at least the following outstanding issues: openzfs/zfs#401 openzfs/zfs#2523 openzfs/zfs#2679 openzfs/zfs#2684 openzfs/zfs#2704 openzfs/zfs#2708 openzfs/zfs#2517 openzfs/zfs#2827 openzfs/zfs#2850 openzfs/zfs#2891 openzfs/zfs#2897 openzfs/zfs#2247 openzfs/zfs#2939 Signed-off-by: Chunwei Chen <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Signed-off-by: Richard Yao <[email protected]> Closes #421
|
@behlendorf This is not a duplicate of #2523. Instead, it is a duplicate of #3091, provided that this deadlock occurred on a multi-socket system. |
It is known that mutexes in Linux are not safe when using them to synchronize the freeing of object in which the mutex is embedded: http://lwn.net/Articles/575477/ The known places in ZFS which are suspected to suffer from the race condition are zio->io_lock and dbuf->db_mtx. * zio uses zio->io_lock and zio->io_cv to synchronize freeing between zio_wait() and zio_done(). * dbuf uses dbuf->db_mtx to protect reference counting. This patch fixes this kind of race by forcing serialization on mutex_exit() with a spin lock, making the mutex safe by sacrificing a bit of performance and memory overhead. This issue most commonly manifests itself as a deadlock in the zio pipeline caused by a process spinning on the damaged mutex. Similar deadlocks have been reported for the dbuf->db_mtx mutex. And it can also cause a NULL dereference or bad paging request under the right circumstances. This issue any many like it are linked off the openzfs/zfs#2523 issue. Specifically this fix resolves at least the following outstanding issues: openzfs/zfs#401 openzfs/zfs#2523 openzfs/zfs#2679 openzfs/zfs#2684 openzfs/zfs#2704 openzfs/zfs#2708 openzfs/zfs#2517 openzfs/zfs#2827 openzfs/zfs#2850 openzfs/zfs#2891 openzfs/zfs#2897 openzfs/zfs#2247 openzfs/zfs#2939 Signed-off-by: Chunwei Chen <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Signed-off-by: Richard Yao <[email protected]> Closes openzfs#421 Conflicts: include/sys/mutex.h
Hello Everyone,
I experienced a lockup during multiple VM suspends from an ESX 5.5 host. I am currently running kernel 3.16.0 with a zfs git build from the 16 August with the Linux AIO patch (wasn't mainlined at the time). I was able to capture the soft lockup as detailed below
[500514.662210] ISO 9660 Extensions: RRIP_1991A
[865464.526832] BUG: soft lockup - CPU#3 stuck for 22s! [z_wr_iss/0:2332]
[865464.526921] Modules linked in: nls_utf8 isofs loop bridge stp llc btrfs kvm_amd kvm nfsd ppdev crct10dif_pclmul crc32_pclmul auth_rpcgss crc32c_intel ghash_clmulni_intel xor r8169 raid6_pq nfs_acl tg3 lockd microcode edac_core serio_raw ptp sp5100_tco pcspkr mii fam15h_power pps_core k10temp edac_mce_amd i2c_piix4 shpchp parport_pc joydev parport asus_atk0110 sunrpc wmi acpi_cpufreq radeon ata_generic pata_acpi i2c_algo_bit drm_kms_helper ttm drm pata_atiixp i2c_core zfs(POE) zunicode(POE) zavl(POE) zcommon(POE) znvpair(POE) spl(OE) [last unloaded: iptable_raw]
[865464.526954] CPU: 3 PID: 2332 Comm: z_wr_iss/0 Tainted: P OE 3.16.0 #1
[865464.526956] Hardware name: System manufacturer System Product Name/M5A78L-M LX PLUS, BIOS 1501 04/27/2013
[865464.526958] task: ffff8800c3fcaee0 ti: ffff8800c3fe0000 task.ti: ffff8800c3fe0000
[865464.526959] RIP: 0010:[] [] _raw_spin_lock+0x1e/0x30
[865464.526964] RSP: 0018:ffff8800c3fe3d48 EFLAGS: 00000202
[865464.526966] RAX: 0000000000000002 RBX: ffffffffa0105559 RCX: ffff88013eec4c20
[865464.526967] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88013eec4f04
[865464.526968] RBP: ffff8800c3fe3d48 R08: 0000000000000000 R09: 0000000000000001
[865464.526970] R10: 0000000000000004 R11: 0000000000000001 R12: ffff88030ad61b80
[865464.526971] R13: ffff8803fc872000 R14: ffff880037a5cb40 R15: 0000000100000000
[865464.526973] FS: 00007fa366cca840(0000) GS:ffff88041ecc0000(0000) knlGS:0000000000000000
[865464.526974] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[865464.526976] CR2: 00007fa366cf7000 CR3: 0000000001c11000 CR4: 00000000000407e0
[865464.526977] Stack:
[865464.526978] ffff8800c3fe3d60 ffffffff8170740c ffff880154d63b10 ffff8800c3fe3d70
[865464.526981] ffffffff8170744b ffff8800c3fe3dc8 ffffffffa0154f7c ffff8800c3fcaee0
[865464.526983] 0000000000000000 ffff8800c3fcaee0 ffff88013eec4f00 0000000000010000
[865464.526985] Call Trace:
[865464.526990] [] __mutex_unlock_slowpath+0x1c/0x40
[865464.526993] [] mutex_unlock+0x1b/0x20
[865464.527031] [] zio_ready+0x1bc/0x400 [zfs]
[865464.527059] [] zio_execute+0xa6/0x140 [zfs]
[865464.527070] [] taskq_thread+0x22d/0x4b0 [spl]
[865464.527074] [] ? wake_up_state+0x20/0x20
[865464.527082] [] ? taskq_cancel_id+0x1f0/0x1f0 [spl]
[865464.527085] [] kthread+0xe1/0x100
[865464.527087] [] ? insert_kthread_work+0x40/0x40
[865464.527090] [] ret_from_fork+0x7c/0xb0
[865464.527092] [] ? insert_kthread_work+0x40/0x40
[865464.527094] Code: b6 17 38 d0 75 f7 eb f0 0f 1f 44 00 00 66 66 66 66 90 55 48 89 e5 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 75 04 5d c3 f3 90 <0f> b6 07 38 d0 75 f7 5d c3 66 0f 1f 84 00 00 00 00 00 66 66 66
[865492.534998] BUG: soft lockup - CPU#3 stuck for 22s! [z_wr_iss/0:2332]
[865492.535086] Modules linked in: nls_utf8 isofs loop bridge stp llc btrfs kvm_amd kvm nfsd ppdev crct10dif_pclmul crc32_pclmul auth_rpcgss crc32c_intel ghash_clmulni_intel xor r8169 raid6_pq nfs_acl tg3 lockd microcode edac_core serio_raw ptp sp5100_tco pcspkr mii fam15h_power pps_core k10temp edac_mce_amd i2c_piix4 shpchp parport_pc joydev parport asus_atk0110 sunrpc wmi acpi_cpufreq radeon ata_generic pata_acpi i2c_algo_bit drm_kms_helper ttm drm pata_atiixp i2c_core zfs(POE) zunicode(POE) zavl(POE) zcommon(POE) znvpair(POE) spl(OE) [last unloaded: iptable_raw]
[865492.535116] CPU: 3 PID: 2332 Comm: z_wr_iss/0 Tainted: P OE 3.16.0 #1
[865492.535117] Hardware name: System manufacturer System Product Name/M5A78L-M LX PLUS, BIOS 1501 04/27/2013
[865492.535119] task: ffff8800c3fcaee0 ti: ffff8800c3fe0000 task.ti: ffff8800c3fe0000
[865492.535121] RIP: 0010:[] [] _raw_spin_lock+0x1e/0x30
[865492.535125] RSP: 0018:ffff8800c3fe3d48 EFLAGS: 00000202
[865492.535127] RAX: 0000000000000002 RBX: ffffffffa0105559 RCX: ffff88013eec4c20
[865492.535128] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88013eec4f04
[865492.535129] RBP: ffff8800c3fe3d48 R08: 0000000000000000 R09: 0000000000000001
[865492.535130] R10: 0000000000000004 R11: 0000000000000001 R12: ffff88030ad61b80
[865492.535132] R13: ffff8803fc872000 R14: ffff880037a5cb40 R15: 0000000100000000
[865492.535133] FS: 00007fa366cca840(0000) GS:ffff88041ecc0000(0000) knlGS:0000000000000000
[865492.535135] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[865492.535136] CR2: 00007fa366cf7000 CR3: 0000000001c11000 CR4: 00000000000407e0
[865492.535137] Stack:
[865492.535138] ffff8800c3fe3d60 ffffffff8170740c ffff880154d63b10 ffff8800c3fe3d70
[865492.535140] ffffffff8170744b ffff8800c3fe3dc8 ffffffffa0154f7c ffff8800c3fcaee0
[865492.535142] 0000000000000000 ffff8800c3fcaee0 ffff88013eec4f00 0000000000010000
[865492.535145] Call Trace:
[865492.535149] [] __mutex_unlock_slowpath+0x1c/0x40
[865492.535152] [] mutex_unlock+0x1b/0x20
[865492.535191] [] zio_ready+0x1bc/0x400 [zfs]
[865492.535216] [] zio_execute+0xa6/0x140 [zfs]
[865492.535226] [] taskq_thread+0x22d/0x4b0 [spl]
[865492.535231] [] ? wake_up_state+0x20/0x20
[865492.535237] [] ? taskq_cancel_id+0x1f0/0x1f0 [spl]
[865492.535240] [] kthread+0xe1/0x100
[865492.535243] [] ? insert_kthread_work+0x40/0x40
[865492.535245] [] ret_from_fork+0x7c/0xb0
[865492.535247] [] ? insert_kthread_work+0x40/0x40
[865492.535248] Code: b6 17 38 d0 75 f7 eb f0 0f 1f 44 00 00 66 66 66 66 90 55 48 89 e5 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 75 04 5d c3 f3 90 <0f> b6 07 38 d0 75 f7 5d c3 66 0f 1f 84 00 00 00 00 00 66 66 66
[865498.595764] INFO: rcu_sched self-detected stall on CPU { 3} (t=60000 jiffies g=7250499 c=7250498 q=12970)
[865498.595896] sending NMI to all CPUs:
[865498.595901] NMI backtrace for cpu 3
[865498.595903] CPU: 3 PID: 2332 Comm: z_wr_iss/0 Tainted: P OE 3.16.0 #1
[865498.595905] Hardware name: System manufacturer System Product Name/M5A78L-M LX PLUS, BIOS 1501 04/27/2013
[865498.595908] task: ffff8800c3fcaee0 ti: ffff8800c3fe0000 task.ti: ffff8800c3fe0000
[865498.595910] RIP: 0010:[] [] __const_udelay+0x12/0x30
[865498.595914] RSP: 0018:ffff88041ecc3de8 EFLAGS: 00000006
[865498.595916] RAX: 0000000001062560 RBX: 0000000000002710 RCX: 0000000000000006
[865498.595917] RDX: 0000000000329399 RSI: 0000000000000002 RDI: 0000000000418958
[865498.595919] RBP: ffff88041ecc3e00 R08: 000000000000000a R09: 0000000000000415
[865498.595920] R10: 0000000000000000 R11: ffff88041ecc3b06 R12: ffffffff81c51b40
[865498.595922] R13: ffffffff81d03f38 R14: ffffffff81c51b40 R15: 0000000000000003
[865498.595924] FS: 00007fa366cca840(0000) GS:ffff88041ecc0000(0000) knlGS:0000000000000000
[865498.595925] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[865498.595927] CR2: 00007fa366cf7000 CR3: 0000000001c11000 CR4: 00000000000407e0
[865498.595928] Stack:
[865498.595929] ffff88041ecc3e00 ffffffff81049132 ffff88041ecce8c0 ffff88041ecc3e58
[865498.595932] ffffffff810f1803 ffff88041ecc3e58 ffffffff810c4331 000312efd075e43e
[865498.595934] 00000000000032aa ffff8800c3fcaee0 0000000000000000 0000000000000003
[865498.595937] Call Trace:
[865498.595939]
[865498.595943] [] ? arch_trigger_all_cpu_backtrace+0xa2/0xd0
[865498.595947] [] rcu_check_callbacks+0x403/0x670
[865498.595950] [] ? account_process_tick+0x121/0x1b0
[865498.595953] [] update_process_times+0x47/0x70
[865498.595957] [] tick_sched_handle.isra.16+0x25/0x60
[865498.595959] [] tick_sched_timer+0x41/0x60
[865498.595962] [] __run_hrtimer+0x73/0x1d0
[865498.595964] [] ? tick_sched_handle.isra.16+0x60/0x60
[865498.595967] [] hrtimer_interrupt+0x107/0x250
[865498.595971] [] local_apic_timer_interrupt+0x37/0x60
[865498.595974] [] smp_apic_timer_interrupt+0x3f/0x60
[865498.595976] [] apic_timer_interrupt+0x6d/0x80
[865498.595978]
[865498.596007] [] ? dva_get_dsize_sync+0x39/0x50 [zfs]
[865498.596010] [] ? _raw_spin_lock+0x1e/0x30
[865498.596013] [] __mutex_unlock_slowpath+0x1c/0x40
[865498.596016] [] mutex_unlock+0x1b/0x20
[865498.596044] [] zio_ready+0x1bc/0x400 [zfs]
[865498.596072] [] zio_execute+0xa6/0x140 [zfs]
[865498.596080] [] taskq_thread+0x22d/0x4b0 [spl]
[865498.596084] [] ? wake_up_state+0x20/0x20
[865498.596091] [] ? taskq_cancel_id+0x1f0/0x1f0 [spl]
[865498.596094] [] kthread+0xe1/0x100
[865498.596097] [] ? insert_kthread_work+0x40/0x40
[865498.596099] [] ret_from_fork+0x7c/0xb0
[865498.596102] [] ? insert_kthread_work+0x40/0x40
[865498.596103] Code: 89 e5 ff 15 49 55 93 00 5d c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 8d 04 bd 00 00 00 00 65 48 8b 14 25 a0 3c 01 00 <48> 89 e5 48 69 d2 fa 00 00 00 f7 e2 48 8d 7a 01 ff 15 10 55 93
[865498.596129] NMI backtrace for cpu 2
[865498.596132] CPU: 2 PID: 0 Comm: swapper/2 Tainted: P OE 3.16.0 #1
[865498.596134] Hardware name: System manufacturer System Product Name/M5A78L-M LX PLUS, BIOS 1501 04/27/2013
[865498.596136] task: ffff8804088ae720 ti: ffff880408914000 task.ti: ffff880408914000
[865498.596138] RIP: 0010:[] [] acpi_idle_do_entry+0x21/0x2b
[865498.596144] RSP: 0018:ffff880408917e20 EFLAGS: 00000093
[865498.596146] RAX: 0003132a985ab400 RBX: ffff8804084094a8 RCX: ffff88041ec91918
[865498.596147] RDX: 0000000000000815 RSI: 0000000000000002 RDI: ffff8804084094a8
[865498.596149] RBP: ffff880408917e20 R08: 00000000ffffffff R09: 0000000000001ccf
[865498.596151] R10: 0000000000001bbf R11: 0000000000000008 R12: ffff880408409400
[865498.596152] R13: 0000000000000002 R14: ffff880407d85200 R15: ffffffff81ca4028
[865498.596154] FS: 00007fa366cca840(0000) GS:ffff88041ec80000(0000) knlGS:0000000000000000
[865498.596156] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[865498.596158] CR2: 00007fa366cf7000 CR3: 00000000c5323000 CR4: 00000000000407e0
[865498.596159] Stack:
[865498.596161] ffff880408917e58 ffffffff81406bdf ffffffff81ca3f60 ffff880407d85200
[865498.596164] ffffffff81ca3f60 000312efd085551c 0000000000000002 ffff880408917e90
[865498.596167] ffffffff81599c80 ffffffff81d03f30 ffff880407d85200 0000000000000002
[865498.596170] Call Trace:
[865498.596174] [] acpi_idle_enter_simple+0xa9/0xd1
[865498.596178] [] cpuidle_enter_state+0x40/0xc0
[865498.596181] [] cpuidle_enter+0x17/0x20
[865498.596184] [] cpu_startup_entry+0x32d/0x460
[865498.596187] [] ? tick_check_new_device+0xda/0xf0
[865498.596192] [] start_secondary+0x220/0x300
[865498.596194] Code: ff fa 66 66 90 66 66 90 5d c3 8a 47 08 55 48 89 e5 3c 01 75 07 e8 c4 cc c3 ff eb 17 3c 02 75 07 e8 ba ff ff ff eb 0c 8b 57 04 ec <48> 8b 15 90 2e bc 00 ed 5d c3 66 66 66 66 90 55 48 63 c2 48 8d
[865498.596230] NMI backtrace for cpu 5
[865498.596240] CPU: 5 PID: 0 Comm: swapper/5 Tainted: P OE 3.16.0 #1
[865498.596246] Hardware name: System manufacturer System Product Name/M5A78L-M LX PLUS, BIOS 1501 04/27/2013
[865498.596251] task: ffff880408920960 ti: ffff880408928000 task.ti: ffff880408928000
[865498.596256] RIP: 0010:[] [] native_safe_halt+0x6/0x10
[865498.596270] RSP: 0018:ffff88040892be00 EFLAGS: 00000246
[865498.596274] RAX: 0000000000000000 RBX: ffff88040840a074 RCX: 0000000000010a78
[865498.596278] RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff88040840a074
[865498.596282] RBP: ffff88040892be00 R08: 00000000ffffffff R09: 0000000000002000
[865498.596286] R10: 0000000000001ea1 R11: 0000000000000008 R12: ffff88040840a000
[865498.596290] R13: 0000000000000001 R14: 0000000000000001 R15: ffffffff81ca3fd0
[865498.596295] FS: 00007ffd6dafd840(0000) GS:ffff88041ed40000(0000) knlGS:0000000000000000
[865498.596299] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[865498.596302] CR2: 00007ffd6db02000 CR3: 00000000c126e000 CR4: 00000000000407e0
[865498.596306] Stack:
[865498.596309] ffff88040892be10 ffffffff81406185 ffff88040892be20 ffffffff81406a93
[865498.596316] ffff88040892be30 ffffffff81406ab7 ffff88040892be58 ffffffff81406b18
[865498.596323] ffff880407d85800 ffffffff81ca3f60 000312efd08577b9 ffff88040892be90
[865498.596330] Call Trace:
[865498.596342] [] arch_safe_halt+0x9/0xd
[865498.596350] [] acpi_safe_halt+0x22/0x2b
[865498.596357] [] acpi_idle_do_entry+0x1b/0x2b
[865498.596364] [] acpi_idle_enter_c1+0x51/0x6f
[865498.596372] [] cpuidle_enter_state+0x40/0xc0
[865498.596378] [] cpuidle_enter+0x17/0x20
[865498.596386] [] cpu_startup_entry+0x32d/0x460
[865498.596392] [] ? tick_check_new_device+0xda/0xf0
[865498.596402] [] start_secondary+0x220/0x300
[865498.596407] Code: 00 00 00 00 00 55 48 89 e5 fa 5d c3 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 fb 5d c3 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 fb f4 <5d> c3 0f 1f 84 00 00 00 00 00 55 48 89 e5 f4 5d c3 66 0f 1f 84
[865498.596473] NMI backtrace for cpu 1
[865498.596483] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P OE 3.16.0 #1
[865498.596488] Hardware name: System manufacturer System Product Name/M5A78L-M LX PLUS, BIOS 1501 04/27/2013
[865498.596494] task: ffff8804088addc0 ti: ffff880408910000 task.ti: ffff880408910000
[865498.596498] RIP: 0010:[] [] acpi_idle_do_entry+0x21/0x2b
[865498.596511] RSP: 0018:ffff880408913e20 EFLAGS: 00000093
[865498.596516] RAX: 0003132a985bd200 RBX: ffff8804084090a8 RCX: ffff88041ec51918
[865498.596519] RDX: 0000000000000815 RSI: 0000000000000002 RDI: ffff8804084090a8
[865498.596523] RBP: ffff880408913e20 R08: 00000000ffffffff R09: 0000000000001eb2
[865498.596527] R10: 0000000000001b76 R11: 0000000000000008 R12: ffff880408409000
[865498.596530] R13: 0000000000000002 R14: ffff880407d85000 R15: ffffffff81ca4028
[865498.596535] FS: 00007fa366cca840(0000) GS:ffff88041ec40000(0000) knlGS:0000000000000000
[865498.596539] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[865498.596543] CR2: 00007fa366bd002c CR3: 0000000001c11000 CR4: 00000000000407e0
[865498.596547] Stack:
[865498.596550] ffff880408913e58 ffffffff81406bdf ffffffff81ca3f60 ffff880407d85000
[865498.596557] ffffffff81ca3f60 000312efd08671dc 0000000000000002 ffff880408913e90
[865498.596564] ffffffff81599c80 ffffffff81d03f30 ffff880407d85000 0000000000000002
[865498.596570] Call Trace:
[865498.596580] [] acpi_idle_enter_simple+0xa9/0xd1
[865498.596589] [] cpuidle_enter_state+0x40/0xc0
[865498.596595] [] cpuidle_enter+0x17/0x20
[865498.596603] [] cpu_startup_entry+0x32d/0x460
[865498.596610] [] ? tick_check_new_device+0xda/0xf0
[865498.596620] [] start_secondary+0x220/0x300
[865498.596625] Code: ff fa 66 66 90 66 66 90 5d c3 8a 47 08 55 48 89 e5 3c 01 75 07 e8 c4 cc c3 ff eb 17 3c 02 75 07 e8 ba ff ff ff eb 0c 8b 57 04 ec <48> 8b 15 90 2e bc 00 ed 5d c3 66 66 66 66 90 55 48 63 c2 48 8d
[865498.596690] NMI backtrace for cpu 0
[865498.596698] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P OE 3.16.0 #1
[865498.596701] Hardware name: System manufacturer System Product Name/M5A78L-M LX PLUS, BIOS 1501 04/27/2013
[865498.596705] task: ffffffff81c18460 ti: ffffffff81c00000 task.ti: ffffffff81c00000
[865498.596708] RIP: 0010:[] [] acpi_idle_do_entry+0x21/0x2b
[865498.596716] RSP: 0018:ffffffff81c03e28 EFLAGS: 00000093
[865498.596719] RAX: 0003132a985bca00 RBX: ffff8804084088a8 RCX: ffff88041ec11918
[865498.596722] RDX: 0000000000000815 RSI: 0000000000000002 RDI: ffff8804084088a8
[865498.596725] RBP: ffffffff81c03e28 R08: 00000000ffffffff R09: 0000000000001eab
[865498.596729] R10: 0000000000001b27 R11: 0000000000000008 R12: ffff880408408800
[865498.596732] R13: 0000000000000002 R14: ffff880407d84e00 R15: ffffffff81ca4028
[865498.596736] FS: 00007f0940beb840(0000) GS:ffff88041ec00000(0000) knlGS:0000000000000000
[865498.596739] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[865498.596742] CR2: 00007faf678e6718 CR3: 00000003d28bc000 CR4: 00000000000407f0
[865498.596745] Stack:
[865498.596747] ffffffff81c03e60 ffffffff81406bdf ffffffff81ca3f60 ffff880407d84e00
[865498.596752] ffffffff81ca3f60 000312efd08669bc 0000000000000002 ffffffff81c03e98
[865498.596764] ffffffff81599c80 ffffffff81d03f30 ffff880407d84e00 0000000000000002
[865498.596774] Call Trace:
[865498.596782] [] acpi_idle_enter_simple+0xa9/0xd1
[865498.596788] [] cpuidle_enter_state+0x40/0xc0
[865498.596793] [] cpuidle_enter+0x17/0x20
[865498.596798] [] cpu_startup_entry+0x32d/0x460
[865498.596807] [] rest_init+0x77/0x80
[865498.596815] [] start_kernel+0x465/0x486
[865498.596820] [] ? set_init_arg+0x53/0x53
[865498.596827] [] ? early_idt_handlers+0x120/0x120
[865498.596833] [] x86_64_start_reservations+0x2a/0x2c
[865498.596839] [] x86_64_start_kernel+0x14d/0x170
[865498.596842] Code: ff fa 66 66 90 66 66 90 5d c3 8a 47 08 55 48 89 e5 3c 01 75 07 e8 c4 cc c3 ff eb 17 3c 02 75 07 e8 ba ff ff ff eb 0c 8b 57 04 ec <48> 8b 15 90 2e bc 00 ed 5d c3 66 66 66 66 90 55 48 63 c2 48 8d
Seems to repeat more or less... if there is more that can help please let me know
The text was updated successfully, but these errors were encountered: