linux-kernel - Bug in 4.5.0: hard lockups on docker operations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20160314181214.3b7a6a90@goldlack.ei>
Date:	Mon, 14 Mar 2016 18:12:14 +0100
From:	Torsten Luettgert <ml-lkml@...a.eu>
To:	linux-kernel@...r.kernel.org
Subject: Bug in 4.5.0: hard lockups on docker operations

Hello kernel hackers,

I'm still getting hard lockups on my docker machine with overlayfs and
3ware RAID with linux 4.5.0. They look a bit different though.
It would be great if someone could look into it.
Kernel messages follow:

NMI watchdog: Watchdog detected hard LOCKUP on cpu 6
Kernel panic - not syncing: Hard LOCKUP
CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.5.0 #1
Hardware name: Supermicro X8DTT/X8DTT, BIOS 2.1c       04/22/2014
 0000000000000000 ffff880c3fc45b70 ffffffff81430607 ffffffff81cfd8b4
 0000000000000000 ffff880c3fc45be8 ffffffff811c0d96 0000000000000008
 ffff880c3fc45bf8 ffff880c3fc45b98 00000000000000c5 0000000000000046
Call Trace:
 <NMI>  [<ffffffff81430607>] dump_stack+0x63/0x8c
 [<ffffffff811c0d96>] panic+0xd2/0x219
 [<ffffffff81181a80>] watchdog_overflow_callback+0x100/0x100
 [<ffffffff811bd6a8>] __perf_event_overflow+0x88/0x1c0
 [<ffffffff811be144>] perf_event_overflow+0x14/0x20
 [<ffffffff8107c62c>] intel_pmu_handle_irq+0x1cc/0x430
 [<ffffffff814321e9>] ? ioremap_page_range+0x299/0x410
 [<ffffffff8120240c>] ? vunmap_page_range+0x1dc/0x310
 [<ffffffff81202551>] ? unmap_kernel_range_noflush+0x11/0x20
 [<ffffffff814d7686>] ? ghes_copy_tofrom_phys+0x116/0x1f0
 [<ffffffff814d77d6>] ? ghes_read_estatus+0x76/0x150
 [<ffffffff81073008>] perf_event_nmi_handler+0x28/0x50
 [<ffffffff810630f1>] nmi_handle+0x61/0x110
 [<ffffffff810634a6>] default_do_nmi+0xe6/0x110
 [<ffffffff810635b1>] do_nmi+0xe1/0x150
 [<ffffffff818d8811>] end_repeat_nmi+0x1a/0x1e
 [<ffffffff81124909>] ? queued_spin_lock_slowpath+0x129/0x190
 [<ffffffff81124909>] ? queued_spin_lock_slowpath+0x129/0x190
 [<ffffffff81124909>] ? queued_spin_lock_slowpath+0x129/0x190
 <<EOE>>  <IRQ>  [<ffffffff818d6427>] _raw_spin_lock_irqsave+0x37/0x40
 [<ffffffff8153817c>] intel_unmap+0xbc/0x220
 [<ffffffff8153830e>] intel_unmap_page+0xe/0x10
 [<ffffffff8161a2bd>] igb_poll+0x11d/0x720
 [<ffffffff81761427>] net_rx_action+0x107/0x300
 [<ffffffff810e27ef>] __do_softirq+0xdf/0x2a0
 [<ffffffff810e2bd5>] irq_exit+0x95/0xa0
 [<ffffffff818d8d16>] do_IRQ+0x56/0xd0
 [<ffffffff818d70c2>] common_interrupt+0x82/0x82
 <EOI>  [<ffffffff8171a8c0>] ? cpuidle_enter_state+0xb0/0x270
 [<ffffffff8171a8b6>] ? cpuidle_enter_state+0xa6/0x270
 [<ffffffff8171aab7>] cpuidle_enter+0x17/0x20
 [<ffffffff8111ddd9>] cpu_startup_entry+0x1c9/0x350
 [<ffffffff81093213>] start_secondary+0x113/0x140
Shutting down cpus with NMI
Kernel Offset: disabled

--

If more info is needed, I'll happily provide it.

Regards,
Torsten