[Google_Puff] Screen blank crashes system

[Tom Anschutz]

Ubuntu 23.04 screen blank crashes system. Not a sleep problem, I can enter and resume from S2idle, S2ram. (Using command line or Power/Suspend GUI) However, when screen blanks, computer has a hard crash. Just rebooting with power button may not work (operating system not found error) I have to unplug the computer and plug it back in again to reboot properly. I would just turn off screen sleep, but when the S2ram suspend mode engages it often, but not always, crashes as well.

I've tried live disks with other OS, and this is not a problem on Linux Mint 21.2, nor on Xubuntu 23.04. Windows 10 works too. I tried Ubuntu 22.04 and it also crashed - using either gnome or wayland.

I'm happy to help debug, but I'm not a developer.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15
Uname: Linux 6.2.0-27-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 21 15:11:21 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41]
InstallationDate: Installed on 2023-06-13 (69 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: Google Noibat
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=77b0ab13-596d-4e94-8648-e6aeda300b7a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 4.20
dmi.bios.vendor: coreboot
dmi.bios.version: MrChromebox-4.20.0
dmi.board.name: Noibat
dmi.board.vendor: HP
dmi.board.version: rev4
dmi.chassis.type: 3
dmi.chassis.vendor: Google
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.20.0:bd05/15/2023:br4.20:efr0.0:svnGoogle:pnNoibat:pvrrev4:rvnHP:rnNoibat:rvrrev4:cvnGoogle:ct3:cvr:skusku83886080:
dmi.product.family: Google_Puff
dmi.product.name: Noibat
dmi.product.sku: sku83886080
dmi.product.version: rev4
dmi.sys.vendor: Google
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Tom Anschutz (tom-anschutz)]

Thank you also for helping. I did not find any files in /var/crash. I did find 3 links at the whoopsie error tracker. However, they do not seem to correlate to my system crashes. I will provide them anyway.

I have tried some additional things. I can confirm that the system also crashes running the 23.04 installer. I can also say that there are a few seconds after the screen turns off that I can return to a working state. However sometime after 10-15 seconds and always before a minute has passed - that's when the system locks up.

Oddly, I have also determined that the new installer for 22.04.3 does not have this problem.

I've also started learning about the linux-crashdump package. I'm still pulling my hair on that one. Even using the manual crash (sysctl -w kernel.sysrq=1 ...) I'm not getting a .crash file or even a reboot. (I'm definitely getting a crash :) I may have to put in a larger value for memory. I'll work on that.

Here are the whoopsies:
https://errors.ubuntu.com/oops/1eb5bb9c-36cf-11ee-bf3b-fa163ef35206
https://errors.ubuntu.com/oops/955ee737-1a89-11ee-a380-fa163e993415
https://errors.ubuntu.com/oops/b7c373c0-192e-11ee-bdd6-fa163ef35206

[Daniel van Vugt (vanvugt)]

Indeed those whoopsies are unrelated to this bug.

Next time it happens, after rebooting please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

[Tom Anschutz (tom-anschutz)]

Hi, I've crashed the system and then collected the prevboot per your instructions.

I have other news too. I saw a .crash file in /var/crash this morning. It has file name _usr_sbin_Cups-browsed.121.crash. There are also same name - .upload and .uploaded files owned by whoopsie. I'll provide the link for that whoopsie. When I typed [sudo ubuntu-bug _usr_sbin_cups-browsed.121.crash] it provided a gui pop-up to report the error, but did not provide any ID.

And I have determined that the system does not crash if it's playing sound. I've tried that several ways: using the analog or HDMI output, and from various sources - even a KVM virtual machine. When the screen goes to sleep, the HDMI sound stops playing on that monitor, but the system does not crash.

The system updated to 6.2.0-31 kernel this morning, but that did not change anything.

https://errors.ubuntu.com/oops/e7724766-45ab-11ee-b35c-fa163e55efd0

Thanks!

[Daniel van Vugt (vanvugt)]

The only error I can see there is Xwayland's fault:

Aug 28 10:14:25 HPCB3 gnome-shell[3517]: Connection to xwayland lost
Aug 28 10:14:25 HPCB3 gnome-shell[3517]: Xwayland terminated, exiting since it was mandatory
Aug 28 10:14:25 HPCB3 org.gnome.Shell.desktop[3517]: GNOME Shell terminated with an error: Xwayland exited unexpectedly
Aug 28 10:14:25 HPCB3 gnome-shell[3517]: (../src/core/meta-context.c:501):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop))
Aug 28 10:14:25 HPCB3 gnome-shell[3517]: Shutting down GNOME Shell

