On Mon, Feb 21, 2022 at 3:30 AM Thorsten Leemhuis <regressions@xxxxxxxxxxxxx> wrote: > > Hi, this is your Linux kernel regression tracker. > > I noticed a regression report in bugzilla.kernel.org that afaics nobody > acted upon since it was reported about a week ago, that's why I decided > to forward it to the lists and all the relevant people. To quote > https://bugzilla.kernel.org/show_bug.cgi?id=215600 : > > > Richard Herbert 2022-02-12 22:13:07 UTC > > > > Created attachment 300445 [details] > > Details > > > > When attempting to play some types of videos with VLC 3.0.16 (eg. *.flv, *.mp4), when running kernels 5.17-rc1 to 5.17-rc3, only the audio portion is heard and the VLC video screen remains black. Meanwhile, many of these entries are written per second to /var/log/syslog: > > > > 2/12/22 3:41 PM starbug kernel [drm:radeon_uvd_cs_parse [radeon]] *ERROR* Failed waiting for UVD message (-1)! > > 2/12/22 3:41 PM starbug kernel [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! > > 2/12/22 3:41 PM starbug kernel [drm:radeon_uvd_cs_parse [radeon]] *ERROR* Failed waiting for UVD message (-1)! > > 2/12/22 3:41 PM starbug kernel [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! > > 2/12/22 3:41 PM starbug kernel [drm:radeon_uvd_cs_parse [radeon]] *ERROR* Failed waiting for UVD message (-1)! > > 2/12/22 3:41 PM starbug kernel [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! > > > > > > The problem doesn't occur in kernels of the 5.16 series. It may have been introduced here: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_uvd.c?id=v5.16&id2=v5.17-rc1 > > > > > > Thanks! > > Could somebody take a look into this? Or was this discussed somewhere > else already? Or even fixed? This is a fix on the bug report. Alex > > Anyway, to get this tracked: > > #regzbot introduced: v5.16..v5.17-rc1 > #regzbot from: Richard Herbert <rherbert@xxxxxxxxxxxx> > #regzbot title: drm: radeon: no sound on video, *ERROR* Failed waiting > for UVD message > #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215600 > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > > P.S.: As the Linux kernel's regression tracker I'm getting a lot of > reports on my table. I can only look briefly into most of them and lack > knowledge about most of the areas they concern. I thus unfortunately > will sometimes get things wrong or miss something important. I hope > that's not the case here; if you think it is, don't hesitate to tell me > in a public reply, it's in everyone's interest to set the public record > straight. > > -- > Additional information about regzbot: > > If you want to know more about regzbot, check out its web-interface, the > getting start guide, and the references documentation: > > https://linux-regtracking.leemhuis.info/regzbot/ > https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md > https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md > > The last two documents will explain how you can interact with regzbot > yourself if your want to. > > Hint for reporters: when reporting a regression it's in your interest to > CC the regression list and tell regzbot about the issue, as that ensures > the regression makes it onto the radar of the Linux kernel's regression > tracker -- that's in your interest, as it ensures your report won't fall > through the cracks unnoticed. > > Hint for developers: you normally don't need to care about regzbot once > it's involved. Fix the issue as you normally would, just remember to > include 'Link:' tag in the patch descriptions pointing to all reports > about the issue. This has been expected from developers even before > regzbot showed up for reasons explained in > 'Documentation/process/submitting-patches.rst' and > 'Documentation/process/5.Posting.rst'.
