** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
To manage notifications about this bug go
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: typer 2994 F pulseaudio
/dev/snd/pcmC0D0p: typer 2994 F...m pulseaudio
CurrentDesktop: LXQt
DistroRelease: Ubuntu 18.10
InstallationDate:
Adding to the above #78, when I start the system, and before logging
into ubuntu 18.04 LTS with my username and password. I opened up the
console view (tty4). While shutdown down from there and reboot also
works fine. I recieve no messages of cpu worker stuck as described
above. I think its some
I have faced this issue but maybe with different logs(pfa log
statement).
My laptop is dell 7757 i7 7700+nvidia 1050ti mobile 8gb ram 128gb ssd and 1tb
sata, dual boot ubuntu 18.04.1LTS with 4.15 kernel + windows 10 home(although
not using much).
Sata raid on enabled in dell bios. Earlier tried
Happening on attempted bootup of a Thinkpad W520, using a USB stick
loaded with Ubuntu 17.10 installer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup -
*That's the Ubuntu Mate 17.10 installer. I get a repeated Call trace
which ends with the line, "perf: interrupt took too long (8809 > 8338),
lowering t_max_sample_rate to 22500.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A friend pointed out that the problem I was experiencing on shutdown
(Dell XPS-15 9560) was due to the X.org Nouveau driver. I switched to
NVidia driver (375.66) and my laptop shuts down normally now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Start happening to me now on boot when I connect to docking station (which
brings secondary monitor)
4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
After reading this thread I realised that its probably multiple problem
of dead lock which
Not sure if this is the same issue, but I'm getting:
[ 32.468026] watchdog: BUG: soft lockup - CPU#5 stuck for 23s!
[nvidia-smi:594]
on Kubuntu 17.04 (kernel 4.13.3-041303-generic, i7-4790, GTX 1070,
Nvidia 384.69). My desktop still works fine, I do not experience any
crashes or freezes, but
I managed to solve the issue for my case!!
The problem was a nfs share defined in /etc/fstab. It seems it should be
unmounted but networking already stopped. So i switched to autofs and
successfuly rebooted twice without the problem.
Thats how i defined the mount:
server:/path/to/nfs-share
To fix it edit /etc/sysctl.conf and add:
kernel.watchdog_thresh=30
reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
I believe this issue is effecting me too after a fresh install of Ubuntu
server 16.04.3 with the HWE kernel 4.10 today (fully updated). After
seeing the issue, was unable to log in or SSH in.
** Attachment added: "Picture of errors in tty"
I installed updates yesterday (August 3) and now the OS shutdown command
does nothing except for hide the mouse cursor and leave the desktop
hung. No response from keyboard or mouse. I now have to do a hard
shutdown using the power button. Executing "shutdown" from a terminal
does nothing.
I created a separat issue in the lightdm tracker but could not link it
properly, here is the link:
https://bugs.launchpad.net/lightdm/+bug/1707574
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Today, after making some updates the issue still exists, but the
shutdown screen got a little bit more verbose.
It tells me
"A stop job is running for Light Display Manager" followed by the
original error from this issue.
If i do the following i can shut down:
1) sudo systemctl stop
I get this error every time I shutdown, starting yesterday 2017-07-24.
I have to finish shutting down by holding down the power button for
several seconds. lshw hangs the system completely.
This never happened before yesterday so it must be a recent patch or
change of some sort.
$ uname -a
I can find the following line in the logs over and over again, could
this be connected to the power-off issue i described above?
nouveau :01:00.0: Refused to change power state, currently in D3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I get those messages every time i shut down, so basically every day.
Installed Ubuntu 16.04 on nvme ssd, that i installed into a msi notebook.
Integrated intel (i7 7700) + dedicated nvidia graphics (gtx 1050)
PLEASE help me, turning off my laptop using the power button feels very
unhealthy.
I can repeatably get this problem if I boot without a network connection.I
get the message "waiting for a start job to complete ... Raise Network
Interfaces" followed by "NMI Watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
[swapper/1:0]"
Booting with a network cable attached has no
Same here on Lubuntu 16.04
Can't be nvidia related, i have an intel gpu.
NMI watchdog: BUG: soft lockup - CPU#10 stuck for 23s!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI
Similar problem in 17.04:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693345
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for
+1
I have encountered the same bug (NMI watchdog: BUG: soft lockup - CPU#10 stuck
for 23s!). Logs could be found in the attachment.
** Attachment added: "SecondHang.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/4880124/+files/SecondHang.log
--
You received
Been seeing this sporadically since 17.04 upgrade. I have an NVIDIA
GeForce GT 740 running the proprietary driver, so it isn't nouveau in my
case. Only common activity that sticks in my mind is that it seems to
have occurred for me when (or shortly after) doing something with
VirtualBox - starting
** Tags added: kde-neon yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
To manage notifications about
I had the exact same issue with Asus -> N552VW
It would boot the livecd once from a cold boot, after reboot I got the
same error as above and it would hang during boot, it would refuse to
every boot again.
The workaround from kngharv worked fine however.
Also I discovered enabling secure-boot
I have the same issue when shutting down from Ubuntu 16.04 LTS. Machine:
Dell Precision 3520
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0
I have the same problem trying to boot from Ubuntu 16.04.2LTS Boot USB
Stick on my new Dell Precision 5520 with Xeon. 17.04 works OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
Dell Inspiron 15 (2016) model with Nvidia gtx960m. I am on 16.10,
kernel version 4.8.0-44-generic.
nouvau driver:
Package: xserver-xorg-video-nouveau
Version: 1:1.0.14+git1703080733.b71de8~gd~y
I also encounter this problem.
at the grub, I can at least log in with full graphics by
I have a new laptop Avell B155 V4 with i7 and GTX 950M and I get the
same error. I'm not able to install or run the live Ubuntu, it gets
stuck on loading screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have a new laptop Asus UX360UAK with this issue too: soft lockup CPU
stuck for XX seconds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck
@seccanj, sorry, I @ the wrong person, I haven't try this distribution
yet. I tried the method in #48
@lpturoyo, thank you very much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
Glad it works for you too.
It would be interesting to investigate what has this distribution that
prevents the bug to show up.
May be the desktop environment, Budgie, which is unique?
There's a Budgie version for Arch:
https://www.archlinux.org/packages/community/x86_64/budgie-desktop/
which
@seccanj, thank you very much bro, you are a life saver.
Now my machine can shutdown and even suspend, it finally became an
usable machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Just wanted to report that I no longer have this issue since I installed
the Solus distribution: https://solus-project.com/
I was also affected by the fan bug just cited in the previous comment,
which also seems to have been solved with Solus:
https://bugzilla.kernel.org/show_bug.cgi?id=153281
I
after re-testing since a while back, now with 16.04.2, I was able to
isolate that acpi_osi parameter solves the shutdown issue from nouveau
"failed to adjust lnkctl speed"
update grub with:
GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=\"!Windows 2015\""
* I removed the quiet splash just to see boot
I too have this bug after a clean install of 16.10 this weekend (with a
low end Nvidia graphics card)
The server, after a few minutes to a few hours would hang. I tried
upgrading to 17.04's current alpha too, and it didn't help. I enabled
netconsole to get some logs, and I've attached them here
I downloaded lubuntu-16.10-desktop-amd64.iso and created a new
VirtualBox VM on my MacBook to install it.
Each time I tried to boot the VM I got that 'NMI watchdog: BUG: soft
lockup - CPU#0 stuck for 22s!'
After reading Keith Burns (alagalah) comment #19, I remembered enabling
the USB 3.0 port
One problem for the method in #44, the fan very easily get spinning all
the time if nouveau is blacklisted. So I have the enable it. I don't
think this is a sensible workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@lpturoyo
Thank you very much, I can shutdown normally now. And my system was
already installing the latest packages before blacklisting nouveau, so
it should be safe to update.
Nonetheless, the shutdown problem should be related to nouveau.
--
You received this bug notification because you
@dspjmr,
in my setup, I do not bother to install/run nvidia, and boot/shutdown works
fine.
during the times I have accidentally updated the kernel ( due to some other
package installation ), I only experience the boot issue ( and it is very
random, about 1 of 5 or maybe 1 of 8 boots ).
The
turoyo dee, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
You received
@lpturoyo,
Do you need to install Nvidia drivers and does it mean you cannot update
any packages? Also after installing the new kernel, does it only has
shutdown problem or it also has boot problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@seccanj , I have experienced this same issue and was able to solve with
the same steps.
- install 16.04.1
- get intel-microcode from "unity" -> "additional drivers"
- blacklist nouveau
- $ update init-ramfs -u
this resolves boot and shutdown lockup.
however, I've accidentally updated
I am seeing this issue too, but in my case, it seems there is something
wrong in bbswitch-dkms, if I remove it manually by 'sudo rm
/lib/modules/4.4.0-xx-generic/updates/dkms/bbswitch.ko' I can boot into
system with both intel and nvidia mode (prime-select intel or prime-
select nvidia).
Since
I am affected with 16.04, kernel 4.4.0-51-generic.
The only way I could make my system work has been to install initial
Ubuntu 16.04 and not upgrade any single package since installation.
I used to have hangs even before login, so I enabled auto-login without
password and things got better.
I
I am affected with Xenial 16.04.1 It all started with an upgrade. It has
made my system useless, and affected my entire business. I have several
VMware virtual machines, all identical, so it is not any driver. It also
does not depend on what server I run them. This is the kernel, which
after an
I was running the latest kernel and the issue went away.
But it returned after updating to 4.8.0-28-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft
My i7 was perfectly stable with 4.4 kernel, but 4.8 after Yakety update
failed to boot properly with soft lockups. Downgrade to 4.4 kernel fixed
the issue for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See the same on Yakety with 4.8.0-26-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
To manage
I am seeing this as well, running Lubuntu 16.04 Xenial and
4.4.0-45-generic
Attached is my dmesg showing similar error:
[Tue Nov 1 21:52:16 2016] NMI watchdog: BUG: soft lockup - CPU#0 stuck
for 23s! [swapper/0:1]
** Attachment added: "dmesg.txt"
I am having this problem too. I'm not sure the root of the problem.
It's intermittent. Sometimes machines boot, sometimes they do not.
Sometimes they boot, but then fail to mount an nfs filesystem. (In
those cases, top shows mount.nfs using 100% of the CPU. I can't kill
the process, and I
This just happend to me when upgrading vom 4.7.8 to 4.8.4. Kernel is
self-compiled, but with the kernel config taken from Ubuntu Mainline
PPA.
I run a Macbook 11,3, so it's very similar to what at wvengen's setup
happens.
--
You received this bug notification because you are a member of Ubuntu
This happened to me too about a 2 months ago:
I installed Ubuntu 16.04.
Then I installed the graphic driver (nvidia-367) about a month ago.
Everything was OK until 21 September 2016.
I think that the linux image update that I downloaded at 21 Sep (according to
the update history file) totally
I'm seeing this issue after desktop upgrade to yakkety with kernel
4.8.0-22-generic but not with kernel 4.4.16-040416-generic.
NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [ps:3908]
Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS
MBP111.88Z.0138.B07.1402121134
Join us.
Bug manifested itself on Ubuntu Server 16.04.
I tried everything I could ..
As a result, updated to 16.10. Bug preserved.
Suffice critical.
The server normally does not work more than 5 hours.
uname -r
4.8.0-22-generic
--
You received this bug notification because you are a member of
Like Frederick Astacio, I see this every time I shutdown the laptop. I am
running elementary OS, which is a Ubuntu derivative.
Is there an ETA for the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Do we have a plan when this will be fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
To manage
I dont think the gpu can be called low end, it's pretty new nvidia
gtx960m.
I am not saying the cause it's in the log, but just some clue about the
bug, you cannot tell all the problems just from logs.
By the way, if I set nomodeset without a nvidia driver, then the system
can be shutdown every
Found that root cause on my rig was low end GPU and nouveau driver. Vendor
upgraded my GPU and put on Nvidia driver and its been perfect ever since.
NOTE: nothing in logs indicates a video issue.
On Mon, Aug 22, 2016, 3:45 AM Jimmy Pan wrote:
> This problem is driving me crazy.
This problem is driving me crazy. Looks like this is related to the
nvidia driver. You can shut down the system with 3rd party nvidia driver
installed in recovery x mode. However, you cannot enter normal mode at
all.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
the error occurred when shutting down the laptop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
To manage
I started experiencing this very issue about 3 months ago. My server,
Dell XPS 8700, would lock up repeatedly over the course of a day but
stay "active", meaning my email server wouldn't crash, for a week
sometimes even though I could not log in. This server is at the latest
standard upgrades of
on my Dell Latitude 3450, Core i7-5500U, some new discoveries:
i can start my system if i:
* enable Multi Core support on BIOS
* and disable Hyperthreading on BIOS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have not had a repeat of this issue after disabling USB 3 (it disables
3.1 not 3) in my bios. A bug has been raised with asus re the X99 deluxe
v3101 of their bios. Hope this helps someone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
this problem was apparently fixed for me, after I install
4.5.0-040500-generic ( from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.5-wily/ ), but after 2016-05-28 ubuntu packages update,
i unable to start Ubuntu 16.04 with any of the installed kernels:
4.5.0-040500-generic ( from
I too am experiencing this issue on a brand new system (received Fri
Jun3) with latest BIOS for X99 deluxe and installed Ubuntu 16.04:
dmesg: https://gist.github.com/a15923ba58575c5e62501c17a43e05b5
dmidecode: https://gist.github.com/29f7ff9030f7cb78791431868c609260
lsb_release -a:
Me too.
Nvidia gtx 960m and i7 6700hq.
New install ,anything not change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
I am having the same issue.
Nvidia gtx 980 and i7-5820k
It was not as much a problem when downgrading the video driver to 355.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI
The NMI messages went away after I upgraded the kernel to 4.5.2-040502
and the nVidia driver to 364.19.
However, I was still experiencing intermittent lockups.
Those went away after I disabled KDE's File Indexing (turning off baloo-
file-indexer). I think that maybe my original NMI problems
I'm still seeing this problem in stock amd64 16.04 (kernel 4.4.0-21):
Apr 28 13:46:37 rincewind kernel: [ 108.345612] NMI watchdog: BUG: soft lockup
- CPU#0 stuck for 22s! [QQmlThread:1159]
Apr 28 13:46:37 rincewind kernel: [ 108.347049] Modules linked in: pci_stub
vboxpci(OE) vboxnetadp(OE)
The bug has been marked as 'Triaged' because there is a fix available
upstream. Even though the fix has not been identified yet, marking the
bug incomplete will cause it to expire.
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
Joseph Salisbury, given this is now marked Triaged, could you please
advise to the fix commit as requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/comments/10
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.4
With mainline kernel build "Linux version 4.4.0-040400rc7-generic
(kernel@tangerine) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
) #201512272230 SMP Mon Dec 28 03:32:16 UTC 2015"
(http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc7-wily), the issue
seems to be resolved. No hangs,
This issue has always been happening, even on the Wily 15.10 live cd.
Since I installed Ubuntu from the 15.10 disk, and then upgraded to
Xenial 16.04, there have not been any kernel versions that do not work,
both kernel 4.3.0-2, and kernel 4.2.0-22 hang after a while.
--
You received this bug
CrystalMageX, the next step is to fully reverse commit bisect from
kernel 4.3 to 4.4-rc7 in order to identify the last bad commit, followed
immediately by the first good one. Once this commit has been identified,
then it may be reviewed as a candidate for backporting into your
release. Could you
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
Due to the nature of the issue, I am unable to run the command "apport-
collect", because I cannot get into my desktop or tty. However, I have
somehow managed to get into recovery mode without it becoming unusable,
and unfortunately "apport-collect" requires internet to run, and
recovery mode
Output of "uname -a" :
** Attachment added: "uname.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/4542678/+files/uname.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Output of "lspci -vnvn":
** Attachment added: "lspci.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/4542677/+files/lspci.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Output of "cat /proc/version_signature" :
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/4542679/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: amd64 wily
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530405
Title:
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
To manage
83 matches
Mail list logo