Description of problem: Every now and then laptop-screen freezes. In message-log on time of freeze following message appears among others: Dec 2 18:48:05 GE77 kernel: [41432.286993] BUG: scheduling while atomic: kwin_x11/2428/0x00000102 It's dual-boot-machine with Win11 as other OS and NVIDIA . After hard reset by power-button, sound on both OS'es is gone. Only way to get sound back is applying latest BIOS-update, but this doesn't prevent for next freeze, as i have learned through experience. Version-Release number of selected component (if applicable): Attached output of message-log and output of inxi -F for what it's worth.
Created attachment 14190 [details] messages at moment of freeze
Created attachment 14191 [details] output inxi -F
Attachment 14190 description: message at moment of freeze => messages at moment of freeze
Try switching to xorg instead of wayland.
CC: (none) => davidwhodgins
Output for: echo $XDG_SESSION_TYPE Gives alreaady: X11 So there is no wayland in use.
Although.......i have a mass load of wayland packages installed. I had the NVIDIA-card configured through mageia-prime-install.
Sorry, I had just noticed the Xwayland in the inxi output, and didn't look closely enough. If it's currently running xorg, try switching to wayland.
I remember that some times for hybrid graphics after kernel and drivers updates is useful run uninstall and install commands https://wiki.mageia.org/en/Mageia-prime_for_Optimus#Switching_between_cards
(In reply to Dave Hodgins from comment #6) > Sorry, I had just noticed the Xwayland in the inxi output, and didn't look > closely enough. > > If it's currently running xorg, try switching to wayland. Any suggestion how to realize such switch?
(In reply to katnatek from comment #7) > I remember that some times for hybrid graphics after kernel and drivers > updates is useful run uninstall and install commands > > https://wiki.mageia.org/en/Mageia-prime_for_Optimus#Switching_between_cards You actually propose to run first: mageia-prime-uninstall -z After that: mageia-prime-install -z Correct?
To try wayland, it should be an option in the menu (sddm, gdm, etc). I have the following wayland packages installed, though I usually use xorg kwayland-5.105.0-2.mga9 kwayland-integration-5.27.5-1.mga9 kwin-wayland-5.27.5-1.mga9 lib64gstwayland1.0_0-1.22.5-1.mga9.tainted lib64kf5wayland5-5.105.0-2.mga9 lib64qt5waylandclient5-5.15.7-2.mga9 lib64qt5waylandcompositor5-5.15.7-2.mga9 lib64qt6waylandclient6-6.4.1-3.mga9 lib64wayland-client0-1.21.0-1.mga9 lib64wayland-cursor0-1.21.0-1.mga9 lib64wayland-egl1-1.21.0-1.mga9 lib64waylandpp1-1.0.0-1.mga9 lib64wayland-server0-1.21.0-1.mga9 libwayland-client0-1.21.0-1.mga9 libwayland-server0-1.21.0-1.mga9 plasma-workspace-wayland-5.27.5-2.1.mga9 qtwayland5-5.15.7-2.mga9 wayland-tools-1.21.0-1.mga9 x11-server-xwayland-22.1.9-1.1.mga9 Another way to start it is to boot to run level 3 (add " 3" to the kernel options), login in text mode and run XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland For gnome, it's XDG_SESSION_TYPE=wayland dbus-run-session gnome-session
(In reply to isadora from comment #9) > (In reply to katnatek from comment #7) > > I remember that some times for hybrid graphics after kernel and drivers > > updates is useful run uninstall and install commands > > > > https://wiki.mageia.org/en/Mageia-prime_for_Optimus#Switching_between_cards > > You actually propose to run first: > mageia-prime-uninstall -z > > After that: > mageia-prime-install -z > > Correct? Yes
CC: (none) => j.alberto.vc
(In reply to Dave Hodgins from comment #10) > To try wayland, it should be an option in the menu (sddm, gdm, etc). > The menu, i looked around in MCC, but i think i don't go to find it without some more information what menu exactly you are pointing at. Regarding wayland-packages, i found these installed: lib64wayland-client0-1.21.0-1.mga9 lib64wayland-server0-1.21.0-1.mga9 lib64wayland-cursor0-1.21.0-1.mga9 lib64qt5waylandclient5-5.15.7-2.mga9 lib64wayland-egl1-1.21.0-1.mga9 lib64qt6waylandclient6-6.4.1-3.mga9 lib64kf5wayland5-5.105.0-2.mga9 kwayland-5.105.0-2.mga9 egl-wayland-json-1.1.11-1.mga9 lib64nvidia-egl-wayland1-1.1.11-1.mga9 lib64gstwayland1.0_0-1.22.3-2.mga9.tainted x11-server-xwayland-22.1.9-1.1.mga9 That's a handful less than you described, but probably some more will be installed along the process of switching to wayland (?).
(In reply to katnatek from comment #11) > Yes Did as you proposed. Will wait and see, before switching to wayland as Dave suggested.
(In reply to isadora from comment #13) > (In reply to katnatek from comment #11) > > > Yes > Did as you proposed. > Will wait and see, before switching to wayland as Dave suggested. To use wayland close current session and in the login screen exist a text that indicates the type of session, by example "Plasma (X11)" click and select "Plasma(wayland)" if you use Plasma, you can return to use normal Plasma session by the same procedure just changing again to the X11 session
(In reply to katnatek from comment #14) > (In reply to isadora from comment #13) > > (In reply to katnatek from comment #11) > > > > > Yes > > Did as you proposed. > > Will wait and see, before switching to wayland as Dave suggested. > First install plasma-workspace-wayland > To use wayland close current session and in the login screen exist a text > that indicates the type of session, by example "Plasma (X11)" click and > select "Plasma(wayland)" if you use Plasma, you can return to use normal > Plasma session by the same procedure just changing again to the X11 session
Right, i thought i would miss some wayland-packages as mentioned in comment 12. And so without plasma-workspace-wayland one would not see an option for wayland in the login-screen (obviously). But as said before, i wait now for a new freeze to happen before switching to wayland.
Last night the system froze again, and after reboot (forced through power-button), sound (as usual) was gone. Message-log comes with same messages "scheduling while atomic" etc. The laptop was put in locked position this time. I was out for a couple of hours, and hoped to login again into the desktop, but i already knew something was wrong, because the clock in the lock-screen did not run and hence also no way of logging in. So, now i will go the wayland-route, and keep you updated about experiences.
Installed plasma-workspace-wayland, which brought in some more wayland-packages. Following wayland-packages are installed now: lib64wayland-client0-1.21.0-1.mga9 lib64wayland-server0-1.21.0-1.mga9 lib64wayland-cursor0-1.21.0-1.mga9 lib64qt5waylandclient5-5.15.7-2.mga9 lib64wayland-egl1-1.21.0-1.mga9 lib64qt6waylandclient6-6.4.1-3.mga9 lib64kf5wayland5-5.105.0-2.mga9 kwayland-5.105.0-2.mga9 egl-wayland-json-1.1.11-1.mga9 lib64nvidia-egl-wayland1-1.1.11-1.mga9 lib64gstwayland1.0_0-1.22.3-2.mga9.tainted x11-server-xwayland-22.1.9-1.1.mga9 kwayland-integration-5.27.5-1.mga9 lib64qt5waylandcompositor5-5.15.7-2.mga9 qtwayland5-5.15.7-2.mga9 kwin-wayland-5.27.5-1.mga9 plasma-workspace-wayland-5.27.5-2.1.mga9 There is a Plasma (wayland)-option now in the session-screen, as mentioned in comment 14. Choosing this option presents a desktop, although everything is a bit smaller, like icons and panel. Also, single-click disappeared, but that is easy to change. But, when i reboot (automatic login), i return into Plasma (X11) environment again. So problem now is, that i have to log out again, choose right choice in session-screen, to return in Plasma (wayland). It would be nice if my choice was saved, and after reboot to come back with Plasma (wayland)-session.
Also, in MCC->Boot->Setup auto-login->Default desktop does not show wayland. Plasma X-11 and Icewm are only choices.
Alright, did some more digging and now i auto-login into wayland. The final solution seemed to change Login Screen (SSDM)->Behavior in System Settings. Changed session there for auto-login-session, asked for root-password, rebooted and there it was. Now fiddle around with settings, and hope for no more freezes. Will be continued, i keep you informed.
I found information that the issue happens in some hardwares with kwin+x11+nvidia, congratulations isadora you got the winner ticket ;) Maybe switch to Wayland is the best recommendation
Well, that is, i still have nvidia not "alive"; OpenGL Renderer: Mesa Intel(R) UHD Graphics (ADL-S GT1)
(In reply to isadora from comment #22) > Well, that is, i still have nvidia not "alive"; > OpenGL Renderer: Mesa Intel(R) UHD Graphics (ADL-S GT1) Wayland works different from X11, maybe I'm wrong but to use the discrete nvdia card you must do in X11 session You can try installing kernel-linus and kernel-linus-devel and in the boot menu in advance options choose the kernel without flavor (desktop, server, etc), but I'm not optimist that this don't get the same fail in X11 session
I find this https://community.kde.org/Plasma/Wayland/Nvidia We have x11-server-xorg 21.1.8 x11-server-xwayland 22.1.9 lib(64)xcb1 1.15 lib(64)nvidia-egl-wayland1 Plasma 5.27.5 In theory can work
Yes, i ran into the same KDE-community-page. And for my further explorations into wayland/nvidia; last night i came to the point, no graphical desktop appeared anymore. Slept a good night, and decided this morning to do new install of Mageia 9. I give it a rest for some time, until then, thank you very much for your support.
Another interesting read is: https://www.tuxedocomputers.com/en/Whats-the-deal-with-X11-and-Wayland-_1.tuxedo Albeit not really promising for Nvidia.
Not meaning to spam, but any information to me seems better than none. https://9to5linux.com/nvidia-545-29-02-linux-graphics-driver-is-out-with-wayland-improvements-more
Situation with regular freezes continued ever since initial report. Still have to use the workaround with "BIOS-flash-update", to get workable situation. Sometimes no issue like for a month, but last week three freezes.
Did the recent nvidia and other updates change something?
Ever since my last report i stopped using NVIDIA for the graphical job. Since then i had no crashes. I will switch back to NVIDIA now and report about experiences.
Two weeks later, still no crashes so far.
This looks good to close.
Status: NEW => RESOLVEDResolution: (none) => FIXED