I have this problem during booting Ubuntu 17.04/XUbuntu 16.04.2 with new dell
5580 Intel Kabylake + Nvidia 940MX, system never finish startup. Solution is
here:
https://askubuntu.com/questions/875173/nmi-watchdog-bug-soft-lockup-cpu2-stuck-for-23s-plymouthd305
If system boot, it must set
One of these appear every time I resume from suspend.
[ 9387.911475] [ cut here ]
[ 9387.911519] WARNING: CPU: 2 PID: 0 at
/home/kernel/COD/linux/net/mac80211/rx.c:630 ieee80211_rx_napi+0x905/0xa20
[mac80211]
[ 9387.911520] Modules linked in: rtsx_usb_ms memstick
The upstream fixed this problem, but now I'm seeing another suspicious entry in
the dmesg log:
[ 1923.628750] [ cut here ]
[ 1923.628837] WARNING: CPU: 0 PID: 0 at
/home/kernel/COD/linux/net/mac80211/rx.c:630 ieee80211_rx_napi+0x905/0xa20
[mac80211]
[ 1923.628842]
This is a fresh install of 17.04 from the ISO at
https://www.ubuntu.com/download/desktop. I am testing v4.12-rc2.
--
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/1693345
Title:
NMI
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12
** Description changed:
+ The problem occurs in the _raw_spin_lock function.
+
May be related to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1689316
- journalctl -b -1:
+ ***
+ *journalctl -b -1:*
+ ***
-- Logs begin at Mon 2017-05-08 08:54:15
** Description changed:
May be related to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1689316
journalctl -b -1:
-- Logs begin at Mon 2017-05-08 08:54:15 IST, end at Thu 2017-05-25 01:31:26
IST. --
May 24 21:09:28 LiCL kernel: microcode: microcode updated early to revision
7 matches
Mail list logo
