Nvidia kernel causes >60 sec boot on xps 9510 since a few weeks

Greetings
XPS 9510 laptop here, intel i7 and rtx3050 mobile hybrid running eos
since an update a week or two ago my boot is no longer graphical (lots of diagnostic text scrolls while starting) - then gets stuck for 30 secs on a line that says something about systemd and modules.

after 30 seconds the scren goes blank with only a cursor in the top left corner - this stays for 60 secs.

after this the gdm greeter appears and I can use my system.

reading the logs I find various notifications about systemd unable to start systemd (?) so here goes, maybe I can provide anything useful. I can not identify what module it is that fails to start.

andreas@moya:~$ systemd-analyze blame
1min 30.240s systemd-modules-load.service
       230ms dev-nvme1n1p2.device
       149ms ldconfig.service
       142ms systemd-rfkill.service
       117ms user@1000.service

and

andreas@moya:~$ systemctl list-units --failed
  UNIT                         LOAD   ACTIVE SUB    DESCRIPTION        
● systemd-modules-load.service loaded failed failed Load Kernel Modules

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
andreas@moya:~$ 

but which is it?
I cannot find / identify it. Any help?

removing all things nvidia solves it for now. (mostly using it for video playback and occasional steam so no biggie but hey…) :wink:

I used nvidia-installer-dkms in the past and after some reading now using nvidia-inst - but both lead to the same symptoms.

  • 30 sec. wait time during CLI boot
  • 60 sec. nothing happens / seems frozen > then gdm login appears.

I am running “Running nvidia-bug-report.sh…” now but it takes ages, will attach once completed.

thanks

Andreas

