Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
MIME-Version: 1.0
References: <978944b7-4e71-475a-2fe6-c414d3e8f64e@leemhuis.info>
In-Reply-To: <978944b7-4e71-475a-2fe6-c414d3e8f64e@leemhuis.info>
From:   Alex Deucher <alexdeucher@gmail.com>
Date:   Mon, 21 Feb 2022 10:10:44 -0500
Message-ID: <CADnq5_OS2jT1eRjjMf_c1OkeEEd1CJa7_T+yBoOtNKrLnWduZw@mail.gmail.com>
Subject: Re: Bug 215600 - Radeon - *ERROR* Failed waiting for UVD message
To:     Thorsten Leemhuis <regressions@leemhuis.info>
Cc:     Alex Deucher <alexander.deucher@amd.com>,
        =?UTF-8?Q?Christian_K=C3=B6nig?= <christian.koenig@amd.com>,
        "Pan, Xinhui" <Xinhui.Pan@amd.com>,
        "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
        "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, Feb 21, 2022 at 3:30 AM Thorsten Leemhuis
<regressions@leemhuis.info> 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=3D215600 :
>
> >  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]] *E=
RROR* 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]] *E=
RROR* 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]] *E=
RROR* Invalid command stream !
> >
> >
> > The problem doesn't occur in kernels of the 5.16 series.  It may have b=
een introduced here:
> >
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff=
/drivers/gpu/drm/radeon/radeon_uvd.c?id=3Dv5.16&id2=3Dv5.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@sympatico.ca>
> #regzbot title: drm: radeon: no sound on video, *ERROR* Failed waiting
> for UVD message
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=3D215600
>
> 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'.