My Lenovo Laptop cannot be left standing for any lengthy interval without requiring reboot

Support and Help
, ,
61

And now back to the original pattern. Had to reboot AGAIN.

journalctl --boot=-1 | tail -n 2000 | pastebinit
https://paste.ubuntu.com/p/bw7p8sK3pp/

Here we see this pattern repeating over and over.

Mar 02 22:44:54 aigas kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 3934s! [idrive:2285]
Mar 02 22:44:54 aigas kernel: watchdog: BUG: soft lockup - CPU#12 stuck for 2370s! [kworker/12:0:55]
Mar 02 22:45:22 aigas kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 3960s! [idrive:2285]
Mar 02 22:45:22 aigas kernel: watchdog: BUG: soft lockup - CPU#12 stuck for 2396s! [kworker/12:0:55]

The same two processes repeating a “soft lockup” over and over. A kworker thread (whatever that is) and an idrive thread which I know is because I do have backups enabled using idrive. I might try turning that off except for the fact that in yesterday’s crash, idrive was not in the journal, just two kworker threads.

Mar 02 09:36:29 aigas kernel: watchdog: BUG: soft lockup - CPU#7 stuck for 1383s! [kworker/7:0:487944]
Mar 02 09:36:33 aigas kernel: watchdog: BUG: soft lockup - CPU#8 stuck for 6687s! [kworker/8:2:487196]
Mar 02 09:36:57 aigas kernel: watchdog: BUG: soft lockup - CPU#7 stuck for 1409s! [kworker/7:0:487944]
Mar 02 09:37:01 aigas kernel: watchdog: BUG: soft lockup - CPU#8 stuck for 6713s! [kworker/8:2:487196]

Look, this is totally absurd. All I want is a reliable method of walking away from this computer and not having to reboot it when I come back. Is that too much to ask for?

I am used to being able to just walk away from the computer. I am willing to settle, instead, for a reliable method of issuing some command to make the computer sleep or suspend or hibernate or whatever other verb someone can come up with, provided that there is some well-defined event, some keypress, mouse movement or whatever that will reliably force it to wake up. Information about what wakes it from any of these states is never provided, which makes me think that any old keypress or mouse click is supposed to be sufficient.

What makes this especially maddening is that I can sit at this computer for hours doing all sorts of tasks and never experience this problem. Only when it is idle do these problems occur. Think for a moment how absurd that is.

My detective work has proven useless.

Looking for a new strategy.

62

Perhaps this terminal command may be worth a shot?
systemctl suspend
The terminal window will still be visible upon resume

63

In a nutshell, A soft lockup in Linux is a situation where a task or kernel thread uses a CPU for a longer period than allowed without giving other tasks a chance to run.

In summary, a soft lockup indicates that the kernel is stuck and not allowing other tasks to run, which can be caused by bugs or poorly written code.

I’m even more convinced there is some controller on this machine, that just is not playing nicely with the system. “I have no clue how to verify that though”.

But one Idea is to hook up a external SSD and try another Ubuntu install on that drive only.

64

Giving this a try. Thanks.

A couple questions:

  1. Do you know how this differs from simply walking away from the computer and letting it sleep/suspend itself?
  2. Is doing this command equivalent to simply closing the laptop cover/screen?

Anyway, I’m doing it, and we’ll see.

65

Regrettably, I have no idea.
If I walk away from the PC for a little while (a Desktop in my case), I use
GUI power Icon > Suspend

Again, I don’t know

Excellent, nothing ventured, nothing gained
Fingers crossed…

66

Things were going pretty well until a crash. But it was a different sort of crash. I invoked suspend and walked away for a couple of minutes.

The system would not come up properly. The laptop screen came up after Fn-Ctrl-Alt-F2. It wasn’t a complete crash, I was able to bring something up but not all the way. I use two monitors, and I call the second monitor primary, mostly because I prefer to have the top panel on that monitor. The result was a working laptop screen but the other screen would not settle in to becoming functional. And anything running on that screen remained inaccessible , even after turning the dual monitor off. I finally had to reboot.

$ journalctl --boot=-1 | tail -n 2000 | pastebinit
https://paste.ubuntu.com/p/QdDYcKGNGw/

Lots of stuff there about my BenQ monitor. I wonder if there’s any configuration stuff beyond what’s in the GUI Dual Monitor setup for dealing with this. Are there some command line ways of temporarily stopping the second monitor?

67

This topic was automatically closed after 30 days. New replies are no longer allowed.