Flip_done timed out Error after updating Manjaro which freezes TTY, DisplayManager for Lenovo T14s

Hardware

Lenovo T14s with AMD Ryzen Pro 7

inxi -b
System:
  Host: my-pc Kernel: 5.10.148-1-MANJARO arch: x86_64 bits: 64 Console: pty pts/0
    Distro: Manjaro Linux
Machine:
  Type: Laptop System: LENOVO product: 20UJS00K00 v: ThinkPad T14s Gen 1
    serial: <superuser required>
  Mobo: LENOVO model: 20UJS00K00 serial: <superuser required> UEFI: LENOVO v: R1CET61W(1.30 )
    date: 12/21/2020
Battery:
  ID-1: BAT0 charge: 29.3 Wh (58.1%) condition: 50.4/57.0 Wh (88.3%) volts: 11.5 min: 11.5
CPU:
  Info: 8-core AMD Ryzen 7 PRO 4750U with Radeon Graphics [MT MCP] speed (MHz): avg: 1397
    min/max: 1400/1700
Graphics:
  Device-1: AMD Renoir driver: amdgpu v: kernel
  Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo
  Display: server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3 driver: X: loaded: amdgpu
    unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu tty: 120x30 resolution: 1920x1080
  Message: Unable to show GL data. Required tool glxinfo missing.
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi
Drives:
  Local Storage: total: 953.87 GiB used: 105.38 GiB (11.0%)
Info:
  Processes: 339 Uptime: 26m Memory: 30.65 GiB used: 1.12 GiB (3.7%) Init: systemd Shell: Zsh
  inxi: 3.3.22

Manjaro

 cat /etc/os-release
NAME="Manjaro Linux"
ID=manjaro
ID_LIKE=arch
BUILD_ID=rolling
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="32;1;24;144;200"
HOME_URL="https://manjaro.org/"
DOCUMENTATION_URL="https://wiki.manjaro.org/"
SUPPORT_URL="https://manjaro.org/"
BUG_REPORT_URL="https://bugs.manjaro.org/"
LOGO=manjarolinux
uname -a  
Linux my-pc 5.10.148-1-MANJARO #1 SMP PREEMPT Sat Oct 15 13:41:09 UTC 2022 x86_64 GNU/Linux

Steps

After the updates were available

sudo pamac update

I was able to download all the necessary packages as well as the process was able to generate the respective initramdisk which generally happens at the last stage of the command above.

I then triggered a reboot:

sudo reboot

Upon reboot, the display manager screen is completely frozen and even moving to TTY consoles takes about close to 5-10 minutes. I was luckily able to log into a TTY Console and I ran the following:

sudo dmesg | grep -i "error"

I get:

[ 1327.409562] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1337.436234] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1347.462915] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1357.489569] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1367.516318] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1377.542905] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1387.569560] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1397.596242] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1407.622892] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1417.649330] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1427.676230] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1437.702915] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1447.729574] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1457.756234] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1467.782955] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1477.809571] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1487.836225] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1497.862893] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1507.889562] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1517.916221] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1527.942885] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1537.969553] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1547.996231] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1558.022881] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1568.049541] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1578.076211] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1588.102881] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1598.129546] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1608.156216] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1618.182882] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1628.209613] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1638.236209] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1648.262893] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1658.289540] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1668.316234] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1678.342884] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1688.369563] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1698.396215] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1708.422893] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1718.449559] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1728.476210] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1738.502987] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1748.529537] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1758.556197] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1768.582883] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1778.609528] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1788.636194] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out
[ 1798.662859] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out
[ 1808.689532] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out

I keep Kernel Traces upon journalctl -xe

