[SOLVED] cannot boot anymore since 6.4.7

crequill · 2023-08-16 10:55:00

Hello,

On my old Dell T1650, since 6.4.7 I can’t boot anymore: system hangs after:

:: running early hook  [udev]
Starting systemd-udevd version 254.1-1-arch

no trace in journalctl. It's not the TPM problem.
6.4.4 and 6.1.45-1-lts kernels boots.

Last edited by crequill (2023-10-27 14:41:02)

seth · 2023-08-16 12:30:22

Remove the "quiet" parameter, possibly add https://wiki.archlinux.org/title/Genera … l_messages
Also try to boot "nomodeset" and if you're using the nvidia driver, make sure to add "nvidia-drm.modeset=1" to the kernel parameters.

crequill · 2023-08-16 13:58:02

Thanks,

I don’t have quiet parameter.
I try with nomodeset and nvidia-drm.modeset=1 and I can boot. Thanks but I cannot use it as I am with nouveau driver. Nouveau requires kernel mode-setting.

seth · 2023-08-16 14:04:15

The idea of nomodeset was to get you access to a terminal (and see where things fall apart), not to be a solution (it's not, it's only good for debugging)

Can you still boot the multi-user.target (2nd link below, w/o nomodeset)?
If not, don't exit the failign boot w/ the power button, use https://wiki.archlinux.org/title/Keyboa … el_(SysRq) so we can hopefully get a useful journal.

I suspect it's a nouveau issue, though.

crequill · 2023-08-16 15:26:44

I can't boot multi-user.target with linux 6.4.10 without nomodeset.
I boot without nomodeset and reboot with sysrq. I get some log.