So we are looking for "oops" reports from xwayland. You can safely ignore all the cups-browsed crashes because those are not relevant.

[Tom Anschutz (tom-anschutz)]

Updated to 6.2.0-32 kernel. No change. No oops. I have noticed that the fan will still change speeds (typically slows down) even after the system has crashed. I'm not sure that the crashdump kernel is working, or perhaps that I know how to use it. Based on your comment, I would suspect that the video has crashed, and I do see that same Xwayland terminated set of messages on other crashes when I do another journalctl -b-1. Is it normal for Wayland to exit when the screen shuts down? Yet I cannot ssh into the system once it's crashed? Any ideas what I can do next? Thanks

[Daniel van Vugt (vanvugt)]

> Is it normal for Wayland to exit when the screen shuts down?

The opposite -- the screen shuts down because Xwayland exits/crashes. Although even that may not matter because I now think that only your login screen was using Wayland/Xwayland. So it's not relevant to any problem experienced after you logged in (which seems to be using Xorg instead of Wayland).

> Yet I cannot ssh into the system once it's crashed?

If you could ssh in before the crash then it sounds like a kernel bug has also occurred, but that's not shown in the log of comment #5 that I can see(?). If you couldn't ssh in before the crash then you need to:

  sudo apt install openssh-server

Next time the bug occurs please reboot and run this command again:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

[Daniel van Vugt (vanvugt)]

This kernel error from your log might be relevant:

Aug 28 10:48:19 HPCB3 kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=123155 end=123156) time 151 us, min 2146, max 2159, scanline start 2145, end 2164

To avoid that please:

1. Add this to /etc/environment: MUTTER_DEBUG_FORCE_KMS_MODE=simple

2. Reboot.

3. Log into a Wayland session (which might just be called "Ubuntu" on the login screen).

[Tom Anschutz (tom-anschutz)]

Hi,

I added the environment variable and then tested it after rebooting with set | grep simple. It was set correctly. I also logged in using wayland. I don't know how it got set to xorg.
The system still crashes with a wayland session, and I've attached the prevboot.txt file here.

I've also determined the following:
If I am running a VM the system does not crash - even if there are no connections to the VM.
Now it gets interesting:
If I'm logged in with ssh and running top - the system does not crash! However if I exit top and then let the ssh session be idle for a minute the system crashes. So similarly to my comment before about audio, it seems if the system is doing anything it keeps running, but if it goes truly idle, then it crashes.

I hope this is all helpful. Thank you for your patience!

[Daniel van Vugt (vanvugt)]

There is no evidence of anything crashing in that log. Please follow the steps in comment #2 each time you experience a problem.

[Tom Anschutz (tom-anschutz)]

Crash today. Nothing in /var/crash and prevboot.txt attached

It seems that the crash does not get logged. Is there anything else I could do to test or work through what is crashing the system?

Thanks!

[Daniel van Vugt (vanvugt)]

I don't see any evidence of a crash there, so it sounds like this is more like a full system freeze.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Tom Anschutz (tom-anschutz)]

Hello again. Something strange happened today. The computer booted, and bingwall ran successfully. (normally it hangs from some new interaction with apparmor (I think). Also on this boot, the screen blank went directly from on to off. (Normally it slowly dims the screen before turning it off). In this state the computer did not lock up. I tried letting the screen blank several times and waited a longer time, and it was not locking up. The system was otherwise completely idle.

So, I rebooted, and things went back to normal. Bingwall hung (and I killed that process to see if it was bingwall causing the crash) The screen dimmed before going to sleep, and the system crashed. However, before the crash I captured a prevboot-good file to attach along with a prevboot that crashed afterwards.

[Tom Anschutz (tom-anschutz)]

Seems I can only attach one file per comment. Attached is the prevboot that crashed from my previous comment.

[Tom Anschutz (tom-anschutz)]

I went back to confirm the problem on other systems. Despite what I wrote before, Ubuntu 22.04.3 does crash when sleeping. My first post stands as correct. Also, I tried Debian 12 with gnome and wayland. That system does not crash - and it has a very similar look and feel to Ubuntu.

[Tom Anschutz (tom-anschutz)]

I upgraded my system to ubuntu 23.10 (not a fresh install) and after the upgrade I still have this issue. However, it seems to take somewhat longer than a minute to crash.