I was reading some news articles, running waterfox, when my machine (thinkpad X220) spontaneously rebooted itself. After the reboot, I can see the following was the last thing to happen in /var/log/messages
Nov 5 20:06:38 box kernel: drmn0: [drm] GPU HANG: ecode 6:1:85fffffc, in Renderer [200136]
Nov 5 20:06:38 box kernel: drmn0: [drm] Resetting chip for stopped heartbeat on rcs0
Nov 5 20:06:38 box kernel: drmn0: [drm] Renderer[200136] context reset due to GPU hang
Nov 5 20:45:50 box syslogd: kernel boot file is /boot/kernel/kernel
Nov 5 20:45:50 box kernel: ---<<BOOT>>---
Nov 5 20:45:50 box kernel: Copyright (c) 1992-2023 The FreeBSD Project.
There's a big gap in timestamps between the gpu hang at 20:06 and the reboot at 20:45. Maybe the event that caused the reboot doesn't have any log entries, but I wondered if there is a connection. I can't find any coredumps on the box.
$ freebsd-version -ukr
14.5-RELEASE-p2
14.5-RELEASE-p2
14.5-RELEASE-p3
It's pretty strange, I don't think I've ever seen freebsd do that before on this hardware.
Has anyone else seen this? Is it a known bug? Any ideas?
Nov 5 20:06:38 box kernel: drmn0: [drm] GPU HANG: ecode 6:1:85fffffc, in Renderer [200136]
Nov 5 20:06:38 box kernel: drmn0: [drm] Resetting chip for stopped heartbeat on rcs0
Nov 5 20:06:38 box kernel: drmn0: [drm] Renderer[200136] context reset due to GPU hang
Nov 5 20:45:50 box syslogd: kernel boot file is /boot/kernel/kernel
Nov 5 20:45:50 box kernel: ---<<BOOT>>---
Nov 5 20:45:50 box kernel: Copyright (c) 1992-2023 The FreeBSD Project.
There's a big gap in timestamps between the gpu hang at 20:06 and the reboot at 20:45. Maybe the event that caused the reboot doesn't have any log entries, but I wondered if there is a connection. I can't find any coredumps on the box.
$ freebsd-version -ukr
14.5-RELEASE-p2
14.5-RELEASE-p2
14.5-RELEASE-p3
It's pretty strange, I don't think I've ever seen freebsd do that before on this hardware.
Has anyone else seen this? Is it a known bug? Any ideas?