août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: bios: version 70.18.83.00.08
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: fb: 512 MiB DDR3
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: VRAM: 512 MiB
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB outp 00: 02000360 00000000
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB outp 01: 02000362 00020010
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB outp 02: 028003a6 0f220010
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB outp 03: 01011380 00000000
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB outp 04: 08011382 00020010
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB outp 05: 088113c6 0f220010
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB conn 00: 00101064
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: DCB conn 01: 00202165
août 16 16:45:01 tarac kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
août 16 16:45:01 tarac kernel: ------------[ cut here ]------------
août 16 16:45:01 tarac kernel: list_add corruption. prev->next should be next (ffff94608704e270), but was 0000000000000000. (prev=ffff946087051020).
août 16 16:45:01 tarac kernel: WARNING: CPU: 2 PID: 113 at lib/list_debug.c:30 __list_add_valid+0x83/0xa0
août 16 16:45:01 tarac kernel: Modules linked in: usbhid nouveau(+) drm_ttm_helper ttm video i2c_algo_bit mxm_wmi wmi drm_display_helper cec
août 16 16:45:01 tarac kernel: CPU: 2 PID: 113 Comm: modprobe Not tainted 6.4.10-arch1-1 #1 2d4402bf7ad4a7ea488c9261840b8101c9d1e712
août 16 16:45:01 tarac kernel: Hardware name: Dell Inc. Precision T1650/0C3YXR, BIOS A13 06/10/2013
août 16 16:45:01 tarac kernel: RIP: 0010:__list_add_valid+0x83/0xa0
août 16 16:45:01 tarac kernel: Code: eb e9 48 89 c1 48 c7 c7 00 ef e6 a1 e8 16 5f a8 ff 0f 0b eb d6 48 89 d1 48 89 c6 4c 89 c2 48 c7 c7 50 ef e6 a1 e8 fd 5e a8 ff <0f> 0b eb bd 48 89 f2 48 89 c1 48 89 fe 48 c7 c7 a0 ef e6 a1 e8 e4
août 16 16:45:01 tarac kernel: RSP: 0018:ffffbb4e4204b9a0 EFLAGS: 00010086
août 16 16:45:01 tarac kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: c0000000ffffefff
août 16 16:45:01 tarac kernel: RDX: 0000000000000000 RSI: 00000000ffffefff RDI: 0000000000000001
août 16 16:45:01 tarac kernel: RBP: ffff946087051000 R08: 0000000000000000 R09: ffffbb4e4204b830
août 16 16:45:01 tarac kernel: R10: 0000000000000003 R11: ffffffffa26ca868 R12: ffff946087051040
août 16 16:45:01 tarac kernel: R13: ffff946087051020 R14: ffff946087051020 R15: ffff94608704e000
août 16 16:45:01 tarac kernel: FS:  00007ff9195ec740(0000) GS:ffff946195d00000(0000) knlGS:0000000000000000
août 16 16:45:01 tarac kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
août 16 16:45:01 tarac kernel: CR2: 000055a198378020 CR3: 0000000100d38004 CR4: 00000000001706e0
août 16 16:45:01 tarac kernel: Call Trace:
août 16 16:45:01 tarac kernel:  <TASK>
août 16 16:45:01 tarac kernel:  ? __list_add_valid+0x83/0xa0
août 16 16:45:01 tarac kernel:  ? __warn+0x81/0x130
août 16 16:45:01 tarac kernel:  ? __list_add_valid+0x83/0xa0
août 16 16:45:01 tarac kernel:  ? report_bug+0x171/0x1a0
août 16 16:45:01 tarac kernel:  ? prb_read_valid+0x1b/0x30
août 16 16:45:01 tarac kernel:  ? handle_bug+0x3c/0x80
août 16 16:45:01 tarac kernel:  ? exc_invalid_op+0x17/0x70
août 16 16:45:01 tarac kernel:  ? asm_exc_invalid_op+0x1a/0x20
août 16 16:45:01 tarac kernel:  ? __list_add_valid+0x83/0xa0
août 16 16:45:01 tarac kernel:  __drm_connector_init+0x31a/0x480
août 16 16:45:01 tarac kernel:  nouveau_connector_create+0x2b2/0x7d0 [nouveau e3b87019dce744d67fbad7dbafb8614fa6c61809]
août 16 16:45:01 tarac kernel:  nv50_display_create+0x530/0xbd0 [nouveau e3b87019dce744d67fbad7dbafb8614fa6c61809]
août 16 16:45:01 tarac kernel:  nouveau_display_create+0x38e/0x510 [nouveau e3b87019dce744d67fbad7dbafb8614fa6c61809]
août 16 16:45:01 tarac kernel:  nouveau_drm_device_init+0x1aa/0x9b0 [nouveau e3b87019dce744d67fbad7dbafb8614fa6c61809]
août 16 16:45:01 tarac kernel:  nouveau_drm_probe+0x12c/0x280 [nouveau e3b87019dce744d67fbad7dbafb8614fa6c61809]
août 16 16:45:01 tarac kernel:  local_pci_probe+0x45/0xa0
août 16 16:45:01 tarac kernel:  pci_device_probe+0xc1/0x260
août 16 16:45:01 tarac kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
août 16 16:45:01 tarac kernel:  really_probe+0x19e/0x3e0
août 16 16:45:01 tarac kernel:  ? __pfx___driver_attach+0x10/0x10
août 16 16:45:01 tarac kernel:  __driver_probe_device+0x78/0x160
août 16 16:45:01 tarac kernel:  driver_probe_device+0x1f/0x90
août 16 16:45:01 tarac kernel:  __driver_attach+0xd2/0x1c0
août 16 16:45:01 tarac kernel:  bus_for_each_dev+0x88/0xd0
août 16 16:45:01 tarac kernel:  bus_add_driver+0x116/0x220
août 16 16:45:01 tarac kernel:  driver_register+0x59/0x100
août 16 16:45:01 tarac kernel:  ? __pfx_nouveau_drm_init+0x10/0x10 [nouveau e3b87019dce744d67fbad7dbafb8614fa6c61809]
août 16 16:45:01 tarac kernel:  do_one_initcall+0x5d/0x240
août 16 16:45:01 tarac kernel:  do_init_module+0x60/0x240
août 16 16:45:01 tarac kernel:  __do_sys_finit_module+0xad/0x130
août 16 16:45:01 tarac kernel:  do_syscall_64+0x60/0x90
août 16 16:45:01 tarac kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
août 16 16:45:01 tarac kernel:  ? do_syscall_64+0x6c/0x90
août 16 16:45:01 tarac kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
août 16 16:45:01 tarac kernel:  ? do_syscall_64+0x6c/0x90
août 16 16:45:01 tarac kernel:  ? exc_page_fault+0x7f/0x180
août 16 16:45:01 tarac kernel:  entry_SYSCALL_64_after_hwframe+0x77/0xe1
août 16 16:45:01 tarac kernel: RIP: 0033:0x7ff9197001ad
août 16 16:45:01 tarac kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 53 eb 12 00 f7 d8 64 89 01 48
août 16 16:45:01 tarac kernel: RSP: 002b:00007fff84614c08 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
août 16 16:45:01 tarac kernel: RAX: ffffffffffffffda RBX: 000055a198375bb0 RCX: 00007ff9197001ad
août 16 16:45:01 tarac kernel: RDX: 0000000000000000 RSI: 000055a1963e7cb2 RDI: 000000000000000b
août 16 16:45:01 tarac kernel: RBP: 000055a1963e7cb2 R08: 0000000000000000 R09: 00007fff84614d40
août 16 16:45:01 tarac kernel: R10: 000000000000000b R11: 0000000000000246 R12: 0000000000060000
août 16 16:45:01 tarac kernel: R13: 000055a198375c30 R14: 0000000000000000 R15: 000055a1983781b0
août 16 16:45:01 tarac kernel:  </TASK>
août 16 16:45:01 tarac kernel: ---[ end trace 0000000000000000 ]---
août 16 16:45:01 tarac kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000