Okt 17 22:24:30 shan-pc kernel: RSP: 0018:ffffa401809dba70 EFLAGS: 00010082
Okt 17 22:24:30 shan-pc kernel: RAX: 0000000000000001 RBX: 0000000000000287 RCX: 000000000000001e
Okt 17 22:24:30 shan-pc kernel: RDX: 0000000000000001 RSI: 0000000000000297 RDI: ffff8d6e6a200188
Okt 17 22:24:30 shan-pc kernel: RBP: ffffa401809dbd68 R08: 0000000000000002 R09: 0000000000000001
Okt 17 22:24:30 shan-pc kernel: R10: 0000000000000000 R11: ffff8d6e65ded118 R12: 0000000000000000
Okt 17 22:24:30 shan-pc kernel: R13: ffff8d6e65ded000 R14: ffff8d6e65ded118 R15: ffff8d6e62201300
Okt 17 22:24:30 shan-pc kernel: FS:  0000000000000000(0000) GS:ffff8d752fb80000(0000) knlGS:0000000000000000
Okt 17 22:24:30 shan-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Okt 17 22:24:30 shan-pc kernel: CR2: 000055c323015004 CR3: 00000006a8e10000 CR4: 0000000000350ee0
Okt 17 22:24:30 shan-pc kernel: Call Trace:
Okt 17 22:24:30 shan-pc kernel:  ? prb_read_valid+0x17/0x20
Okt 17 22:24:30 shan-pc kernel:  ? vprintk_emit+0x14f/0x290
Okt 17 22:24:30 shan-pc kernel:  ? printk+0x58/0x73
Okt 17 22:24:30 shan-pc kernel:  ? drm_atomic_helper_wait_for_dependencies+0x1e4/0x200 [drm_kms_helper]
Okt 17 22:24:30 shan-pc kernel:  ? __drm_err+0x72/0x90 [drm]
Okt 17 22:24:30 shan-pc kernel:  commit_tail+0x94/0x130 [drm_kms_helper]
Okt 17 22:24:30 shan-pc kernel:  drm_atomic_helper_commit+0x112/0x140 [drm_kms_helper]
Okt 17 22:24:30 shan-pc kernel:  drm_atomic_helper_dirtyfb+0x189/0x260 [drm_kms_helper]
Okt 17 22:24:30 shan-pc kernel:  drm_fb_helper_dirty_work+0x179/0x1b0 [drm_kms_helper]
Okt 17 22:24:30 shan-pc kernel:  process_one_work+0x1aa/0x360
Okt 17 22:24:30 shan-pc kernel:  worker_thread+0x1e0/0x390
Okt 17 22:24:30 shan-pc kernel:  ? process_one_work+0x360/0x360
Okt 17 22:24:30 shan-pc kernel:  kthread+0x12d/0x150
Okt 17 22:24:30 shan-pc kernel:  ? kthread_associate_blkcg+0xc0/0xc0
Okt 17 22:24:30 shan-pc kernel:  ret_from_fork+0x22/0x30
Okt 17 22:24:30 shan-pc kernel: ---[ end trace e5068d684a9ffbde ]---
Okt 17 22:24:34 shan-pc audit[3265]: USER_AUTH pid=3265 uid=1000 auid=1000 ses=7 subj=unconfined msg='op=PAM:authentication grantors=pam_unix acct="shantan>
Okt 17 22:24:34 shan-pc kernel: audit: type=1100 audit(1666038274.401:430): pid=3265 uid=1000 auid=1000 ses=7 subj=unconfined msg='op=PAM:authentication gr>
Okt 17 22:24:34 shan-pc dbus-daemon[1034]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' >
Okt 17 22:24:34 shan-pc dbus-daemon[1034]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.>
Okt 17 22:24:34 shan-pc sudo[3265]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Okt 17 22:24:34 shan-pc audit[3265]: USER_ACCT pid=3265 uid=1000 auid=1000 ses=7 subj=unconfined msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_ti>
Okt 17 22:24:34 shan-pc kernel: audit: type=1101 audit(1666038274.405:431): pid=3265 uid=1000 auid=1000 ses=7 subj=unconfined msg='op=PAM:accounting granto>
Okt 17 22:24:34 shan-pc sudo[3265]: shantanoo : TTY=pts/0 ; PWD=/home/shantanoo ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Okt 17 22:24:34 shan-pc audit[3265]: CRED_REFR pid=3265 uid=1000 auid=1000 ses=7 subj=unconfined msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/us>
Okt 17 22:24:34 shan-pc kernel: audit: type=1110 audit(1666038274.408:432): pid=3265 uid=1000 auid=1000 ses=7 subj=unconfined msg='op=PAM:setcred grantors=>
Okt 17 22:24:34 shan-pc sudo[3265]: pam_unix(sudo:session): session opened for user root(uid=0) by user(uid=1000)

