Failed to Shutdown. watchdog: BUG: soft lockup

ariakun · 2018-06-23 10:50:57

Hello,
I had just run pacman -Syyu this morning.
But when i try shutdown or reboot process. it said bug soft lockup core #7.
I think its kernel problem.

idk where to start, I've been waiting for about an hour to see what will happen next. but it stucked (doesnt shutdown).

*currently i'm using 4.17.2-1-ARCH kernel

this problem comes when i upgrade to the linux kernel to 4.16.3-1.
I have downgraded to the linux-lts kernel and it's back to normally.
and I am now trying to re-use the latest linux kernel.
However, the problem comes again. should i use linux-lts again?

Anyway, thanks for reading, any suggestions or advice would be greatly appreciated.

*this is the error notification I got
https://imgur.com/3KH8SXH

Last edited by ariakun (2018-06-24 05:14:21)

seth · 2018-06-23 12:19:39

systemctl list-unit-files --state=enabled

Also please your complete pacman log.

Sidenotes:
NEVER! Run "-Syyu" unless you know what the second "y" does any you *really* want that.
Also dropping links to other forum threads (let alone at fakebook) is not well regarded.
And "have done read some™ article is a generic and shallow disclaimer that translates to "idk where to start" - nobody here will fall for that. Either explain in detail what you tried and ruled out or just say "I've no idea where to start".

ariakun · 2018-06-24 05:08:23

seth wrote:

systemctl list-unit-files --state=enabled
Also please your complete pacman log.
Sidenotes:
NEVER! Run "-Syyu" unless you know what the second "y" does any you *really* want that.
Also dropping links to other forum threads (let alone at fakebook) is not well regarded.
And "have done read some™ article is a generic and shallow disclaimer that translates to "idk where to start" - nobody here will fall for that. Either explain in detail what you tried and ruled out or just say "I've no idea where to start".

umm.. thank's.
i'll edit the post

here is my pacman.log.
https://drive.google.com/open?id=1A0ULp … Lhu1aK4q2L

and systemctl list-unit-files
https://drive.google.com/open?id=1n_qy- … vFMV66gQVt

Last edited by ariakun (2018-06-24 05:16:51)

seth · 2018-06-24 07:45:19

dhcpcd.service                              enabled
...
NetworkManager.service           enabled

You're running concurrent network managing services.
For a start, choose one and disable the other - they enter a race for the interfaces and that is at least currently the tail of your shutdown.

ariakun · 2018-06-24 22:35:00

seth wrote:

dhcpcd.service                              enabled
...
NetworkManager.service           enabled
You're running concurrent network managing services.
For a start, choose one and disable the other - they enter a race for the interfaces and that is at least currently the tail of your shutdown.

the problem still same.
it said watchdog: BUG: soft lockup - CPU#6 stuck for 22s.

and it's like doesn't stop.
it still continue the process.
i had just waiting for hours.
but the result still same.
always said watchdog bug.
untill i force shutdown from the button.

here the image i had just capture it:
https://imgur.com/vh0h3dq

Last edited by ariakun (2018-06-24 22:40:47)

seth · 2018-06-25 06:26:03

It would seem https://bugs.archlinux.org/task/55645 is back?
Please post a complete dmesg (before attempting to shutdown)

ariakun · 2018-06-26 07:13:46

seth wrote:

It would seem https://bugs.archlinux.org/task/55645 is back?
Please post a complete dmesg (before attempting to shutdown)

so, like this command?

 dmesg > dmesg.txt

and here is the output:
https://drive.google.com/file/d/1YvnlK8 … Tss3j/view

V1del · 2018-06-26 09:15:12

Somehow that still isn't the complete output...

However nouveau is going bonkers, try to see what happens if you blacklist that. In general for options regarding the secondary nvidia card you will want to look at https://wiki.archlinux.org/index.php/Optimus

loqs · 2018-06-26 10:05:03

dmesg ring buffer is too small to retain all the messages. You could try add the kernel option log_buf_len=4M

ariakun · 2018-06-27 11:36:29

V1del wrote:

Somehow that still isn't the complete output...
However nouveau is going bonkers, try to see what happens if you blacklist that. In general for options regarding the secondary nvidia card you will want to look at https://wiki.archlinux.org/index.php/Optimus

i don't know what should i do to get complete output.
i have following guide from here:
https://docs.nvidia.com/cuda/cuda-insta … le-nouveau

and i'm Generate customized initcpio, with these guide.
https://wiki.archlinux.org/index.php/Mk … activation

and the problem still same.

loqs wrote:

dmesg ring buffer is too small to retain all the messages. You could try add the kernel option log_buf_len=4M

how to add the option log on my kernel options?

*can i use journalctl to get all the complete output?

Last edited by ariakun (2018-06-27 11:37:59)

seth · 2018-06-27 13:06:04

