| 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
| ||
|
Message-ID: <alpine.LRH.2.11.1409281201160.9728@adalberg.ut.ee> Date: Sun, 28 Sep 2014 12:05:38 +0300 (EEST) From: Meelis Roos <mroos@...ux.ee> To: Linux Kernel list <linux-kernel@...r.kernel.org> Subject: kernel:[ 1155.839866] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/u8:5:71] While trying yesterdays 3.17 git snapshot on a i5-2400 + intel graphics computer, it seems to go into soft lockup. Still pings but no ssh to it any more, and active ssh session got the following kind of NMI watchdog soft lockups during aptitude list update: essage from syslogd@...es at Sep 27 11:43:55 ... kernel:[ 1015.866355] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u8:5:71] Message from syslogd@...es at Sep 27 11:44:23 ... kernel:[ 1043.861061] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u8:5:71] Message from syslogd@...es at Sep 27 11:44:51 ... kernel:[ 1071.855791] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u8:5:71] Message from syslogd@...es at Sep 27 11:45:19 ... kernel:[ 1099.850501] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u8:5:71] Message from syslogd@...es at Sep 27 11:45:47 ... kernel:[ 1127.845192] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/u8:5:71] Message from syslogd@...es at Sep 27 11:46:15 ... kernel:[ 1155.839866] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/u8:5:71] 3.16 ran fine. This was remote reboot into the new kernel, so only graphics usage is kms console on i915 + kdm login screen. Only user-initiaded action was ssh connection with dmesg, su -, aptitude and aptitude list update from there. -- Meelis Roos (mroos@...ux.ee) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists