Happens to me too, driver 460 and 470, ubuntu 21.04, kernel 5.11.0-34-generic #36-Ubuntu SMP.
Changing driver to 460 and 450 with “Software and updates” didn’t solve it.
Needed to change it in the command line as @alex21975, but I also removed unused nvidia packages before reinstalling:
sudo apt purge nvidia-*
sudo apt autoremove
sudo apt install nvidia-driver-450-server
reboot
Is there any update on this ?
I have this issue with my Razer Blade 15 Advanced (NVIDIA GTX 1060 Max Q) running Ubuntu 20.04 LTS (470.57.02)
Can we get an update?
I’m also on Acer Aspire 7 with Nvidia GeForce GTX 1050, but with ubuntu 21.10.
I was able to solve it, as the way @alex21975 and @hdaniel mentioned, but with nvidia-driver-460-server:
sudo apt purge nvidia-*
sudo apt autoremove
sudo apt install nvidia-driver-460-server
Nowt the computer will not stuck on boot after suspend
but if I do
sudo service nvidia-suspend status
it will show
“Unit nvidia-suspend.service could not be found.”
Solving it with
NVIDIA Suspend fix
still shows me
"
nvidia-suspend.service - NVIDIA system suspend actions
Loaded: loaded (/etc/systemd/system/nvidia-suspend.service; enabled; vendor preset: enabled)
Active: inactive (dead)
"
and the logs shows
kernel: snd_hda_codec_hdmi hdaudioC1D0: Unable to sync register 0x7f0800. -5 kernel: snd_hda_intel 0000:01:00.1: can't change power state from D3cold to D0 (config space inaccessible)
I’m suspecting this thread contains two different issues.
All users that, when running
sudo lspci -xxx -d 10de:*
get the audio device’s pci config space with all 0xFF, please try if this helps:
if not already mentioned in this thread.
Method above to remove the nvidia audio device works for me.
Tried with 495 driver. Issue still persists unfortunately.
I found a kind of workaround. When the screen wakes from sleep (but goes black), use CTRL + ALT + F2 to switch to a terminal (terminal shows on the screen in a few seconds) and CTRL + ALT + F1 or F7 (depending on the system) to switch back to the graphical session. The screen will then work normally again (until the next time it goes to sleep).
The 495 driver seems to work, although this might be because I’ve tinkered around a lot when trying to fix previous driver versions. But I guess that it is worth trying the update. I do include some of my settings below, as those might be useful if the 495 driver is not working for you.
Getting the conformation on the installed driver.
user@device:~$ nvidia-smi
Tue Nov 9 09:58:24 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 495.44 Driver Version: 495.44 CUDA Version: 11.5 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 Quadro M1000M Off | 00000000:01:00.0 On | N/A |
| N/A 52C P8 N/A / N/A | 259MiB / 4043MiB | 22% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 1320 G /usr/lib/xorg/Xorg 158MiB |
| 0 N/A N/A 2710 G /usr/lib/xorg/Xorg 97MiB |
+-----------------------------------------------------------------------------+
Getting some of my settings listed (I had changed some of these while trying to change the memory handling at hibernation), see above.
user@device:~$ cat /proc/driver/nvidia/params
ResmanDebugLevel: 4294967295
RmLogonRC: 1
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 0
DeviceFileMode: 438
InitializeSystemMemoryAllocations: 1
UsePageAttributeTable: 4294967295
EnableMSI: 1
RegisterForACPIEvents: 1
EnablePCIeGen3: 0
MemoryPoolSize: 0
KMallocHeapMaxSize: 0
VMallocHeapMaxSize: 0
IgnoreMMIOCheck: 0
TCEBypassMode: 0
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
NvLinkDisable: 0
RmProfilingAdminOnly: 1
PreserveVideoMemoryAllocations: 1
EnableS0ixPowerManagement: 0
S0ixPowerManagementVideoMemoryThreshold: 256
DynamicPowerManagement: 3
DynamicPowerManagementVideoMemoryThreshold: 200
RegisterPCIDriver: 1
EnablePCIERelaxedOrderingMode: 0
EnableGpuFirmware: 18
RegistryDwords: ""
RegistryDwordsPerDevice: ""
RmMsg: ""
GpuBlacklist: ""
TemporaryFilePath: "/tmp-nvidia"
ExcludedGpus: ""
I’ve also looked at the hibernate, suspend and resume services, which seem to be inactive but loaded.
user@device:~$ sudo service nvidia-suspend status
● nvidia-suspend.service - NVIDIA system suspend actions
Loaded: loaded (/etc/systemd/system/nvidia-suspend.service; enabled; vendor preset: enabled)
Active: inactive (dead)
nov 09 09:52:10 device systemd[1]: Starting NVIDIA system suspend actions...
nov 09 09:52:10 device suspend[6680]: nvidia-suspend.service
nov 09 09:52:10 device logger[6680]: <13>Nov 9 09:52:10 suspend: nvidia-suspend.service
nov 09 09:52:11 device systemd[1]: nvidia-suspend.service: Succeeded.
nov 09 09:52:11 device systemd[1]: Finished NVIDIA system suspend actions.
nov 09 09:53:06 device systemd[1]: Starting NVIDIA system suspend actions...
nov 09 09:53:06 device suspend[7975]: nvidia-suspend.service
nov 09 09:53:06 device logger[7975]: <13>Nov 9 09:53:06 suspend: nvidia-suspend.service
nov 09 09:53:07 device systemd[1]: nvidia-suspend.service: Succeeded.
nov 09 09:53:07 device systemd[1]: Finished NVIDIA system suspend actions.
user@device:~$ sudo service nvidia-hibernate status
● nvidia-hibernate.service - NVIDIA system hibernate actions
Loaded: loaded (/etc/systemd/system/nvidia-hibernate.service; enabled; vendor preset: enabled)
Active: inactive (dead)
user@device:~$ sudo service nvidia-resume status
● nvidia-resume.service - NVIDIA system resume actions
Loaded: loaded (/etc/systemd/system/nvidia-resume.service; enabled; vendor preset: enabled)
Active: inactive (dead)
nov 09 09:52:39 device systemd[1]: Starting NVIDIA system resume actions...
nov 09 09:52:39 device suspend[7377]: nvidia-resume.service
nov 09 09:52:39 device logger[7377]: <13>Nov 9 09:52:39 suspend: nvidia-resume.service
nov 09 09:52:39 device systemd[1]: nvidia-resume.service: Succeeded.
nov 09 09:52:39 device systemd[1]: Finished NVIDIA system resume actions.
nov 09 09:54:07 device systemd[1]: Starting NVIDIA system resume actions...
nov 09 09:54:07 device suspend[8614]: nvidia-resume.service
nov 09 09:54:07 device logger[8614]: <13>Nov 9 09:54:07 suspend: nvidia-resume.service
nov 09 09:54:07 device systemd[1]: nvidia-resume.service: Succeeded.
nov 09 09:54:07 device systemd[1]: Finished NVIDIA system resume actions.
@generix weirdly enough, it didn’t only fix the reboot problem, but even the audio device pci problem was fixed. The second device had all ffs listed before. (I only have a single graphics card, but ever since the start the M1000M gets also recognized as a 940MX).
user@device:~$ sudo lspci -xxx -d 10de:*
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1000M] (rev a2)
00: de 10 b1 13 07 04 10 00 a2 00 00 03 00 00 80 00
10: 00 00 00 e4 0c 00 00 a0 00 00 00 00 0c 00 00 b0
20: 00 00 00 00 01 30 00 00 00 00 00 00 3c 10 d4 80
30: 00 00 00 00 60 00 00 00 00 00 00 00 ff 01 00 00
40: 3c 10 d4 80 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 00 00 00 01 00 00 00 ce d6 23 00 00 00 00 00
60: 01 68 03 00 08 00 00 00 05 78 81 00 38 0a e0 fe
70: 00 00 00 00 00 00 00 00 10 00 02 00 e1 8d 2c 01
80: 30 21 00 00 03 3d 46 00 43 01 01 11 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 13 00 04 00
a0: 00 00 00 00 0e 00 00 00 03 00 1f 00 00 00 00 00
b0: 00 00 00 00 09 00 14 01 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01:00.1 Audio device: NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX] (rev a1)
00: de 10 bc 0f 06 00 10 00 a1 00 03 04 00 00 80 00
10: 00 00 00 e5 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 ff 02 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 ce d6 23 00 00 00 00 00
60: 01 68 03 00 08 00 00 00 05 78 80 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 10 00 02 00 e1 8d 2c 01
80: 30 29 00 00 03 3d 45 00 03 01 01 11 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 13 00 04 00
a0: 00 00 00 00 0e 00 00 00 00 00 01 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Here is my nvidia-bug-report.log.gz (456.0 KB).
The only difference with my configuration (except for hardware) are the PreserveVideoMemoryAllocations and TemporaryFilePath params so the issue probably only occurs when PreserveVideoMemoryAllocations is disabled (0).
Hmm that might very well be related. I tried setting these because they were recommended above by @generix. But when I tried it in the past, with the 465 drivers, this didn’t help. Could you try changing these setting?
Please try follow the Arch manual for the TemporaryFilePath memory allocation, and see if you can come up with the same results that I did. I’m interested to see whether this makes a difference or not.
(Sorry for the late reply. The forum system didn’t allow me to send a third message in this topic unil now.)
I expected it would solve the issue but unfortunately it didn’t (also I had to update the initramfs for the modprobe settings to be applied at boot). Also, either way, I don’t see any errors in the kernel logs anymore, so maybe I’m now running into a different issue. (I’ve had issues with displayport before, but HDMI worked fine until 460.) Maybe you could try disabling PreserveVideoMemoryAllocations to see if the issue pops up again?
Okay, this was surprising to me, disabling PreserveVideoMemoryAllocation did not give any issues. Hibernation works fine for ‘Nvidia-only’, ‘On-demand’ and the ‘Intel’ mode. I do agree that this might point out that you run into a different kind of issue.
Anyway, on my side there is still enough other, and probably also related issues. I’ll have a look at them in the future, but at least they are less frustrating.
As a result, I’ll have to use the Nvidia mode for now.
I also tested the 495 driver, it is not useful in my case, since it does not support my card anymore.
So all currently maintained nvidia drivers either fail on my card with black screen on boot, or don’t support my card anymore, and I am locked-in to older Xorg and kernel versions.
There’s nothing to configure in terms of power management, as my first post outlined, the issue happens on my machine on boot, not after suspend or anything (even though it looks similar to the issues reported for these cases).
I have tested the following versions, which yield a black screen after a turning the backlight on and off several times directly on boot:
The following versions gave me an immediate black screen on boot:
All with the same error message (Failed to allocate display engine core DMA push buffer).
The last working version in my case is 455.45.01 which has several security issues by now and lacks support for any recent kernels and supported Xorg versions. Any update from nvidia on this bug is greatly appreciated.
Can you clarify whether this bug is the one affecting users after suspend only, or also about “black screen on cold boot” — or is this the same bug?
For those who get a black screen on boot in this thread from this regression, none of the currently supported drivers are usable anymore, and they are locked-in to nvidia drivers with security issues and lack of Xorg / kernel support.
It looks like I am also hitting this issue on desktop PC running Ubuntu 22.04 with NVIDIA driver 510.60.02 installed. Looking in the journal I see a spattering of the following messages that look related to the above:
Apr 08 08:49:23 pkkid-desktop kernel: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
Apr 08 08:49:23 pkkid-desktop kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
…
Apr 08 08:50:06 pkkid-desktop kernel: x86/cpu: SGX disabled by BIOS.
…
Apr 08 08:50:06 pkkid-desktop kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Apr 08 08:50:06 pkkid-desktop kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
…
Apr 08 08:50:09 pkkid-desktop gnome-session-binary[1858]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion ‘error == NULL || *error == NULL’ failed
Apr 08 08:50:09 pkkid-desktop gnome-session-binary[1858]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion ‘error == NULL || *error == NULL’ failed
…
Apr 08 08:50:15 pkkid-desktop gdm-password][3125]: gkr-pam: unable to locate daemon control file
…
Apr 08 08:50:16 pkkid-desktop systemd[3142]: app-gnome-gnome\x2dkeyring\x2dpkcs11-3345.scope: Failed to add PIDs to scope’s control group: No such process
Apr 08 08:50:16 pkkid-desktop systemd[3142]: app-gnome-gnome\x2dkeyring\x2dpkcs11-3345.scope: Failed with result ‘resources’.
Apr 08 08:50:16 pkkid-desktop systemd[3142]: Failed to start Application launched by gnome-session-binary.
…
Apr 08 08:50:18 pkkid-desktop gnome-session-binary[1858]: WARNING: Lost name on bus: org.gnome.SessionManager
Apr 08 08:50:18 pkkid-desktop gnome-session[1858]: gnome-session-binary[1858]: WARNING: Lost name on bus: org.gnome.SessionManager
Apr 08 08:50:18 pkkid-desktop gdm-launch-environment][1651]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Apr 08 08:50:18 pkkid-desktop gdm-launch-environment][1651]: GLib-GObject: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed
…
Apr 08 08:50:18 pkkid-desktop kernel: [drm:nv_drm_master_set [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Apr 08 08:50:31 pkkid-desktop kernel: [drm:nv_drm_master_set [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
It looks like I should be trying to set the PreserveVideoMemoryAllocations=1 in /proc/driver/nvidia/params. I imaging editing this file directly is not how that is done. Can someone explain where I put this setting? I can report back if this fixes the blank screen when resuming from suspend.
@michael.shepanski You set it on the kernel command-line. For example I have the following in /etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="nvidia.NVreg_PreserveVideoMemoryAllocations=1"
Edit: the parameter should be on nvidia, not nvidia_modeset.
Can you share any updates on this issue?
I am most interested in the problem already causing black screen on boot, i.e. making the drivers unusable.
Thanks in advance!
@amrits Thanks, sure, I tested with version 470.161.03 right now, which is the latest version of the latest legacy branch still supporting my:
NVIDIA Corporation GK104M [GeForce GTX 880M] (rev a1)
Results are the same as with the other versions, i.e. the screen turns black and dark right after boot.
Kernel logs:
Mar 30 00:15:46 localhost kernel: [ 31.624168] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
Mar 30 00:15:46 localhost kernel: [ 31.625194] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
...
Mar 30 00:15:50 localhost kernel: [ 35.946451] BUG: kernel NULL pointer dereference, address: 0000000000000070
Mar 30 00:15:50 localhost kernel: [ 35.946456] #PF: supervisor read access in kernel mode
Mar 30 00:15:50 localhost kernel: [ 35.946457] #PF: error_code(0x0000) - not-present page
Mar 30 00:15:50 localhost kernel: [ 35.946459] PGD 0 P4D 0
Mar 30 00:15:50 localhost kernel: [ 35.946461] Oops: 0000 [#1] SMP PTI
Mar 30 00:15:50 localhost kernel: [ 35.946464] CPU: 4 PID: 10421 Comm: X Tainted: P O 5.15.28-gentoo #1
Mar 30 00:15:50 localhost kernel: [ 35.946466] Hardware name: Alienware Alienware 17/04WT2G, BIOS A17 07/22/2019
Mar 30 00:15:50 localhost kernel: [ 35.946467] RIP: 0010:_nv002523kms+0x18/0x70 [nvidia_modeset]
Mar 30 00:15:50 localhost kernel: [ 35.946488] Code: 24 1f 01 eb b2 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 54 55 49 89 fc 53 89 d5 41 b8 04 00 00 00 ba 02 01 02 00 48 83 ec 10 <8b> 46 70 8b 3d 6f 79 0c 00 48 8d 4c 24 0c 89 ee 89 44
24 0c e8 cf
Mar 30 00:15:50 localhost kernel: [ 35.946490] RSP: 0018:ffff9df346ec7cf8 EFLAGS: 00010282
Mar 30 00:15:50 localhost kernel: [ 35.946492] RAX: 0000000000000000 RBX: ffff92d18e899008 RCX: ffff92d18145bec0
Mar 30 00:15:50 localhost kernel: [ 35.946493] RDX: 0000000000020102 RSI: 0000000000000000 RDI: ffff92d18e899008
Mar 30 00:15:50 localhost kernel: [ 35.946494] RBP: 0000000000010009 R08: 0000000000000004 R09: 0000000000000000
Mar 30 00:15:50 localhost kernel: [ 35.946495] R10: ffff92d1d2dab000 R11: ffff92d1d2dab000 R12: ffff92d18e899008
Mar 30 00:15:50 localhost kernel: [ 35.946496] R13: ffff92d18e8990a0 R14: 0000000000000fff R15: 0000000000010008
Mar 30 00:15:50 localhost kernel: [ 35.946498] FS: 00007f7d92a608c0(0000) GS:ffff92d8bed00000(0000) knlGS:0000000000000000
Mar 30 00:15:50 localhost kernel: [ 35.946499] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 30 00:15:50 localhost kernel: [ 35.946501] CR2: 0000000000000070 CR3: 0000000107e4e006 CR4: 00000000001706e0
Mar 30 00:15:50 localhost kernel: [ 35.946502] Call Trace:
Mar 30 00:15:50 localhost kernel: [ 35.946504] <TASK>
Mar 30 00:15:50 localhost kernel: [ 35.946505] ? _nv002522kms+0xb1/0x150 [nvidia_modeset]
Mar 30 00:15:50 localhost kernel: [ 35.946517] ? _nv002301kms+0x489/0x670 [nvidia_modeset]
Mar 30 00:15:50 localhost kernel: [ 35.946530] ? __kmalloc+0x179/0x1a0
Mar 30 00:15:50 localhost kernel: [ 35.946533] ? kmem_cache_debug_flags+0x5/0x10
Mar 30 00:15:50 localhost kernel: [ 35.946536] ? __check_heap_object+0x53/0xec
Mar 30 00:15:50 localhost kernel: [ 35.946538] ? __check_object_size+0xff/0x18e
Mar 30 00:15:50 localhost kernel: [ 35.946541] ? nv_kthread_q_stop+0x2247/0x2c77 [nvidia_modeset]
Mar 30 00:15:50 localhost kernel: [ 35.946550] ? nv_kthread_q_stop+0x227b/0x2c77 [nvidia_modeset]
Mar 30 00:15:50 localhost kernel: [ 35.946558] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset]
Mar 30 00:15:50 localhost kernel: [ 35.946567] ? nvkms_ioctl_common+0x53/0x11b [nvidia_modeset]
Mar 30 00:15:50 localhost kernel: [ 35.946575] ? nvkms_ioctl_common+0xec/0x11b [nvidia_modeset]
Mar 30 00:15:50 localhost kernel: [ 35.946584] ? nvidia_frontend_unlocked_ioctl+0x14/0x17 [nvidia]
Mar 30 00:15:50 localhost kernel: [ 35.946745] ? vfs_ioctl+0x19/0x26
Mar 30 00:15:50 localhost kernel: [ 35.946747] ? __do_sys_ioctl+0x63/0x86
Mar 30 00:15:50 localhost kernel: [ 35.946749] ? do_syscall_64+0x6d/0x80
Mar 30 00:15:50 localhost kernel: [ 35.946753] ? entry_SYSCALL_64_after_hwframe+0x44/0xae
Mar 30 00:15:50 localhost kernel: [ 35.946757] </TASK>
Mar 30 00:15:50 localhost kernel: [ 35.946758] Modules linked in: bpfilter ccm cmac algif_hash algif_skcipher af_alg bnep zram btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_co
mmon videodev mc intel_rapl_msr intel_rapl_common intel_powerclamp coretemp iwlmvm kvm_intel mac80211 kvm iwlwifi vhba(O) dell_wmi snd_hda_codec_realtek dell_smbios pcspkr snd_hda_codec_hdmi snd_hda_codec_generic dell_wmi_descriptor cfg
80211 snd_hda_intel snd_intel_dspcfg alx snd_hda_codec mdio snd_hda_core dell_rbtn dell_smo8800 nvidia_drm(PO) nvidia_modeset(PO) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel nvidia(PO) sdhci_pci iosf_mbi cqhci iTCO_wdt
sdhci rtsx_pci_sdmmc intel_pmc_bxt mmc_core
Mar 30 00:15:50 localhost kernel: [ 35.946781] CR2: 0000000000000070
Mar 30 00:15:50 localhost kernel: [ 35.946783] ---[ end trace c5a799bc5efbc771 ]---
Mar 30 00:15:51 localhost kernel: [ 35.989425] RIP: 0010:_nv002523kms+0x18/0x70 [nvidia_modeset]
Mar 30 00:15:51 localhost kernel: [ 35.989438] Code: 24 1f 01 eb b2 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 54 55 49 89 fc 53 89 d5 41 b8 04 00 00 00 ba 02 01 02 00 48 83 ec 10 <8b> 46 70 8b 3d 6f 79 0c 00 48 8d 4c 24 0c 89 ee 89 44
24 0c e8 cf
Mar 30 00:15:51 localhost kernel: [ 35.989440] RSP: 0018:ffff9df346ec7cf8 EFLAGS: 00010282
Mar 30 00:15:51 localhost kernel: [ 35.989442] RAX: 0000000000000000 RBX: ffff92d18e899008 RCX: ffff92d18145bec0
Mar 30 00:15:51 localhost kernel: [ 35.989443] RDX: 0000000000020102 RSI: 0000000000000000 RDI: ffff92d18e899008
Mar 30 00:15:51 localhost kernel: [ 35.989444] RBP: 0000000000010009 R08: 0000000000000004 R09: 0000000000000000
Mar 30 00:15:51 localhost kernel: [ 35.989445] R10: ffff92d1d2dab000 R11: ffff92d1d2dab000 R12: ffff92d18e899008
Mar 30 00:15:51 localhost kernel: [ 35.989446] R13: ffff92d18e8990a0 R14: 0000000000000fff R15: 0000000000010008
Mar 30 00:15:51 localhost kernel: [ 35.989447] FS: 00007f7d92a608c0(0000) GS:ffff92d8bed00000(0000) knlGS:0000000000000000
Mar 30 00:15:51 localhost kernel: [ 35.989448] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 30 00:15:51 localhost kernel: [ 35.989450] CR2: 0000000000000070 CR3: 0000000107e4e006 CR4: 00000000001706e0
i.e. the exact same error as before.
To reiterate, the latest version which worked fine was 455.45.01, all later versions do not work anymore but produce a black screen right on boot. Since this version is not updated for more recent kernels, I am currently bound to use 390.157.
Any news on the issue / regression are greatly appreciated. Thanks in advance!