jun 07 08:24:39 moya systemd[1]: Finished File System Check on /dev/disk/by-uuid/A871-BC57.
jun 07 08:24:39 moya audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk>
jun 07 08:24:39 moya kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance w>
jun 07 08:24:39 moya kernel: wmi_bus wmi_bus-PNP0C14:02: WQBC data block query control method not found
jun 07 08:24:39 moya kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance w>
jun 07 08:24:39 moya kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 236
jun 07 08:24:39 moya kernel: 
jun 07 08:24:39 moya kernel: traps: Missing ENDBR: _nv011433rm+0x0/0x10 [nvidia]
jun 07 08:24:39 moya kernel: ------------[ cut here ]------------
jun 07 08:24:39 moya kernel: kernel BUG at arch/x86/kernel/traps.c:252!
jun 07 08:24:39 moya kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
jun 07 08:24:39 moya kernel: CPU: 14 PID: 326 Comm: systemd-modules Tainted: P           OE     5.18.1-arch1-1 #1 aeb6a>
jun 07 08:24:39 moya kernel: Hardware name: Dell Inc. XPS 15 9510/01V4T3, BIOS 1.9.0 03/17/2022
jun 07 08:24:39 moya kernel: RIP: 0010:exc_control_protection+0xc2/0xd0
jun 07 08:24:39 moya kernel: Code: 8b 93 80 00 00 00 be f9 00 00 00 48 c7 c7 83 ab 26 99 e8 d1 f1 4f ff e9 72 ff ff ff >
jun 07 08:24:39 moya kernel: RSP: 0018:ffffb0cfc0eb3bc8 EFLAGS: 00010002
jun 07 08:24:39 moya kernel: RAX: 0000000000000033 RBX: ffffb0cfc0eb3be8 RCX: 0000000000000027
jun 07 08:24:39 moya kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff92147f7a16a0
jun 07 08:24:39 moya kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: ffffb0cfc0eb39e8
jun 07 08:24:39 moya kernel: R10: 0000000000000003 R11: ffffffff99acaa08 R12: 0000000000000000
jun 07 08:24:39 moya kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
jun 07 08:24:39 moya kernel: FS:  00007fa921b48380(0000) GS:ffff92147f780000(0000) knlGS:0000000000000000
jun 07 08:24:39 moya kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jun 07 08:24:39 moya kernel: CR2: 00007fa91d6b7000 CR3: 0000000107d08006 CR4: 0000000000f70ee0
jun 07 08:24:39 moya kernel: PKRU: 55555554
jun 07 08:24:39 moya kernel: Call Trace:
jun 07 08:24:39 moya kernel:  <TASK>
jun 07 08:24:39 moya kernel:  asm_exc_control_protection+0x22/0x30
jun 07 08:24:39 moya kernel: RIP: 0010:_nv011433rm+0x0/0x10 [nvidia]
jun 07 08:24:39 moya kernel: Code: 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 e8 d7 0f 1e 00 48 83 c4 08 48 89 c7 e9 bb >
jun 07 08:24:39 moya kernel: RSP: 0018:ffffb0cfc0eb3c90 EFLAGS: 00010202
jun 07 08:24:39 moya kernel: RAX: ffffffffc0de9370 RBX: ffffffffc2ffdaf0 RCX: 0000000000000000
jun 07 08:24:39 moya kernel: RDX: 0000000000071818 RSI: 0000000000000010 RDI: ffffffffc2ffdaf0
jun 07 08:24:39 moya kernel: RBP: ffff92111a722fe0 R08: 0000000000000020 R09: ffffffffc2ffdb30
jun 07 08:24:39 moya kernel: R10: ffffffffc2fb4830 R11: 0000000000000000 R12: 0000000000000010
jun 07 08:24:39 moya kernel: R13: ffff92111a720000 R14: 00007fa921bab32c R15: ffffb0cfc0eb3e10
jun 07 08:24:39 moya kernel:  ? _nv034912rm+0x20/0x20 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  _nv011431rm+0x24/0xe0 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  _nv034913rm+0xe/0xa0 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  _nv034916rm+0x1d/0x30 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  _nv034918rm+0x2f/0x40 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  _nv015566rm+0x15/0x70 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  _nv000642rm+0x9/0x20 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  ? cdev_add+0x4d/0x60
jun 07 08:24:39 moya kernel:  rm_init_rm+0x17/0x60 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance w>
jun 07 08:24:39 moya kernel:  nvidia_init_module+0x242/0x613 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  ? nvidia_init_module+0x613/0x613 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  nvidia_frontend_init_module+0x50/0x91 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  ? nvidia_init_module+0x613/0x613 [nvidia b2c04aa1d16edd4206e36ab935006fb1999a128e]
jun 07 08:24:39 moya kernel:  do_one_initcall+0x5a/0x220
jun 07 08:24:39 moya kernel:  do_init_module+0x4a/0x240
jun 07 08:24:39 moya kernel:  __do_sys_init_module+0x138/0x1b0
jun 07 08:24:39 moya kernel:  ? __vm_munmap+0x90/0x110
jun 07 08:24:39 moya kernel:  do_syscall_64+0x5c/0x90
jun 07 08:24:39 moya kernel:  ? ksys_read+0x6f/0xf0
jun 07 08:24:39 moya kernel:  ? syscall_exit_to_user_mode+0x26/0x50
jun 07 08:24:39 moya kernel:  ? do_syscall_64+0x6b/0x90
jun 07 08:24:39 moya kernel:  ? exc_page_fault+0x74/0x170
jun 07 08:24:39 moya kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
jun 07 08:24:39 moya kernel: RIP: 0033:0x7fa92151299e
jun 07 08:24:39 moya kernel: Code: 48 8b 0d fd a3 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 >
jun 07 08:24:39 moya kernel: RSP: 002b:00007ffdf45aa4f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
jun 07 08:24:39 moya kernel: RAX: ffffffffffffffda RBX: 000055a2631eac40 RCX: 00007fa92151299e
jun 07 08:24:39 moya kernel: RDX: 00007fa921bab32c RSI: 0000000003cd2588 RDI: 00007fa9199e5010
jun 07 08:24:39 moya kernel: RBP: 00007fa9199e5010 R08: 0000000002061000 R09: 0000000000000000
jun 07 08:24:39 moya kernel: R10: 00000000000176f1 R11: 0000000000000246 R12: 00007fa921bab32c
jun 07 08:24:39 moya kernel: R13: 000055a2631ead10 R14: 000055a2631eaa30 R15: 000055a2631eae70
jun 07 08:24:39 moya kernel:  </TASK>
jun 07 08:24:39 moya kernel: Modules linked in: wmi(+) pcc_cpufreq(-) fjes(-) acpi_cpufreq(-) mac_hid rfkill i2c_hid in>
jun 07 08:24:39 moya kernel: ---[ end trace 0000000000000000 ]---
jun 07 08:24:39 moya kernel: RIP: 0010:exc_control_protection+0xc2/0xd0
jun 07 08:24:39 moya kernel: Code: 8b 93 80 00 00 00 be f9 00 00 00 48 c7 c7 83 ab 26 99 e8 d1 f1 4f ff e9 72 ff ff ff >
jun 07 08:24:39 moya kernel: RSP: 0018:ffffb0cfc0eb3bc8 EFLAGS: 00010002
jun 07 08:24:39 moya kernel: RAX: 0000000000000033 RBX: ffffb0cfc0eb3be8 RCX: 0000000000000027
jun 07 08:24:39 moya kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff92147f7a16a0
jun 07 08:24:39 moya kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: ffffb0cfc0eb39e8
jun 07 08:24:39 moya kernel: R10: 0000000000000003 R11: ffffffff99acaa08 R12: 0000000000000000
jun 07 08:24:39 moya kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
jun 07 08:24:39 moya kernel: FS:  00007fa921b48380(0000) GS:ffff92147f780000(0000) knlGS:0000000000000000
jun 07 08:24:39 moya kernel: acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance w>
jun 07 08:24:39 moya kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jun 07 08:24:39 moya kernel: acpi PNP0C14:05: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance w>
jun 07 08:24:39 moya kernel: CR2: 00007fa91d6b7000 CR3: 0000000107d08006 CR4: 0000000000f70ee0
jun 07 08:24:39 moya kernel: acpi PNP0C14:06: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance w>
jun 07 08:24:39 moya kernel: PKRU: 55555554
jun 07 08:24:39 moya kernel: acpi PNP0C14:07: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance w>
jun 07 08:24:39 moya kernel: usb 3-14: new full-speed USB device number 4 using xhci_hcd
jun 07 08:24:39 moya systemd[1]: systemd-modules-load.service: Main process exited, code=killed, status=11/SEGV
jun 07 08:24:39 moya systemd[1]: systemd-modules-load.service: Failed with result 'signal'.
jun 07 08:24:39 moya systemd[1]: Failed to start Load Kernel Modules.
jun 07 08:24:39 moya audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load >
jun 07 08:24:39 moya systemd[1]: Starting Apply Kernel Variables...
jun 07 08:24:39 moya systemd[1]: Finished Apply Kernel Variables.
jun 07 08:24:39 moya audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm=">
jun 07 08:24:39 moya kernel: ACPI: bus type thunderbolt registered

