Nvidia Prime "Missing ENDBR" kernel trap

My new adventure is building a new desktop with a used RTX 2080 Ti. I confirmed the card works fine in the chassis by temporarily installing Windows on a second drive and running Cyberpunk 2077 in benchmark mode on Ultra settings. In Manjaro, the nonfree driver throws a traceback in dmesg. I have a few ideas to workaround this, but thought I’d share the logs as I was working through it.

Here’s sudo inxi -G with the DP cable plugged into the Nvidia card:

Graphics:
  Device-1: Intel Raptor Lake-S UHD Graphics driver: i915 v: kernel
  Device-2: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] driver: N/A
  Display: server: X.org v: 1.21.1.6 driver: N/A tty: 280x57
  API: OpenGL Message: GL data unavailable in console for root.

The nonfree installer option stalled on boot (manjaro-kde-22.0-221224-linux61.iso), so I started with the nouveau driver, and then installed video-hybrid-intel-nvidia-prime. That got me far enough to see the kernel trace log. I’m guessing the workaround will be to roll back to an older driver version, or just remove the video-linux driver using mhwd (nope, that didn’t help). I’ll try to remember to report back if I get it running.

Here’s package versions:

pacman -Q | grep nvidia
lib32-nvidia-utils 525.60.11-1
linux61-nvidia 525.60.11-2
mhwd-nvidia 525.60.11-2
mhwd-nvidia-390xx 390.157-1
mhwd-nvidia-470xx 470.161.03-1
nvidia-prime 1.0-4
nvidia-utils 525.60.11-2

Kernel: Linux 6.1.1-1-MANJARO #1 SMP PREEMPT_DYNAMIC Wed Dec 21 23:21:50 UTC 2022 x86_64 GNU/Linux

Here’s mhwd -li:

> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
video-hybrid-intel-nvidia-prime            2021.11.04               false            PCI

Here’s the trace:

[    4.439603] nvidia-nvlink: Nvlink Core is being initialized, major device number 236

