[Bug 1198545] New: Failed to grab modeset ownership - nvidia
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 Bug ID: 1198545 Summary: Failed to grab modeset ownership - nvidia Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs@suse.de Reporter: sndanailov@gmail.com QA Contact: sndirsch@suse.com Found By: --- Blocker: --- Nvidia Driver Version: 470.103.01 Linux 5.17.2-1-default Apr 17 09:24:57 PC kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to grab modeset ownership Apr 17 09:24:57 PC kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to grab modeset ownership Apr 17 09:24:57 PC kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to grab modeset ownership This started to happen more often lately and it's getting pretty annoying. My solution always is to just reboot the system until it doesn't fail. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c2 --- Comment #2 from Sotir Danailov <sndanailov@gmail.com> --- It's not just a warning, because my PC doesn't show the login prompt, just a black screen with a blinking cursor. Like I said, I have to reboot multiple times until it actually grabs the modeset ownership eventually. The issue link from Github you sent me is related to Firefox and it's after logging in. I'm talking about even before that, it happens when I start the machine, no login prompt shows. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c3 --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Two things you can try. 1) Use 510.60.02/G06 driver, but if your GPU is too old you can't. I can tell you if you can provide the output of 'inxi -aG' 2) Remove or comment out line options nvidia-drm modeset=1 from /etc/modprobe.d/50-nvidia-default.conf and run 'mkinitrd' to make it permanend in initrd. Reboot the machine. But without this kernel driver option you cannot run Wayland as far as I know. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c4 --- Comment #4 from Sotir Danailov <sndanailov@gmail.com> --- Well my GPU is NVIDIA GeForce GTX 760, I think it's too old for G06. I've set "nomodeset" as a parameter in the GRUB config, doesn't this have the same effect? I think without this parameter it would never boot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c5 --- Comment #5 from Stefan Dirsch <sndirsch@suse.com> --- Indeed GeForce GTX 760 is too old for G06. Could be that nomodeset does the same as using the default value 0 for modeset option of nvidia_drm module. So with 'nomodeset' the errors no longer occur and nvidia kernel modules are still loaded? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c6 --- Comment #6 from Sotir Danailov <sndanailov@gmail.com> --- No, I had to set "nomodeset" when I first installed Tumbleweed, because otherwise it wouldn't boot at all. I didn't have any problems for a while, but after a couple of updates, the system started to have the same problems even with "nomodeset", but at least after I reboot a couple of times it eventually boots properly. Today it booted normally on the first try, but that's rare and the thing is, I have to idea how to reproduce it, it seems random almost. Maybe there's nothing to do, because Nvidia themselves have to look at this. Is there a way to fill a bug report directly to them for the Linux driver? I wasn't sure if this is the right place to report this, because it's not an open source kernel module and it isn't directly part of OpenSUSE, but I had to try at least and I wanted to see if anyone else had the same problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c7 --- Comment #7 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Sotir Danailov from comment #6)
No, I had to set "nomodeset" when I first installed Tumbleweed, because otherwise it wouldn't boot at all.
That was probably still with nouveau driver in place.
I didn't have any problems for a while,
after installing nvidia driver I assume
but after a couple of updates, the system started to have the same problems
Hmm. Can't be the same problems with nouveau and nvidia driver ...
even with "nomodeset",
but then using "nomodeset" looks different than using nvidia_drm module without modesetting
but at least after I reboot a couple of times it eventually boots properly. Today it booted normally on the first try, but that's rare and the thing is, I have to idea how to reproduce it, it seems random almost.
Hmm. IMO it still would be worth a try using nvdiia_drm module without modesetting as I outlined in comment #3.
Maybe there's nothing to do, because Nvidia themselves have to look at this. Is there a way to fill a bug report directly to them for the Linux driver? I wasn't sure if this is the right place to report this, because it's not an open source kernel module and it isn't directly part of OpenSUSE, but I had to try at least and I wanted to see if anyone else had the same problem.
There is no public issue tracker at nVidia unfortunately. Only a forum, but I will add my contact at nVidia here. Could be he is interested into this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddadap@nvidia.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c8 --- Comment #8 from Sotir Danailov <sndanailov@gmail.com> ---
from /etc/modprobe.d/50-nvidia-default.conf
This file doesn't exist, I'm going to create it and put this line in it: options nvidia-drm modeset=0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c9 --- Comment #9 from Stefan Dirsch <sndirsch@suse.com> --- Oh. This is Tumbleweed. Plesae check /usr/lib/modprobe.d/50-nvidia-default.conf instead. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c10 --- Comment #10 from Sotir Danailov <sndanailov@gmail.com> ---
Plesae check /usr/lib/modprobe.d/50-nvidia-default.conf
This file exists, I commented the line like so: # options nvidia-drm modeset=1 I ran: sudo mkinitrd Rebooted the system and all seems to be fine, but keep in mind in the meantime my kernel got updated to 5.17.3-1-default and I don't know if that had any effect, but had to mention just in case. Is it a problem to comment the nvidia-drm modeset and have "nomodeset" as a parameter at the same time? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c11 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sndanailov@gmail. | |com) | --- Comment #11 from Stefan Dirsch <sndirsch@suse.com> --- Thanks. This that change "nomodeset" is no longer needed. I would remove it. In theory the kernel update may have fixed a regression which had been introduced in previous kernel versions. Well, you can try without the modeset module option with that new kernel if you like. And as I said without modeset you can't use Wayland. Only X. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c12 --- Comment #12 from Sotir Danailov <sndanailov@gmail.com> --- I removed "nomodeset" and I uncommented the nvidia-drm option and ran mkinitrd, after the reboot, the login prompt showed up, but when I tried to login, everything froze and this are the log messages: Apr 22 14:48:43 PC kernel: caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs ... Apr 22 14:48:46 PC kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to grab modeset ownership Apr 22 14:48:46 PC kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to grab modeset ownership Apr 22 14:48:46 PC kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to grab modeset ownership ... Apr 22 14:49:04 PC kernel: lightdm[1499]: segfault at 0 ip 00007fd2e6f5881a sp 00007ffc9f3b55d8 error 4 in libc.so.6[7fd2e6ecf000+182000] ... Apr 22 14:49:24 PC systemd[1]: Forcibly rebooting: Ctrl-Alt-Del was pressed more than 7 times within 2s Apr 22 14:49:24 PC systemd[1]: Shutting down. Apr 22 14:49:24 PC systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0 Apr 22 14:49:24 PC systemd[1]: Watchdog running with a timeout of 10min. Apr 22 14:49:24 PC kernel: watchdog: watchdog0: watchdog did not stop! I stopped the machine by holding the power button. After this I started Tumbleweed in "Recovery mode", when the login prompt showed up I pressed ctrl+atl+F2, I logged in successfully and again commented the nvidia-drm option, ran mkinitrd, rebooted again and this time there was no issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c13 --- Comment #13 from Sotir Danailov <sndanailov@gmail.com> --- I did 2 more reboots and one complete shutdown and start from the power button after this just in case and it all seems to be fine. So I guess I have to leave the option commented out. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c14 --- Comment #14 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Thanks for testing. So you need modeset option of nvidia_drm module disabled, but "nomodeset" isn't needed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Failed to grab modeset |Failed to grab modeset |ownership - nvidia |ownership - | |nvidia_drm.modeset must not | |be enabled (G05/470.103.01 | |on GeForce GTX 760) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198545 http://bugzilla.opensuse.org/show_bug.cgi?id=1198545#c15 Nick Singer <nsinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nsinger@suse.com --- Comment #15 from Nick Singer <nsinger@suse.com> --- I face the same issue on a GTX1060 with G06 and the most recent kernel installed. The symptoms are the same as described by Sotir Danailov. What usually helps for me is restarting sddm - afterwards the login screen appears. Here is what the journal shows: Jul 05 19:52:34 heimdall kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership Jul 05 19:52:34 heimdall kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership Jul 05 19:52:34 heimdall kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership Jul 05 19:52:35 heimdall sddm[1010]: Setting default cursor Jul 05 19:52:35 heimdall kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership Jul 05 19:52:35 heimdall kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership Jul 05 19:52:35 heimdall kernel: [drm:drm_new_set_master [drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership Jul 05 19:52:35 heimdall sddm[1010]: Running display setup script "/usr/etc/X11/xdm/Xsetup" Jul 05 19:52:35 heimdall sddm[1010]: Display server started. Jul 05 19:52:35 heimdall sddm[1010]: Socket server starting... Jul 05 19:52:35 heimdall sddm[1010]: Socket server started. Jul 05 19:52:35 heimdall sddm[1010]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf" Jul 05 19:52:35 heimdall sddm[1010]: Greeter starting... Jul 05 19:52:35 heimdall sddm-helper[1192]: [PAM] Starting... Jul 05 19:52:35 heimdall sddm-helper[1192]: [PAM] Authenticating... Jul 05 19:52:35 heimdall sddm-helper[1192]: [PAM] returning. Jul 05 19:52:35 heimdall systemd[1]: Created slice User Slice of UID 465. Jul 05 19:52:35 heimdall systemd[1]: Starting User Runtime Directory /run/user/465... Jul 05 19:52:35 heimdall systemd-logind[692]: New session 2 of user sddm. I will try the workaround with "options nvidia-drm modeset=0" and report back but please assume the regression isn't fixed by more recent versions of driver/kernel. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com