Hi,
On 5/13/22 15:25, Zack Rusin wrote:
On May 13, 2022, at 3:43 AM, Thorsten Leemhuis <regressions@leemhuis.info mailto:regressions@leemhuis.info> wrote:
CCing airlied
On 09.05.22 14:02, Javier Martinez Canillas wrote:
On 5/9/22 13:55, Hans de Goede wrote: [snip]
Fixes: dabdcdc9822a ("drm/vmwgfx: Switch to mode_cmd2") BugLink: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.r... https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.redhat.com%2Fshow_bug.cgi%3Fid%3D2072556&data=05%7C01%7Czackr%40vmware.com%7Ca34647a1351748917ad608da34b459a0%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637880246471436744%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LSQP%2Bqnf4p51QsF%2B7ZkvKlB5gSx0%2FgRUsgcIPChR33g%3D&reserved=0 Signed-off-by: Hans de Goede <hdegoede@redhat.com mailto:hdegoede@redhat.com>
Zack fixed this already:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcgit.freed... https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcgit.freedesktop.org%2Fdrm%2Fdrm-misc%2Fcommit%2F%3Fid%3D5405d25b9e8e6&data=05%7C01%7Czackr%40vmware.com%7Ca34647a1351748917ad608da34b459a0%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637880246471436744%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=IMtLj94VBo3Bv8oCGmbatBmT%2F2%2B9xkIptnlPTPuHMHc%3D&reserved=0
I see, but it seems that this was never pushed to drm-misc-fixes, so this is still broken in 5.18-rc#
Indeed. Agreed that should be cherry-picked in -fixes as well.
Looks to me like nobody did that and this regression fix is missing in
No, it has been done. It’s after rc6 so the patch is in drm-misc-next-fixes you can see it at: https://cgit.freedesktop.org/drm/drm-misc/commit/drivers/gpu/drm/vmwgfx?h=dr... https://cgit.freedesktop.org/drm/drm-misc/commit/drivers/gpu/drm/vmwgfx?h=drm-misc-next-fixes&id=5405d25b9e8e6e0d3bdb04833d528a9bb35fe7ce
Erm, the after rc6 rule is for fixes for the next cycle, if we want to get this in this cycle (which IMHO we want) it should have been in drm-misc-fixes before the PR which was send to Linus today.
At this point in the cycle the best thing is probably to just send it directly to Linus. That or wait till 5.19, but it seems that for some reason (likely changes elsewhere changing the stack) this long standing bugs is hit 100% with 5.18, where as before we seemed to be lucky and not hit it.
Regards,
Hans