Following update around May 28, Thinkpad running 20.04 won't suspend [closed]

I upgraded to 20.04 a couple of weeks ago, and everything seemed fine. Yesterday I did an update and received, among other things, a new kernel (5.4.0-33). Following this my laptop no longer suspends. Normally, I close the lid and after a second or two the red LED on the lid goes from solid on to a "heartbeat": fade in, fade out. Now it stays on. A little research suggested using systemctl suspend while monitoring dmesg, so I did dmesg -C to clear the ring buffer, then dmesg -w to display continuously while I tried to manually suspend. Here is what I see:

[43626.785407] e1000e: enp0s31f6 NIC Link is Down
[43630.799579] PM: suspend entry (deep)
[43630.808651] Filesystems sync: 0.009 seconds
[43630.809262] Freezing user space processes ... 
[43650.815912] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
[43650.816372] systemd-udevd   D    0  4776    335 0x80000324
[43650.816382] Call Trace:
[43650.816400]  __schedule+0x2e3/0x740
[43650.816412]  ? vprintk_func+0x4c/0xbc
[43650.816420]  schedule+0x42/0xb0
[43650.816429]  do_exit.cold+0xab/0xb5
[43650.816441]  rewind_stack_do_exit+0x17/0x20
[43650.816448] RIP: 0033:0x7f361f32adf0
[43650.816464] Code: Bad RIP value.
[43650.816489] RSP: 002b:00007ffe502f1788 EFLAGS: 00010202
[43650.816497] RAX: 0000000000000d68 RBX: 00005638297288e0 RCX: 0000000000000c00
[43650.816503] RDX: 00007f361f4928a0 RSI: 00005638299aa820 RDI: 00005638297288e0
[43650.816508] RBP: 00007f361f4934a0 R08: 0000000000000c00 R09: 0000563829973100
[43650.816512] R10: 0000563829714010 R11: 00007f361f491be0 R12: 0000000000001001
[43650.816517] R13: 00005638299aa820 R14: 00005638299aa820 R15: 0000000000000000
[43650.816640] OOM killer enabled.
[43650.816643] Restarting tasks ... done.
[43650.863152] PM: suspend exit
[43650.863224] PM: suspend entry (s2idle)
[43650.868181] Filesystems sync: 0.004 seconds
[43650.868458] Freezing user space processes ... 
[43670.880679] Freezing of tasks failed after 20.012 seconds (1 tasks refusing to freeze, wq_busy=0):
[43670.881069] systemd-udevd   D    0  4776    335 0x80000324
[43670.881080] Call Trace:
[43670.881102]  __schedule+0x2e3/0x740
[43670.881116]  ? vprintk_func+0x4c/0xbc
[43670.881125]  schedule+0x42/0xb0
[43670.881135]  do_exit.cold+0xab/0xb5
[43670.881148]  rewind_stack_do_exit+0x17/0x20
[43670.881156] RIP: 0033:0x7f361f32adf0
[43670.881175] Code: Bad RIP value.
[43670.881181] RSP: 002b:00007ffe502f1788 EFLAGS: 00010202
[43670.881189] RAX: 0000000000000d68 RBX: 00005638297288e0 RCX: 0000000000000c00
[43670.881194] RDX: 00007f361f4928a0 RSI: 00005638299aa820 RDI: 00005638297288e0
[43670.881199] RBP: 00007f361f4934a0 R08: 0000000000000c00 R09: 0000563829973100
[43670.881204] R10: 0000563829714010 R11: 00007f361f491be0 R12: 0000000000001001
[43670.881209] R13: 00005638299aa820 R14: 00005638299aa820 R15: 0000000000000000
[43670.881307] OOM killer enabled.
[43670.881310] Restarting tasks ... done.
[43670.931424] PM: suspend exit

I don't know enough to interpret this, but the stack trace doesn't seem good.

My system:

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

$ uname -a
Linux tx1 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

ThinkPad X1 Carbon, 4th generation I think.

Something else happened after the update which may or may not be related: shortly after the update my screen froze, and in place of my normal application icons along the left side of the screen they all were replaced by one single icon which I think was a file. I think I was opening LibreOffice and opening the "file" menu, so it's as if that icon replaced all the others. After trying various things I ended up power cycling, and when the system came up LibreOffice started it's usual process of restoring files that were in use at the time of the shutdown, and for the first time it failed, claiming that the file was corrupted. The file wasn't critical, so no big deal. This has not happened since, but it did make me wonder if I have a problem with my file system. I have a 300GB SSD that's about 40% full.

I'm running pretty much the same system on an old Dell M14X (Alienware) with no problems.

Any ideas?

Edit: Shutdown took about 20 minutes! I'm guessing it was retrying whatever was causing it not to suspend and eventually timed out. I wonder if I wait 20 minutes it will suspend.

Edit 2: After restarting from power off this morning the problem seems to have gone away. I'm glad it's solved but wish I knew why! I had tried power cycling yesterday with no improvement.

2
задан 4 June 2020 в 07:12

1 ответ

Power cycle seems to have made the problem go away. I don't know why. I closed my laptop lid expect it not to work and it did. Tried it again manually (systemctl suspend) and watched dmesg -w, no stack trace. Thanks everyone who tried to help.

0
ответ дан 19 June 2020 в 21:33

Другие вопросы по тегам:

Похожие вопросы: