Hey, Den 2026-05-22 kl. 22:54, skrev Linus Torvalds: > On Fri, 22 May 2026 at 13:44, Rodrigo Vivi <[email protected]> wrote: >> >> Any journal saving the kernel buf log of previous boots? Preferably with >> some drm.debug flags enabled 0xf likely > > Note that this is very much not repeatable. I have no idea what > triggered it, and I don't think it was necessarily brought on by > anything recent. > > I've seen timeouts before, but looking at my logs, the last time it > caused a complete hang was Feb 3. So a few months ago... > >> What was the last drm-fixes pull you got in this >> 7.1.0-rc3-00073-ga6920214ba75 ? > > That's just mainline commit v7.1-rc3-71-g31e62c2ebbfd with two random > small patches on top that change some build flags (this is my "built > by clang" tree) > > So the last drm merge would have been 51d24842acb9 Merge tag > 'drm-fixes-2026-05-08-1' of https://gitlab.freedesktop.org/drm/kernel > > Linus
Just thinking that since the guc_id=0, the most likely culprit is in the kernel migration code. There are 3 places you'll most likely interact with it: - Zeroing VRAM bo's on allocation - On integrated, it may clear system memory bo's CCS data. - Moving memory between system and VRAM. I'm assuming you only have a discrete card, so it's either happening on allocation or memory movement. Since it's sporadic, it *might* be more likely the latter. Does it happen more frequently when loading VRAM intensive programs? Kind regards, ~Maarten Lankhorst
