From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752155AbcCKLhk (ORCPT ); Fri, 11 Mar 2016 06:37:40 -0500 Received: from mail1.cbxnet.de ([212.87.33.16]:56275 "EHLO mail1.cbxnet.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751495AbcCKLhd (ORCPT ); Fri, 11 Mar 2016 06:37:33 -0500 X-Greylist: delayed 979 seconds by postgrey-1.27 at vger.kernel.org; Fri, 11 Mar 2016 06:37:32 EST Date: Fri, 11 Mar 2016 12:21:11 +0100 From: Torsten Luettgert To: linux-kernel@vger.kernel.org Subject: BUG: hard lockups on docker operations Message-ID: <20160311122111.4e4c44f1@goldlack.ei> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello kernel hackers, I'm getting hard lockups with kernel 4.4.5 (at least 4.4.3 and 4.4.4 also). This is a docker hypervisor machine with overlayfs and 3ware RAID. They usually happen when I do something with docker, here when I ran poweroff in a container (those are all VM-like containers which run /sbin/init inside). Oops follows: NMI watchdog: Watchdog detected hard LOCKUP on cpu 4 Kernel panic - not syncing: Hard LOCKUP CPU: 4 PID: 26116 Comm: plymouthd Not tainted 4.4.5 #1 Hardware name: Supermicro X8DTT/X8DTT, BIOS 2.1c 04/22/2014 0000000000000000 ffff880c3fc05b70 ffffffff814328e7 ffffffff81cf26a2 0000000000000000 ffff880c3fc05be8 ffffffff811b2afc ffff880c00000008 ffff880c3fc05bf8 ffff880c3fc05b98 0000000000000000 0000000000000046 Call Trace: [] dump_stack+0x63/0x8c [] panic+0xc8/0x20f [] watchdog_overflow_callback+0xe0/0xe0 [] __perf_event_overflow+0x88/0x1c0 [] perf_event_overflow+0x14/0x20 [] intel_pmu_handle_irq+0x1cc/0x430 [] ? ioremap_page_range+0x299/0x410 [] ? vunmap_page_range+0x1dc/0x310 [] ? unmap_kernel_range_noflush+0x11/0x20 [] ? ghes_copy_tofrom_phys+0x116/0x1f0 [] ? ghes_read_estatus+0x76/0x150 [] perf_event_nmi_handler+0x28/0x50 [] nmi_handle+0x61/0x120 [] default_do_nmi+0xad/0xf0 [] do_nmi+0xe1/0x150 [] end_repeat_nmi+0x1a/0x1e [] ? qi_submit_sync+0x17f/0x3e0 [] ? qi_submit_sync+0x17f/0x3e0 [] ? qi_submit_sync+0x17f/0x3e0 <> [] modify_irte+0xaf/0x140 [] intel_irq_remapping_activate+0x16/0x20 [] irq_domain_activate_irq+0x41/0x50 [] irq_domain_activate_irq+0x2b/0x50 [] irq_startup+0x35/0x80 [] __setup_irq+0x528/0x5c0 [] ? serial8250_backup_timeout+0x120/0x120 [] request_threaded_irq+0xf4/0x1b0 [] univ8250_setup_irq+0x231/0x270 [] serial8250_do_startup+0x12f/0x650 [] serial8250_startup+0x25/0x30 [] uart_startup.part.16+0x85/0x1c0 [] uart_open+0x11b/0x170 [] tty_open+0x101/0x620 [] ? kobj_lookup+0x10d/0x160 [] chrdev_open+0xaa/0x170 [] do_dentry_open+0x227/0x320 [] ? cdev_put+0x30/0x30 [] vfs_open+0x57/0x60 [] path_openat+0x181/0x1140 [] do_filp_open+0x7e/0xd0 [] ? __alloc_fd+0x3f/0x170 [] do_sys_open+0x128/0x210 [] SyS_open+0x1e/0x20 [] entry_SYSCALL_64_fastpath+0x12/0x71 Shutting down cpus with NMI Kernel Offset: disabled If more info is needed, I'll happily provide it. Regards, Torsten