seth · 2023-08-16 20:03:46

Same as https://bbs.archlinux.org/viewtopic.php?id=287681
=> https://gitlab.freedesktop.org/drm/nouveau/-/issues

dakota · 2023-09-05 21:00:52

Thanks Seth!

I was experiencing the exact same symptoms as the OP.

The workaround you recommended in the linked thread seems to be working for me, but I'm confused about a few things.

Summary

1. Removed xf86-video-nouveau [pacman -Rs]
2. Installed nvidia-390xx-dkms and nvidia-390xx-utils from the AUR
3. Installed linux-headers
4. Modified mkinitcpio.conf modules...
a. removed (nouveau)
b. added (nvidia nvidia_modeset nvidia_uvm nvidia_drm)
5. For systemd-boot...
a. Added "console-mode auto" to /boot/loader/loader.conf [so console text would not be super-sized. Boot menu is now very small, but console text is nicely readable.]
6. blacklisted "nouveau" by creating a new file: /etc/modprobe.d/nouveau.conf [blacklist nouveau]
7. Regenerated the initramfs [mkinitcpio -p linux]

Questions
1. Did I need to install linux-headers? [I did not install linux-lts-headers, but the lts kernel still boots]
2. Even though I removed the xf86-video-nouveau package, removed (nouveau) from the modules hook, and blacklisted nouveau I still see the following:

$ mkinitcpio -M
--------------------
...
nouveau
nvidia
nvidia_drm
...

Is this normal and expected?

Cheers,

--------------------
Edit - spelling

Last edited by dakota (2023-09-05 22:43:01)

seth · 2023-09-05 21:14:07

* You need the header packages of every kernel you want to boot, "dkms status" to see which modules and for what kernel are available
* nvidia-390xx-utils blacklists nouveau in /usr/lib/modprobe.d - no need for a local config
* do you have "kms" in the HOOKS array?
* you only regenerated the linux initramfs, the linux-lts one will probably still have a non-blacklisted nouveau module inside and you end up loading that
* the presence of xf86-video-nouveau is irrelevant to all of this, it's only used with nouveau

dakota · 2023-09-05 23:13:10

Wow. You really pack a lot into a few words!

1. Installed linux-lts-headers

$ dkms status
--------------------
nvidia/390.157, 6.1.51-1-lts, x86_64: installed
nvidia/390.157, 6.4.12-arch1-1, x86_64: installed

2. Removed the blacklist file: /etc/modprobe.d/nouveau.conf [as you noted, it is alread blacklisted at /usr/lib/modprobe.d]
3. Added kms to the hooks array [base udev autodetect modconf kms block mdadm_udev keyboard consolefont filesystems fsck]
4. Regenerated the initramfs for all kernels [mkinitcpio -P]

Thank You!

Cheers,

--------------------
Edit - I wanted lsmod, not mkinitcpio -M

lsmod = Show the status of modules in the Linux Kernel
mkinitcpio -M = Display modules found via autodetection

Last edited by dakota (2023-09-05 23:21:04)

crequill · 2023-10-27 12:40:06

Hi,

Corrected with linux 6.5.9.

seth · 2023-10-27 12:45:03

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2023-08-16 10:55:00

[SOLVED] cannot boot anymore since 6.4.7

#2 2023-08-16 12:30:22

Re: [SOLVED] cannot boot anymore since 6.4.7

#3 2023-08-16 13:58:02

Re: [SOLVED] cannot boot anymore since 6.4.7

#4 2023-08-16 14:04:15

Re: [SOLVED] cannot boot anymore since 6.4.7

#5 2023-08-16 15:26:44

Re: [SOLVED] cannot boot anymore since 6.4.7

#6 2023-08-16 20:03:46

Re: [SOLVED] cannot boot anymore since 6.4.7

#7 2023-09-05 21:00:52

Re: [SOLVED] cannot boot anymore since 6.4.7

#8 2023-09-05 21:14:07

Re: [SOLVED] cannot boot anymore since 6.4.7

#9 2023-09-05 23:13:10

Re: [SOLVED] cannot boot anymore since 6.4.7

#10 2023-10-27 12:40:06

Re: [SOLVED] cannot boot anymore since 6.4.7

#11 2023-10-27 12:45:03

Re: [SOLVED] cannot boot anymore since 6.4.7

Board footer