[Solved] Soft lockup on CPU0 when calling lspci

Voxol · 2018-04-06 20:44:23

I'm sorry for formatting and for posting a picture of the error, but my laptop is softlocked on this error and I only have my phone to write here. (English is also a second language, so I might be using some weird terms)

During a new arch installation I was following the install guide and just before installing the bootloader I launched lspci to see what is the network card and this happened:

https://owncloud.eigenlab.org/s/1leLDUG6pyTd2Wy

I honesty have no idea what's happening or what could be causing it as the PC is brand new and I was just removing windows to install arch.

The laptop is an msi GP62M 7RD

Last edited by Voxol (2018-04-12 09:40:12)

Trilby · 2018-04-06 22:25:21

Which iso are you using? I just searched and can't seem to find it - but I'm pretty sure I've seen this issue on the forums recently. If I'm remembering right (big if), it seemed to be a problem with one of the recent monthly isos.

Voxol · 2018-04-06 22:34:03

I downloaded the most recent one today.

If it's a problem of the ISO, could it be that it will go away if I actually manage to finish the installation? Or after a few updates?

Trilby · 2018-04-06 22:37:00

That's what I vaguely recall from the previous time I remember seeing something like this. But until I can find the other thread I can't be sure.

Voxol · 2018-04-06 23:31:27

Well, I don't know if it can help but after rebooting into the installed system the problem persists.

Just to test if it's actually the ISO, is there a way to get an older one?

Trilby · 2018-04-07 00:04:09

They're all here. But if the problem persists in the installed system, a different iso would not help.