https://wiki.archlinux.org/index.php/Kernel_parameters

What is your strategy reg. the optimus system and could you please try substituting nouveau w/ the nvidia blob?

drcouzelis · 2018-06-27 13:14:33

Are you using a Ryzen processor?

There is kind of a known issue with Ryzen processors...

ariakun · 2018-06-27 13:51:44

seth wrote:

https://wiki.archlinux.org/index.php/Kernel_parameters
What is your strategy reg. the optimus system and could you please try substituting nouveau w/ the nvidia blob?

idk, as i remember i'm installing nvidia with these command:

pacman -S nvidia

and i never trying to use optimus

drcouzelis wrote:

Are you using a Ryzen processor?
There is kind of a known issue with Ryzen processors...

my device is acer E5-476G.
and i'm using Intel Core i5-8250U.

seth · 2018-06-27 14:52:17

and i never trying to use optimus

This is where your problems start…
You've to decide whether you only want to use the intel chip or only the nvidia chip or dynamically invoke the nvidia chip or use them for different display servers at the same time.
Also you've to make an opinion on whether to use nouveau or nvidia and w/ the GP108 chip, id'd rather try the nvidia blob.
Also, according to the posted dmesg fraction, the nvidia kernel module isn't installed - but the nouveau one is. So you didn't install the nvidia package at all.

ariakun · 2018-06-30 07:55:25

seth wrote:

and i never trying to use optimus
This is where your problems start…
You've to decide whether you only want to use the intel chip or only the nvidia chip or dynamically invoke the nvidia chip or use them for different display servers at the same time.
Also you've to make an opinion on whether to use nouveau or nvidia and w/ the GP108 chip, id'd rather try the nvidia blob.
Also, according to the posted dmesg fraction, the nvidia kernel module isn't installed - but the nouveau one is. So you didn't install the nvidia package at all.

oh my god, it's work!
i've just download it from:
http://www.nvidia.com/object/unix.html
at the first time shutdown it doesn't work. but when 2nd try to shutdown it's totally works!

how can it be happen? i mean, graphics related to the shutdown process.
on lts kernel it's totally normal. but, when on latest kernel. it's bugged.
I am very confused with this.

can someone explain it?

loqs · 2018-06-30 08:02:36

You ignored the warning at the top of NVIDIA and used the driver from the nvidia website?

ariakun · 2018-06-30 10:32:11

loqs wrote:

You ignored the warning at the top of NVIDIA and used the driver from the nvidia website?

uh, i'm forget about that.
so what should i do. if i'm back to use

 pacman -S nvidia

this problem will come again.

Last edited by ariakun (2018-06-30 10:43:27)

loqs · 2018-06-30 11:22:25

Why would the problem come again because you install nvidia using pacman?

ariakun · 2018-07-01 03:21:34

loqs wrote:

Why would the problem come again because you install nvidia using pacman?

i'm using nvidia from pacman before.
and currently i'm using it from blob package.

seth · 2018-07-01 05:01:48

No, you did not. At least not when you took the logs you posted.

ariakun · 2018-07-01 08:34:31

seth wrote:

No, you did not. At least not when you took the logs you posted.

which one?
pacman logs?
here is my pacman.log:
https://drive.google.com/open?id=1QQbpI … rrBjzrqjvu

seth · 2018-07-01 09:28:04

The dmesg log in comment #7 - it clearly says you're using nouveau:
https://drive.google.com/file/d/1YvnlK8 … Tss3j/view

Your pacman log says you were messing around w/ the 340xx branch and updated to the latest nvidia driver on June 27th (matching the comment #13 date) but we've not seen any logs of this configuration, nor indications that things failed *after* this change.

Arch Linux

#1 2018-06-23 10:50:57

Failed to Shutdown. watchdog: BUG: soft lockup

#2 2018-06-23 12:19:39

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#3 2018-06-24 05:08:23

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#4 2018-06-24 07:45:19

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#5 2018-06-24 22:35:00

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#6 2018-06-25 06:26:03

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#7 2018-06-26 07:13:46

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#8 2018-06-26 09:15:12

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#9 2018-06-26 10:05:03

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#10 2018-06-27 11:36:29

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#11 2018-06-27 13:06:04

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#12 2018-06-27 13:14:33

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#13 2018-06-27 13:51:44

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#14 2018-06-27 14:52:17

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#15 2018-06-30 07:55:25

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#16 2018-06-30 08:02:36

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#17 2018-06-30 10:32:11

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#18 2018-06-30 11:22:25

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#19 2018-07-01 03:21:34

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#20 2018-07-01 05:01:48

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#21 2018-07-01 08:34:31

Re: Failed to Shutdown. watchdog: BUG: soft lockup

#22 2018-07-01 09:28:04

Re: Failed to Shutdown. watchdog: BUG: soft lockup

Board footer