[    4.439621] traps: Missing ENDBR: _nv012292rm+0x0/0x10 [nvidia]
[    4.439805] ------------[ cut here ]------------
[    4.439806] kernel BUG at arch/x86/kernel/traps.c:255!
[    4.439808] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
[    4.439811] fbcon: Taking over console
[    4.439813] CPU: 8 PID: 435 Comm: systemd-modules Tainted: P           OE      6.1.1-1-MANJARO #1 58eeef856bad441bca33a8abb39f91301fd24d8d
[    4.439815] Hardware name: Gigabyte Technology Co., Ltd. Z690 AORUS ULTRA/Z690 AORUS ULTRA, BIOS F22 12/07/2022
[    4.439816] RIP: 0010:exc_control_protection+0xc2/0xd0
[    4.439819] Code: fa ff 45 31 c9 49 89 d8 b9 09 00 00 00 48 8b 93 80 00 00 00 be fc 00 00 00 48 c7 c7 89 de 03 95 e8 73 f4 47 ff e9 64 ff ff ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 90 66 0f 1f 00 55 53 48 89
[    4.439821] RSP: 0018:ffff983643773bb8 EFLAGS: 00010002
[    4.439823] RAX: 0000000000000033 RBX: ffff983643773bd8 RCX: 0000000000000027
[    4.439824] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8b7d5f821660
[    4.439824] RBP: 0000000000000003 R08: 0000000000000000 R09: ffff983643773a50
[    4.439825] R10: 0000000000000003 R11: ffff8b7d7fbab128 R12: 0000000000000000
[    4.439826] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[    4.439827] FS:  00007f9beb04d080(0000) GS:ffff8b7d5f800000(0000) knlGS:0000000000000000
[    4.439828] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    4.439829] CR2: 00007f9be6009000 CR3: 000000010167e001 CR4: 0000000000f70ee0
[    4.439829] PKRU: 55555554
[    4.439830] Call Trace:
[    4.439832]  <TASK>
[    4.439833]  asm_exc_control_protection+0x26/0x30
[    4.439834] RIP: 0010:_nv012292rm+0x0/0x10 [nvidia]
[    4.439995] Code: 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 e8 27 c2 1f 00 48 83 c4 08 48 89 c7 e9 bb ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 89 f7 e9 18 08 00 00 0f 1f 84 00 00 00 00 00 48 89 f7 e9 18 08
[    4.439997] RSP: 0018:ffff983643773c80 EFLAGS: 00010202
[    4.439998] RAX: ffffffffc13aaee0 RBX: ffffffffc43de6d0 RCX: 0000000000000000
[    4.439999] RDX: 0000000000098628 RSI: 0000000000000010 RDI: ffffffffc43de6d0
[    4.440000] RBP: ffff8b75e7afdfe0 R08: ffff983643773c10 R09: ffffffffc43de710
[    4.440001] R10: ffffffffc43a95b0 R11: 0000000000000000 R12: 0000000000000010
[    4.440002] R13: ffff8b75e7afb000 R14: 00007f9beb901343 R15: ffff983643773e00
[    4.440003]  ? _nv038334rm+0x20/0x20 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.440178]  _nv012290rm+0x24/0xe0 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.440351]  _nv038335rm+0xe/0xa0 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.440524]  _nv038338rm+0x1d/0x30 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.440696]  _nv038340rm+0x2f/0x40 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.440868]  _nv017011rm+0x15/0x70 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.440996]  _nv000690rm+0x9/0x20 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.441122]  ? cdev_add+0x50/0x70
[    4.441124]  rm_init_rm+0x17/0x60 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.441263]  nvidia_init_module+0x24e/0x622 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.441393]  ? nvidia_init_module+0x622/0x622 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.441519]  nvidia_frontend_init_module+0x50/0x94 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.441646]  ? nvidia_init_module+0x622/0x622 [nvidia 36a21714ae2795812fa554f17149bf9aa2fd12e7]
[    4.441772]  do_one_initcall+0x5a/0x220
[    4.441774]  do_init_module+0x4a/0x1e0
[    4.441777]  __do_sys_init_module+0x17f/0x1b0
[    4.441779]  do_syscall_64+0x5c/0x90
[    4.441780]  ? do_user_addr_fault+0x1e0/0x6a0
[    4.441782]  ? do_syscall_64+0x6b/0x90
[    4.441783]  ? exc_page_fault+0x74/0x170
[    4.441785]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[    4.441787] RIP: 0033:0x7f9beb321eae
[    4.441789] Code: 48 8b 0d dd ee 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d aa ee 0c 00 f7 d8 64 89 01 48
[    4.441791] RSP: 002b:00007ffd24eab698 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[    4.441793] RAX: ffffffffffffffda RBX: 0000555e6e19d880 RCX: 00007f9beb321eae
[    4.441794] RDX: 00007f9beb901343 RSI: 000000000589e0e8 RDI: 00007f9be076b010
[    4.441795] RBP: 00007f9beb901343 R08: 0000555e6e19dad0 R09: 0000000000000000
[    4.441796] R10: 0000000000000005 R11: 0000000000000246 R12: 0000000000020000
[    4.441797] R13: 0000555e6e19d900 R14: 0000555e6e19d880 R15: 0000555e6e19dd30
[    4.441799]  </TASK>
[    4.441799] Modules linked in: pcc_cpufreq(-) fjes(-) acpi_cpufreq(-) nvidia(POE+) video wmi intel_hid vfat sparse_keymap fat acpi_tad acpi_pad mac_hid crypto_user fuse bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvme nvme_core spi_intel_pci crc32c_intel xhci_pci spi_intel nvme_common xhci_pci_renesas
[    4.441809] ---[ end trace 0000000000000000 ]---

Re-reading the trace I noticed that the meaningful error was actually the traps: Missing ENDBR line. That lead me to a similar thread on the nvidia forum (that I can’t link to yet, since I’m new here) where the suggestion is to disable Indirect branch tracking with kernel parameter ibt=off.

The system is booting and so I’ll mark this as solved.

1 Like

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