welcome at the forum… and sry to see you have such issue.
Also i do not think it is a general issue with nvidia-inst script, and more likely something between Kernel and Nvidia drivers?

First thing to check would be installing LTS kernel in addition to main one to see if it works for the Nvidia Driver.

In addition i would think this machine is an optimus hybrid GPU one? RTX 3050 nvidia + igpu iris intel?

indeed it is intel+nvidia hybrid.

I read that nvidia driver these days contains the optimus/prime functions so I did not bother experimenting with optimus or bumblebee . I’d rather have no nvidia accelleration than broken system. This laptop has a second M.2 for windows - that’s where I play games :wink:

endeavour is my daily workhorse - I just wonder why it broke all of a sudden (worked for 2 years without a problem using nvidia-dkms)

not trying to complain or fix, just offering help if someone wants to fix this alleged “bug”

also > changed the topic to reflect. thanks!

Andreas

a boot log could tell a story :wink:
https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

I have the same/similar problems on an RTX3070, the best solution is to downgrade back to the previous driver and stick them in IgnorePkg for the time being. Found some stuff on the Arch forum (but am at work ATM).

Does this add the nvidia modules to /etc/mkinitcpio.conf ?

no, it only adds DRM modestting on grub kernel line.

1 Like

removed nvidia-*

fuck this proprietary shit

sorry for short temper and lack of patience. if you ever need someone to test stuff on a mobile RTX let me know - for the moment I need a working laptop, sorry - busy week :frowning:

P.S. appreciate all the effort you put into this. been following your posts back with Antergos, too. <3

2 Likes