F35 random freezes in gnome wayland

Hello how are you?.

I have a problem that has been present for more than 6 years and it also affects the sections in Xorg, although in a different way (striped screen in Xorg).

I would like to help as much as possible to investigate these screen/system freezes to see if there is a way to recover the system without resorting to a forced shutdown.

I’ve always liked using my old pc as a fedora test mini lab, I’d really love to help improve that, maybe there’s more collateral benefit to this.

About the problem:

  • Possible causes: The gonome wayland section suddenly freezes in cases where I use the system panels, many programs open at the same time, playing videos, opening and closing games in full screen, among other things.

During freezing:

  • The graphics: The graphics are frozen (as if it were a screenshot), the mouse cursor stops moving.
  • The audio: The audio reproduction does not seem to be affected by this, the music continues to play, the video also and even, and if a music ends, it advances to the next track.
  • The keyboard: The shortcuts no longer work, it is also not possible to change/open any section of the TTY terminal, but the keyboard lights still respond to “block mayus” or “block number”.
  • Processor: the light keeps blinking, it also blinks when pressing some keys like “block mayus” and “block number”.
  • Screen off or screen lock: When the minutes pass and the section activates the screen saver or turns off the screen, the displayed image is only black (what looked like a screenshot is now all black).

My gpu is old:

00:0d.0 VGA compatible controller [0300]: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller])
	Subsystem: ASRock Incorporation Device [1849:03d6]
	Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22, NUMA node 0
	Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Memory at f9000000 (64-bit, non-prefetchable) [size=16M]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: nouveau
	Kernel modules: nouveau

00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration [1022:1200]
	Flags: fast devsel, NUMA node 0
1 Like

I don’t have any specific comments, but I guess we start by looking at your system logs. Can you please find the logs for the boot where this happened and see what they say, hopefully something related to the screen freeze:

https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/

1 Like

Well I’ve filtered yesterday’s logs and compressed them into a file.

My main suspicion is those who say:

ene 17 12:35:15 fedora kernel: nouveau 0000:00:0d.0: gr: intr 00100000 [ERROR] nsource 00000002 [DATA_ERROR] nstatus 02000000 [BAD_ARGUMENT] ch 7 [00072000 vlc[18827]] subc 7 class 4497 mthd 0208 data 00000120

Apparently vlc media player was working at the moment.

File log:
https://github.com/Yona-TYT/imgs/raw/main/test-yesterday.zip

1 Like

Yeh, that does look suspicious. Could be a nouveau bug? Are you using the proprietary driver? That could help:

https://rpmfusion.org/Howto/NVIDIA

Unfortunately, the proprietary drivers are obsolete for my PC, but I can confirm that I have been using them for years and the problem has practically disappeared.

1 Like

I am not the only one, for many years many have suffered with this problem I am afraid. :frowning:

related reports:

https://nouveau.freedesktop.narkive.com/NoeonDJf/system-freeze-debian-testing-with-c61-geforce-7025-nforce-630a

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784305

https://forums.linuxmint.com/viewtopic.php?p=1831489&sid=011bc8ee779ae760616a4d21e530f33a#p1831489

1 Like

Hi, I’m not sure if this can help.

Since it’s test lab, maybe you could try with Fedora Xfce spin. If you want also to experience with minimal wayland, you can use sway window manager.

Maybe you also want to use LTS version of kernel maintained by @kwizart

At least is there a way to recover the system without resorting to forced shutdown?

I still have some hope, so I started a bugzilla report.
https://bugzilla.redhat.com/show_bug.cgi?id=2042295