Bug#1081546: new "GPU HANG: ecode 12:1:85dffdfb, in Renderer" regression in i915 driver since 6.10 kernel upgrade
- To: Antoine Beaupré <anarcat@debian.org>
- Cc: 1081546@bugs.debian.org
- Subject: Bug#1081546: new "GPU HANG: ecode 12:1:85dffdfb, in Renderer" regression in i915 driver since 6.10 kernel upgrade
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Thu, 24 Apr 2025 14:58:09 +0200
- Message-id: <[🔎] aAo1YV5Jix7F5-yS@eldamar.lan>
- Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 1081546@bugs.debian.org
- In-reply-to: <Z96-F5mInjIDemtr@eldamar.lan>
- References: <172615722963.13536.260751860512984317.reportbug@angela.anarc.at> <handler.1081546.B.1726157233254514.ack@bugs.debian.org> <172615722963.13536.260751860512984317.reportbug@angela.anarc.at> <87seu4lo0d.fsf@angela.anarc.at> <172615722963.13536.260751860512984317.reportbug@angela.anarc.at> <Z96-F5mInjIDemtr@eldamar.lan> <172615722963.13536.260751860512984317.reportbug@angela.anarc.at>
Hi Antoine,
On Sat, Mar 22, 2025 at 02:41:43PM +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Thu, Sep 12, 2024 at 02:34:26PM -0400, Antoine Beaupré wrote:
> > The same fellow DD who suggested filing this bug helpfully found what
> > seems to be a similar issue:
> >
> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7549
> >
> > ... except that bug report is much older, and seems to apply to 5.x
> > kernels. I didn't have that issue back then, nor in 6.9, so I don't
> > think it's the same issue (nor is it the same symptoms).
> >
> > Digging in that issue tracker, however, i do find a bunch of somewhat
> > similar regressions:
> >
> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11797
> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11899
> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11975
> >
> > I'll also add some more data to back up my claim this is a new
> > regression from the upgrade:
> >
> > anarcat@angela:~$ sudo grep -c GPU\ HANG /var/log/kern.log*
> > /var/log/kern.log:7
> > /var/log/kern.log.1:0
> > /var/log/kern.log.2.gz:0
> > /var/log/kern.log.3.gz:0
> > /var/log/kern.log.4.gz:0
> > anarcat@angela:~$ ls -al /var/log/kern.log*
> > -rw-r----- 1 root adm 2 082 950 2024-09-12 14:30 /var/log/kern.log
> > -rw-r----- 1 root adm 3 420 621 2024-09-10 09:54 /var/log/kern.log.1
> > -rw-r----- 1 root adm 285 294 2024-09-03 09:21 /var/log/kern.log.2.gz
> > -rw-r----- 1 root adm 386 756 2024-08-26 08:53 /var/log/kern.log.3.gz
> > -rw-r----- 1 root adm 248 500 2024-08-18 00:00 /var/log/kern.log.4.gz
> >
> > ie. 7 hangs in the `kern.log` file, which started two days ago, and none
> > in the other files, going back a month.
> >
> > Interestingly, the kernel was upgraded early after the kern.log.1
> > rotation:
> >
> > Start-Date: 2024-09-04 09:30:57
> > Commandline: apt upgrade
> > Requested-By: anarcat (1000)
> > Install: linux-kbuild-6.10.6+bpo:amd64 (6.10.6-1~bpo12+1, automatic), linux-image-6.10.6+bpo-amd64:amd64 (6.10.6-1~bpo12+1, automatic), linux-headers-6.10.6+bpo-amd64:amd64 (6.10.6-1~bpo12+1, automatic), linux-headers-6.10.6+bpo-common:amd64 (6.10.6-1~bpo12+1, automatic)
> > Upgrade: linux-cpupower:amd64 (6.9.7-1~bpo12+1, 6.10.6-1~bpo12+1), linux-headers-amd64:amd64 (6.9.7-1~bpo12+1, 6.10.6-1~bpo12+1), dh-debputy:amd64 (0.1.39~bpo12+1, 0.1.48~bpo12+1), libssl3:amd64 (3.0.14-1~deb12u1, 3.0.14-1~deb12u2), linux-image-amd64:amd64 (6.9.7-1~bpo12+1, 6.10.6-1~bpo12+1), tailspin:amd64 (2.0.0+dfsg-1, 3.0.2+dfsg-1), libssl-dev:amd64 (3.0.14-1~deb12u1, 3.0.14-1~deb12u2), python3-lsprotocol:amd64 (2023.0.0-1, 2023.0.1-1~bpo12+1), libcpupower1:amd64 (6.9.7-1~bpo12+1, 6.10.6-1~bpo12+1), firefox-esr:amd64 (115.14.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), openssl:amd64 (3.0.14-1~deb12u1, 3.0.14-1~deb12u2), linux-libc-dev:amd64 (6.9.7-1~bpo12+1, 6.10.6-1~bpo12+1)
> > End-Date: 2024-09-04 09:31:48
> >
> > ... but I booted in the new kernel only 4 days ago:
> >
> > anarcat@angela:~$ last reboot
> > reboot system boot 6.10.6+bpo-amd64 Thu Sep 12 11:12 still running
> > reboot system boot 6.10.6+bpo-amd64 Tue Sep 10 09:54 still running
> > reboot system boot 6.10.6+bpo-amd64 Mon Sep 9 09:24 still running
> > reboot system boot 6.10.6+bpo-amd64 Sun Sep 8 12:36 still running
> >
> > ... so this would probably explain the lack of hangs in the older log.
>
> I assume the problem is still present in fresh kernel in unstable or
> experimental? If so can you report it upstream as Ben suggested and
> link back here the specific report?
Any news here?
Regards,
Salvatore
Reply to: