Gnome Stability issues/GDM Disconnecting behaviour on my Asus ROG Strix

Hey guys I am have bee having some driver stability issues for a while and made a post on Manjaros forum about it asking if anyone else has been having issues here: Gnome Stability issues/GDM Disconnecting behaviour on my Asus ROG Strix - Support - Manjaro Linux Forum at the 9th January 2024

I have a ROG Strix G512 gaming laptop with a GTX 1660TI running Manjaro Gnome and currently have the 545.29.06 driver installed, ever since one of the updates my whole UI and OS will freeze up and in the logs to mentions the gpu disconnecting in xorg

Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): EDID vendor "CMN", prod id 5409
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Using hsync ranges from config file
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Using vrefresh ranges from config file
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Modeline "1920x1080"x0.0  342.06  1920 1968 2000 2080  1080 1090 1095 1142 -hsync -vsync (164.5 kHz eP)
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Modeline "1920x1080"x0.0  142.53  1920 1968 2000 2080  1080 1090 1095 1142 -hsync -vsync (68.5 kHz e)
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): EDID vendor "CMN", prod id 5409
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Using hsync ranges from config file
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Using vrefresh ranges from config file
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Modeline "1920x1080"x0.0  342.06  1920 1968 2000 2080  1080 1090 1095 1142 -hsync -vsync (164.5 kHz eP)
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Modeline "1920x1080"x0.0  142.53  1920 1968 2000 2080  1080 1090 1095 1142 -hsync -vsync (68.5 kHz e)
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-0: disconnected
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-0: 2660.0 MHz maximum pixel clock
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0):
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-1: disconnected
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0):
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-2: disconnected
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0):
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5641eb8d34e0] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5641ec3ebc00] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5641eb8d34e0] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5641ec3ebc00] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5641e7d0bcd0] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5641ea2edad0] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e0000a
Jan 08 23:46:53 corey-rogstrixg512lug512lu rtkit-daemon[1129]: Successfully made thread 160249 of process 160226 owned by '1000' high priority at nice level -15.
Jan 08 23:46:53 corey-rogstrixg512lug512lu rtkit-daemon[1129]: Supervising 7 threads of 4 processes of 1 users.
Jan 08 23:47:00 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5641e7d0bcd0] is on because it needs an allocation.
Jan 08 23:47:00 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5641ea2edad0] is on because it needs an allocation.
Jan 08 23:47:04 corey-rogstrixg512lug512lu gnome-shell[1524]: invalid (NULL) pointer instance

Please run nvidia-bug-report.sh as root and attach the resulting nvidia-bug-report.log.gz file to your post.

Sure here you go

nvidia-bug-report.log.gz (443.1 KB)

You have a hybrid graphics notebook, the internal display is driven by the intel igpu, the nvidia gpu actually doing nothing, being in offload mode.
I don’t see any i915 related errors, though.

Right and but why are the xorg errors Nvidia related? ever since I got a Nvidia update a while ago when I originally made the post on Manjaro I have been having issues and before that I was having no stability issues

Those are not error messages but only informational, showing the nvidia gpu has no monitors connected. Errors are identified by (EE) and not by (–) or (II).

Ah I see, so do you know what exactly is causing the problem?

No, there don’t seem to be any crashes related to Xserver or i915/nvidia drivers. Only gnome-shell seems to be crashing.
Under which circumstances does that happen?

Right I see, Interesting. It only seems to happening when it sits there on idle for a while, it doesn’t specifically have anything running for it to happen.

So maybe triggered by suspend/resume? Please check.

Nah it isn’t from suspending, after I did yet another reboot I left it there on the desktop and it did it, I also notice before it it fully freezes up applications will stop opening/responding and icons on the gnome application screen will disappear

I guess then you should check coredumpctl to see whether something is crashing.

Here is my log but I assume most of these are going to just show because of the issue I am having

 1000 SIGABRT missing  /usr/bin/gnome-control-center                           >
 1000 SIGSEGV missing  /usr/bin/file-roller                                    >
 1000 SIGSYS  missing  /home/corey/Stuff/Electron/browser/node_modules/electron>
 1000 SIGSEGV missing  /usr/bin/gnome-text-editor                              >
 1000 SIGSEGV missing  /usr/bin/file-roller                                    >
 1000 SIGABRT missing  /app/jdk/17/bin/java                                    >
 1000 SIGSEGV missing  /usr/bin/openbor                                        >
 1000 SIGSEGV missing  /home/corey/OpenBOR/OpenBOR                             >
 1000 SIGSEGV missing  /home/corey/OpenBOR/OpenBOR                             >
 1000 SIGSEGV present  /opt/teamviewer/tv_bin/TeamViewer                       >
 1000 SIGTRAP present  /opt/libelectron/node_modules/electron/dist/electron    >
 1000 SIGSEGV present  /opt/teamviewer/tv_bin/TeamViewer 

What exactly is happening on freeze/crash?

My Gnome desktop will freeze and I have to reboot my laptop

Can you ssh into the system while frozen?

I will have to test that but if I can what would you like me to do?

If ssh works, please create a new nvidia-bug-report.log, maybe this will yield some info. If ssh doesn’t work, this would point to some more serious hw issue.

Alright no problem, I will get back to you if I can or not and if I can I will upload a new Nvidia log

Nope sadly as soon as it starts to happen things start failing and after a while SSH breaks and won’t even log in properly

Man this is a really annoying bug that is completely breaking the reliability of my OS especially when I need to work on projects…

I got two videos of it before it freezes and what it does and when it completely freezes