I've also now spent a fair bit of time trying to find the previous thread I was thinking of, yet I can't find it. So either it has been deleted, or perhaps I am remembering incorrectly (just a bad case of deja vu - I could swear I saw a thread about this recently, but it doesn't seem to exist).

Last edited by Trilby (2018-04-07 00:34:15)

circleface · 2018-04-07 03:27:32

One other option that might work is to install a different kernel before you reboot. The -lts kernel may not cause the same error.

Edit: Also, for what it's worth, I just installed Arch using the latest ISO on my laptop and ran into no problems. But as Trilby said, if the error persists in the booted environment, it is unlikely to be an ISO problem.

Last edited by circleface (2018-04-07 03:44:34)

Lone_Wolf · 2018-04-07 10:38:19

The first INFO line in the pic looks like it has some usual info that's not entirely readable .

It starts with

INFO : task lspci :

Does it say 8420 or B420 ?

lspci looks like it was run after installing something , possibly in a chroot.

Does lspci also crash just after the iso has booted ?

Are you running latest firmware for the laptop ?

Voxol · 2018-04-08 02:52:14

Lone_Wolf wrote:

The first INFO line in the pic looks like it has some usual info that's not entirely readable .
It starts with
INFO : task lspci : 
Does it say 8420 or B420 ?

It says 8420, I have another picture I took prior to the other one which reads more clearly

https://owncloud.eigenlab.org/s/QFhZWSdJl5EloYf

lspci looks like it was run after installing something , possibly in a chroot.

It's in arch-chroot as it's during the installation, but it gave the same problem after rebooting into the installed system

Does lspci also crash just after the iso has booted ?

I don't remember now if I checked and it did, but I'll try in the morning as I'll need to ask a friend for a PC to make another live USB.

Are you running latest firmware for the laptop ?

You mean the UEFI firmware? As the computer just came from the shop I didn't check, I'll do that and update if it isn't.

Trilby · 2018-04-08 11:49:09

Voxol wrote:

I don't remember now if I checked and it did, but I'll try in the morning as I'll need to ask a friend for a PC to make another live USB.

Your arch system works except for lspci, right? You can make an iso on your system.

Voxol · 2018-04-09 11:27:14

So, I just updated the firmware and the problem persists, even when I just booted the iso

Trilby · 2018-04-09 12:38:34

What about any relevant microcode?

Voxol · 2018-04-10 09:58:59

Ok, yesterday I managed to find a solution to the problem.

I found this page for another laptop on the wiki which described exactly my problem, so I tried following it and it solved everything.

https://wiki.archlinux.org/index.php/De … PU_lockups

In short it was the graphics card which locked everything and I had to add

nouveau.modeset=0

as a kernel parameter to solve it.

As for curiosity, I searched for a bit, but wasn't able to find what this parameter actually does or what it means, so if anyone knows I'd be happy to know.

Edit: Since it seems to be a recurring problem with nvidia cards (on my home computer with a GTX970 I had to add nomodeset as a kernel parameter or the bootloader wouldn't start) to be needing special kernel parameters, wouldn't it be the case to add a section in the nvidia/nouveau page for this kind of problems? I know these are the pages for the drivers, not for the card, but I feel they are pages which could easily be looked at by someone with a problem on a computer with an NVIDIA card.

Last edited by Voxol (2018-04-10 10:09:50)

Lone_Wolf · 2018-04-10 11:02:45

Voxol, this sounds like a problem exclusive to nvidia proprietary driver.
Adding it to that page should be ok.

(nouveau users want to avoid that parameter like the plague).

Voxol · 2018-04-12 09:39:50

Lone_Wolf wrote:

Voxol, this sounds like a problem exclusive to nvidia proprietary driver.
Adding it to that page should be ok.
(nouveau users want to avoid that parameter like the plague).

As I said, I don't really understand what that parameter does, could you please explain? Or link to somewhere I could find an explanation?

V1del · 2018-04-12 09:49:45

It enables/disables kernel mode setting, so that mode changes (resolution changes and the like) are done in kernel space: https://01.org/linuxgraphics/gfx-docs/d … m-kms.html https://wiki.archlinux.org/index.php/Ke … de_setting

For the intents and purposes of nouveau you are essentially disabling the driver if you disable modesetting. It does trip up on trying to enable it for graphics adapters it doesn't really support yet. which leads to the freeze while it tries to show you info on a graphics chip.

Last edited by V1del (2018-04-12 09:50:10)

Arch Linux

#1 2018-04-06 20:44:23

[Solved] Soft lockup on CPU0 when calling lspci

#2 2018-04-06 22:25:21

Re: [Solved] Soft lockup on CPU0 when calling lspci

#3 2018-04-06 22:34:03

Re: [Solved] Soft lockup on CPU0 when calling lspci

#4 2018-04-06 22:37:00

Re: [Solved] Soft lockup on CPU0 when calling lspci

#5 2018-04-06 23:31:27

Re: [Solved] Soft lockup on CPU0 when calling lspci

#6 2018-04-07 00:04:09

Re: [Solved] Soft lockup on CPU0 when calling lspci

#7 2018-04-07 03:27:32

Re: [Solved] Soft lockup on CPU0 when calling lspci

#8 2018-04-07 10:38:19

Re: [Solved] Soft lockup on CPU0 when calling lspci

#9 2018-04-08 02:52:14

Re: [Solved] Soft lockup on CPU0 when calling lspci

#10 2018-04-08 11:49:09

Re: [Solved] Soft lockup on CPU0 when calling lspci

#11 2018-04-09 11:27:14

Re: [Solved] Soft lockup on CPU0 when calling lspci

#12 2018-04-09 12:38:34

Re: [Solved] Soft lockup on CPU0 when calling lspci

#13 2018-04-10 09:58:59

Re: [Solved] Soft lockup on CPU0 when calling lspci

#14 2018-04-10 11:02:45

Re: [Solved] Soft lockup on CPU0 when calling lspci

#15 2018-04-12 09:39:50

Re: [Solved] Soft lockup on CPU0 when calling lspci

#16 2018-04-12 09:49:45

Re: [Solved] Soft lockup on CPU0 when calling lspci

Board footer