https://bugs.freedesktop.org/show_bug.cgi?id=100375
--- Comment #2 from Edward O'Callaghan funfunctor@folklore1984.net --- (In reply to Michel Dänzer from comment #1)
set_root doesn't look directly related to amdgpu or drm, so this could be memory corruption. KASAN might give more information.
Does this only happen when forcing an invalid EDID?
Hi Michel,
yes it only happens on shutdown with a EDID blob passed at boot. Actually the EDID blob passed I don't think is invalid, I don't know where it is getting the one in the trace from that could be from perhaps the monitor itself.
Is the kernel there trying to open the EDID blob on a umounted fs?