External e-gpu nvidia stopped working (SOLVED: mesa)

[kkazakov]

I have a 3060ti in an external Lenovo Legion Booststation.

Until yesterday’s update, I had no issues with the e-gpu ( default built-in drivers ), display from the enclosure worked, everything was fine, out of the box. I have no need to install proprietary nvidia drivers.

However, yesterday several packages were updated with yay -Syu, including kernel 6.2.7. After reboot, all I get is a stuck cursor and no login screen is shown. Cannot switch to console, nothing works, it’s frozen.

I downgraded the kernel several times ( sudo downgrade linux ), going one after the other until 6.2.2, but at every try, nothing helped. Still freezes.

When I run it without the e-gpu connected through the thunderbolt, it works fine, I can login. If I connect it, while logged in - it freezes again.

I’m open to any ideas …

[petsam]

@kkazakov

I’m open to any ideas …

Check the logs (journal and Xorg).

[kkazakov]

That’s all I can see in the logs:

мар 22 18:18:50 t14e kernel: ------------[ cut here ]------------
мар 22 18:18:50 t14e kernel: nouveau 0000:52:00.0: timeout
мар 22 18:18:50 t14e kernel: WARNING: CPU: 2 PID: 702 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0xfd/0x110 [nouveau]
мар 22 18:18:50 t14e kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq cmac algif_hash algif_skcipher af_alg nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reje>
мар 22 18:18:50 t14e kernel:  snd_soc_core intel_pmc_bxt ee1004 r8152 platform_profile snd_compress ecdh_generic iTCO_vendor_support mtd intel_rapl_msr mii kvm ac97_bus snd_hda_codec_hdmi i9>
мар 22 18:18:50 t14e kernel:  int3400_thermal intel_hid acpi_thermal_rel acpi_pad sparse_keymap mac_hid fuse loop dm_mod ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid sdhc>
мар 22 18:18:50 t14e kernel: CPU: 2 PID: 702 Comm: gnome-shell Tainted: G        W          6.2.7-arch1-1 #1 d0ef1d2ba4aa7f22be04df39dde66a4c3cc73dc4
мар 22 18:18:50 t14e kernel: Hardware name: LENOVO 20W00094BM/20W00094BM, BIOS N34ET54W (1.54 ) 11/21/2022
мар 22 18:18:50 t14e kernel: RIP: 0010:g84_bar_flush+0xfd/0x110 [nouveau]
мар 22 18:18:50 t14e kernel: Code: 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 e5 13 3d e9 48 89 da 48 c7 c7 e7 a6 4c c1 48 89 c6 e8 33 32 ba e8 <0f> 0b eb aa e8 1a d8 82 e9 >
мар 22 18:18:50 t14e kernel: RSP: 0018:ffffa183c1d277c0 EFLAGS: 00010082
мар 22 18:18:50 t14e kernel: RAX: 0000000000000000 RBX: ffff960dc2008ac0 RCX: 0000000000000027
мар 22 18:18:50 t14e kernel: RDX: ffff9616f76a1648 RSI: 0000000000000001 RDI: ffff9616f76a1640
мар 22 18:18:50 t14e kernel: RBP: ffff960dc54772b8 R08: 0000000000000000 R09: ffffa183c1d27650
мар 22 18:18:50 t14e kernel: R10: 0000000000000003 R11: ffffffffabcc9a68 R12: 0000000000000246
мар 22 18:18:50 t14e kernel: R13: 00000000fb000006 R14: 0000000000000001 R15: ffff960e054eb490
мар 22 18:18:50 t14e kernel: FS:  00007fc38165bb40(0000) GS:ffff9616f7680000(0000) knlGS:0000000000000000
мар 22 18:18:50 t14e kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
мар 22 18:18:50 t14e kernel: CR2: 00007f77372f59d0 CR3: 000000011e4ca004 CR4: 0000000000770ee0
мар 22 18:18:50 t14e kernel: PKRU: 55555554
мар 22 18:18:50 t14e kernel: Call Trace:
мар 22 18:18:50 t14e kernel:  <TASK>
мар 22 18:18:50 t14e kernel:  nv50_instobj_release+0x34/0xc0 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  nvkm_ramht_update+0xfd/0x170 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  nvkm_ramht_insert+0xa2/0xe0 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  nvkm_disp_chan_child_new+0xae/0xe0 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  nvkm_ioctl_new+0x14d/0x290 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  ? __pfx_nvkm_disp_chan_child_new+0x10/0x10 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  ? __pfx_nvkm_dma_oclass_fifo_new+0x10/0x10 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  nvkm_ioctl+0x10b/0x240 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  nvif_object_ctor+0x111/0x190 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  nv50_wndw_prepare_fb+0x263/0x340 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  drm_atomic_helper_prepare_planes+0x75/0x200
мар 22 18:18:50 t14e kernel:  nv50_disp_atomic_commit+0x8f/0x1b0 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  drm_atomic_commit+0x97/0xd0
мар 22 18:18:50 t14e kernel:  ? __pfx___drm_printfn_info+0x10/0x10
мар 22 18:18:50 t14e kernel:  drm_atomic_helper_set_config+0x74/0xb0
мар 22 18:18:50 t14e kernel:  drm_mode_setcrtc+0x512/0x7e0
мар 22 18:18:50 t14e kernel:  ? __pfx_drm_mode_setcrtc+0x10/0x10
мар 22 18:18:50 t14e kernel:  drm_ioctl_kernel+0xca/0x170
мар 22 18:18:50 t14e kernel:  drm_ioctl+0x233/0x410
мар 22 18:18:50 t14e kernel:  ? __pfx_drm_mode_setcrtc+0x10/0x10
мар 22 18:18:50 t14e kernel:  nouveau_drm_ioctl+0x5a/0xb0 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  __x64_sys_ioctl+0x91/0xd0
мар 22 18:18:50 t14e kernel:  do_syscall_64+0x5c/0x90
мар 22 18:18:50 t14e kernel:  ? __pm_runtime_suspend+0x6e/0x100
мар 22 18:18:50 t14e kernel:  ? nouveau_drm_ioctl+0x7d/0xb0 [nouveau 2452dfc2f38b065c0607ad74e3eb915f17817093]
мар 22 18:18:50 t14e kernel:  ? __x64_sys_ioctl+0xac/0xd0
мар 22 18:18:50 t14e kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
мар 22 18:18:50 t14e kernel:  ? do_syscall_64+0x6b/0x90
мар 22 18:18:50 t14e kernel:  ? exc_page_fault+0x74/0x170
мар 22 18:18:50 t14e kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
мар 22 18:18:50 t14e kernel: RIP: 0033:0x7fc385b1553f
мар 22 18:18:50 t14e kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 >
мар 22 18:18:50 t14e kernel: RSP: 002b:00007ffe164e9fc0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
мар 22 18:18:50 t14e kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc385b1553f
мар 22 18:18:50 t14e kernel: RDX: 00007ffe164ea050 RSI: 00000000c06864a2 RDI: 000000000000000f
мар 22 18:18:50 t14e kernel: RBP: 00007ffe164ea050 R08: 0000000000000000 R09: 0000564c1afca2f0
мар 22 18:18:50 t14e kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c06864a2
мар 22 18:18:50 t14e kernel: R13: 000000000000000f R14: 0000564c1c0e17d0 R15: 0000564c1b8e5790
мар 22 18:18:50 t14e kernel:  </TASK>
мар 22 18:18:50 t14e kernel: ---[ end trace 0000000000000000 ]---
мар 22 18:19:09 t14e kernel: thunderbolt 0000:00:0d.3: 1: timeout reading config space 2 from 0x2c
мар 22 18:19:09 t14e kernel: thunderbolt 1-1: reading DROM failed: -5
мар 22 18:19:11 t14e gnome-session[692]: gnome-session-binary[692]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
мар 22 18:19:11 t14e gnome-session-binary[692]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached

[manuel]

Could be the update of mesa?

[kkazakov]

Thank you! I’ve downgraded mesa package to the last (22.3.6) before the upgrade (23.0.0 - this seems to be broken here), upgraded the kernel back to latest (6.2.7) and it all works now!