Changes tried

I tried adding video=SVIDEO-1:d in the /etc/default/grub and also tried adding idle=nomwait in the kernel boot options but nothing is working. I still keep getting delays close to 5 minutes and the UI never loads.

What have done wrong here? Can I revert the updates somehow, because before the updates everything worked well

try the 5.15 kernel and see if it helped

Hi,
Sorry to ask this but would you be able to provide some steps as to how to install the 5.15 kernel?

so how did you get the info above? can you boot normally? or from chroot?
you can install it with:
sudo mhwd-kernel -i linux515

1 Like

As mentioned, I have to wait a long time till I get a TTY console. I was able to log into the console, and instantly enabled SSH, so I am currently logged into my laptop via another device.

i see, so can you install the kernel using ssh? if so install it, reboot and see if it helped

So I tried as you mentioned:

❯ sudo mhwd-kernel -i linux515
:: Synchronizing package databases...
 core                                                             163,0 KiB   827 KiB/s 00:00 [#######################################################] 100% extra                                                           1834,1 KiB  9,95 MiB/s 00:00 [#######################################################] 100% community                                                          7,4 MiB  12,0 MiB/s 00:01 [#######################################################] 100% multilib                                                         175,4 KiB   909 KiB/s 00:00 [#######################################################] 100%resolving dependencies...
looking for conflicting packages...

Packages (2) linux515-5.15.74-3  linux515-virtualbox-host-modules-6.1.38-12

Total Download Size:   101,32 MiB
Total Installed Size:  105,82 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 linux515-5.15.74-3-x86_64                                        101,1 MiB  1990 KiB/s 00:52 [#######################################################] 100% linux515-virtualbox-host-modules-6.1.38-12-x86_64                261,7 KiB  1744 KiB/s 00:00 [#######################################################] 100% Total (2/2)                                                      101,3 MiB  1988 KiB/s 00:52 [#######################################################] 100%
(2/2) checking keys in keyring                                                                [#######################################################] 100%
(2/2) checking package integrity                                                              [#######################################################] 100%
(2/2) loading package files                                                                   [#######################################################] 100%
(2/2) checking for file conflicts                                                             [#######################################################] 100%
(2/2) checking available disk space                                                           [#######################################################] 100%
:: Processing package changes...
(1/2) installing linux515                                                                     [#######################################################] 100%
Optional dependencies for linux515
    wireless-regdb: to set the correct wireless channels of your country [installed]
(2/2) installing linux515-virtualbox-host-modules                                             [#######################################################] 100%
===> You must load vboxdrv module before starting VirtualBox:
===> # modprobe vboxdrv
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.74-3-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [plymouth]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.74-3-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [plymouth]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.

Upon reboot, however I am still stuck like before. I cannot see any DisplayManager UI / TTY console

just to be sure check if you are using the 515:
uname -r
also rerun the update again:
sudo pacman -Syyu
any errors from it?

Okay I can report that updating the kernel to 5.15 has solved the issue. Thank you so much. Would you happen to know what could have gone haywired here?
Was this update supposed to be some breaking change that I needed to keep in mind?

Also no errors when conducting pacman -Syyu so everything is working well.

I was curious as to why I would need to jump a large leap from 5.10 to 5.15?

i just noticed several people on forum having the same issue with the 5.10 kernel using amd, and switching to newer kernel resolved it…
and have no idea what could be the reason for it…

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.