On Mon, 9 Sep 2019 at 14:15, Koenig, Christian wrote:
>
> I agree with Daniels analysis.
>
> It looks like the problem is simply that PM turns of a block before all
> work is done on that block.
>
> Have you opened a bug report yet? If not then that would certainly help
> cause it is really hard t
I agree with Daniels analysis.
It looks like the problem is simply that PM turns of a block before all
work is done on that block.
Have you opened a bug report yet? If not then that would certainly help
cause it is really hard to extract all necessary information from that
mail thread.
Regard
On Thu, 5 Sep 2019 at 12:58, Daniel Vetter wrote:
>
> I think those fences are only emitted for CS, not display related.
> Adding Christian König.
More fresh kernel log with 5.3RC7 - the issue still happens.
https://pastebin.com/tyxkWJYV
--
Best Regards,
Mike Gavrilov.
On Thu, 5 Sep 2019 at 12
On Thu, Sep 5, 2019 at 12:27 AM Mikhail Gavrilov
wrote:
>
> On Wed, 4 Sep 2019 at 13:37, Daniel Vetter wrote:
> >
> > Extend your backtrac warning slightly like
> >
> > WARN(r, "we're stuck on fence %pS\n", fence->ops);
> >
> > Also adding Harry and Alex, I'm not really working on amdgpu
On Wed, 4 Sep 2019 at 13:37, Daniel Vetter wrote:
>
> Extend your backtrac warning slightly like
>
> WARN(r, "we're stuck on fence %pS\n", fence->ops);
>
> Also adding Harry and Alex, I'm not really working on amdgpu ...
[ 3511.998320] [ cut here ]
[ 3511.998714] w
On Wed, Sep 04, 2019 at 09:17:16AM +0800, Hillf Danton wrote:
> Daniel Vetter
> >>
> >> Now 11:01pm and "gnome shell stuck warning" not appear since 19:17. So
> >> looks like issue happens only when computer blocked and monitor in
> >> power save mode.
> >
> > I'd bet on runtime pm or some other p
On Tue, 3 Sep 2019 11:48:12 +0500 From: Mikhail Gavrilov
> On Fri, 30 Aug 2019 at 08:30, Hillf Danton wrote:
> >
> > Add a warning to show if it makes sense in field: neither regression nor
> > problem will have been observed with the warning printed.
>
> I caught the problem.
>
>
> [21793.09
Daniel Vetter
>>
>> Now 11:01pm and "gnome shell stuck warning" not appear since 19:17. So
>> looks like issue happens only when computer blocked and monitor in
>> power save mode.
>
> I'd bet on runtime pm or some other power saving feature in amdgpu
> shutting the interrupt handling down before
On Tue, Sep 3, 2019 at 8:07 PM Mikhail Gavrilov
wrote:
>
> On Tue, 3 Sep 2019 at 13:21, Hillf Danton wrote:
> >
> > Describe the problems you are experiencing please.
> > Say is the screen locked up? Machine lockedup?
> > Anything unnormal after you see the warning?
> >
>
> According to my observ
On Tue, 3 Sep 2019 at 13:21, Hillf Danton wrote:
>
> Describe the problems you are experiencing please.
> Say is the screen locked up? Machine lockedup?
> Anything unnormal after you see the warning?
>
According to my observations, all "gnome shell stuck warning" happened
when me not sitting on t
On Fri, 30 Aug 2019 at 08:30, Hillf Danton wrote:
>
> Add a warning to show if it makes sense in field: neither regression nor
> problem will have been observed with the warning printed.
>
I caught the problem.
[21793.094289] [ cut here ]
[21793.094296] gnome shell stuck
On Fri, 30 Aug 2019 06:04:06 +0800 Mikhail Gavrilov wrote:
> On Sun, Aug 25, 2019 at 10:13:05PM +0800, Hillf Danton wrote:
> > Can we try to add the fallback timer manually?
> >
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> > @@ -322,6 +3
On Sun, Aug 25, 2019 at 10:13:05PM +0800, Hillf Danton wrote:
> Can we try to add the fallback timer manually?
>
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> @@ -322,6 +322,10 @@ int amdgpu_fence_wait_empty(struct amdgp
> }
>
On Sun, Aug 25, 2019 at 10:13:05PM +0800, Hillf Danton wrote:
>
> On Sun, 25 Aug 2019 04:28:01 -0700 Mikhail Gavrilov wrote:
> > Hi folks,
> > I left unblocked gnome-shell at noon, and when I returned at the
> > evening I discovered than monitor not sleeping and show open gnome
> > activity. At fi
On Sun, 25 Aug 2019 04:28:01 -0700 Mikhail Gavrilov wrote:
> Hi folks,
> I left unblocked gnome-shell at noon, and when I returned at the
> evening I discovered than monitor not sleeping and show open gnome
> activity. At first, I thought that some application did not let fall
> asleep the system.
Hi folks,
I left unblocked gnome-shell at noon, and when I returned at the
evening I discovered than monitor not sleeping and show open gnome
activity. At first, I thought that some application did not let fall
asleep the system. But when I try to move the mouse, I realized that
the system hanged.
16 matches
Mail list logo
