| 2023-12-08 07:51:55 |
Ken Sharp |
bug |
|
|
added bug |
| 2023-12-08 07:51:55 |
Ken Sharp |
attachment added |
|
apt history.log https://bugs.launchpad.net/bugs/2045951/+attachment/5727424/+files/history.log |
|
| 2023-12-08 07:52:43 |
Ken Sharp |
attachment added |
|
apt history.log.1 https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045951/+attachment/5727428/+files/history.log.1.gz |
|
| 2023-12-08 08:11:31 |
Ken Sharp |
bug watch added |
|
https://github.com/electron/electron/issues/40732 |
|
| 2023-12-08 08:18:57 |
Ken Sharp |
description |
The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams...]. Indeed the same crash can occur in Chrome and Brave.
In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen].
Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 00007efc77192336 sp 00007efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e
I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway.
This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components.
The only bug reported kernel bug was closed as not enough information was supplied:
https://bugzilla.kernel.org/show_bug.cgi?id=209129
This has been reported for Ubuntu a number of times but I thought it best to start fresh:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286
From around the Interwebs:
https://bbs.archlinux.org/viewtopic.php?id=263124
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
https://github.com/ValveSoftware/steam-for-linux/issues/7370
https://github.com/ValveSoftware/steam-for-linux/issues/9793
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/
For testing I tried the following but couldn't trigger this manually:
Windows+L to lock screen, switch monitor off, switch back on and log back in.
Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in.
xset dpms force off then wake the screen up.
Any ideas how to continue would be greatly appreciated.
I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though.
I also note the --disable-gpu-* options for CEF which I'll also test.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec 8 07:09:25 2023
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 |
The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave.
In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen].
Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 00007efc77192336 sp 00007efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e
I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway.
This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components.
The only bug reported kernel bug was closed as not enough information was supplied:
https://bugzilla.kernel.org/show_bug.cgi?id=209129
This has been reported for Ubuntu a number of times but I thought it best to start fresh:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286
From around the Interwebs:
https://bbs.archlinux.org/viewtopic.php?id=263124
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
https://github.com/ValveSoftware/steam-for-linux/issues/7370
https://github.com/ValveSoftware/steam-for-linux/issues/9793
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/
For testing I tried the following but couldn't trigger this manually:
Windows+L to lock screen, switch monitor off, switch back on and log back in.
Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in.
xset dpms force off then wake the screen up.
Any ideas how to continue would be greatly appreciated.
I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though.
I also note the --disable-gpu-* options for CEF which I'll also test.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec 8 07:09:25 2023
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 |
|
| 2023-12-08 08:21:12 |
Ken Sharp |
description |
The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave.
In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen].
Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 00007efc77192336 sp 00007efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e
I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway.
This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components.
The only bug reported kernel bug was closed as not enough information was supplied:
https://bugzilla.kernel.org/show_bug.cgi?id=209129
This has been reported for Ubuntu a number of times but I thought it best to start fresh:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286
From around the Interwebs:
https://bbs.archlinux.org/viewtopic.php?id=263124
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
https://github.com/ValveSoftware/steam-for-linux/issues/7370
https://github.com/ValveSoftware/steam-for-linux/issues/9793
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/
For testing I tried the following but couldn't trigger this manually:
Windows+L to lock screen, switch monitor off, switch back on and log back in.
Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in.
xset dpms force off then wake the screen up.
Any ideas how to continue would be greatly appreciated.
I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though.
I also note the --disable-gpu-* options for CEF which I'll also test.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec 8 07:09:25 2023
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 |
The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave.
In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen].
Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 00007efc77192336 sp 00007efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e
I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway.
This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components.
The only bug reported kernel bug was closed as not enough information was supplied:
https://bugzilla.kernel.org/show_bug.cgi?id=209129
This has been reported for Ubuntu a number of times but I thought it best to start fresh:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286
From around the Interwebs:
https://bbs.archlinux.org/viewtopic.php?id=263124
https://askubuntu.com/q/1490916/170177
https://github.com/ValveSoftware/steam-for-linux/issues/7370
https://github.com/ValveSoftware/steam-for-linux/issues/9793
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
https://unix.stackexchange.com/q/658684/45386
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/
For testing I tried the following but couldn't trigger this manually:
Windows+L to lock screen, switch monitor off, switch back on and log back in.
Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in.
xset dpms force off then wake the screen up.
Any ideas how to continue would be greatly appreciated.
I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though.
I also note the --disable-gpu-* options for CEF which I'll also test.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec 8 07:09:25 2023
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 |
|
| 2023-12-08 13:44:51 |
Launchpad Janitor |
linux-signed-hwe-6.2 (Ubuntu): status |
New |
Confirmed |
|
| 2023-12-09 03:48:37 |
daas |
bug |
|
|
added subscriber daas |
| 2023-12-10 11:21:07 |
Ken Sharp |
description |
The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave.
In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen].
Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 00007efc77192336 sp 00007efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e
I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway.
This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components.
The only bug reported kernel bug was closed as not enough information was supplied:
https://bugzilla.kernel.org/show_bug.cgi?id=209129
This has been reported for Ubuntu a number of times but I thought it best to start fresh:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286
From around the Interwebs:
https://bbs.archlinux.org/viewtopic.php?id=263124
https://askubuntu.com/q/1490916/170177
https://github.com/ValveSoftware/steam-for-linux/issues/7370
https://github.com/ValveSoftware/steam-for-linux/issues/9793
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
https://unix.stackexchange.com/q/658684/45386
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/
For testing I tried the following but couldn't trigger this manually:
Windows+L to lock screen, switch monitor off, switch back on and log back in.
Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in.
xset dpms force off then wake the screen up.
Any ideas how to continue would be greatly appreciated.
I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though.
I also note the --disable-gpu-* options for CEF which I'll also test.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec 8 07:09:25 2023
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 |
The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave.
In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen].
Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 00007efc77192336 sp 00007efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e
I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway.
This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components.
The only upstream reported kernel bug was closed as not enough information was supplied:
https://bugzilla.kernel.org/show_bug.cgi?id=209129
This has been reported for Ubuntu a number of times but I thought it best to start fresh:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286
From around the Interwebs:
https://bbs.archlinux.org/viewtopic.php?id=263124
https://askubuntu.com/q/1490916/170177
https://github.com/ValveSoftware/steam-for-linux/issues/7370
https://github.com/ValveSoftware/steam-for-linux/issues/9793
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
https://unix.stackexchange.com/q/658684/45386
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/
For testing I tried the following but couldn't trigger this manually:
Windows+L to lock screen, switch monitor off, switch back on and log back in.
Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in.
xset dpms force off then wake the screen up.
Any ideas how to continue would be greatly appreciated.
I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though.
I also note the --disable-gpu-* options for CEF which I'll also test.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec 8 07:09:25 2023
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 |
|
| 2023-12-30 13:11:00 |
ku4eto |
attachment added |
|
syslog https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045951/+attachment/5734774/+files/syslog |
|
