From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: ** X-Spam-Status: No, score=2.7 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,HTTPS_HTTP_MISMATCH, MAILING_LIST_MULTI,MIME_HTML_MOSTLY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AD46BC433B4 for ; Thu, 1 Apr 2021 06:56:07 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 230F2600EF for ; Thu, 1 Apr 2021 06:56:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 230F2600EF Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=amd-gfx-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 9D96F6E2E6; Thu, 1 Apr 2021 06:56:06 +0000 (UTC) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) by gabe.freedesktop.org (Postfix) with ESMTPS id B91F76EAD6 for ; Wed, 31 Mar 2021 15:47:40 +0000 (UTC) Received: by mail-lf1-x133.google.com with SMTP id i26so29742037lfl.1 for ; Wed, 31 Mar 2021 08:47:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VL1HvJMWv5vpUExbqykDYQ81VmpgLN1I8wPZc/3kjXk=; b=PFv/X4cm7iS8rFn0nBH6Q8ah0rkfkz46VyOjgcbgWdK4Yrt7SnQSDkb6sBesywhHkw ainbje8zocr/8Lqz8228gpnohIVhYtZTEnNBWIfBYlUsmKu9Q3wMtZWw+0cLajox8FcK +Ns1ee6vRt9WnRSrDUq0e/2SU17+coHLMqMoxIJlNjhTgsrEWdocyTaQGczHfV5WFURe HJaGW6UYjZUxsWikCRpq5G5pgYnnHTSilWW1rr9r85XTQXGax0nM8hNTy6gG6Rfma/9L L+3RvIw8QGWp5AIji/77yA8VWHSLCsw3P2DsK38+ut79EeOKp0BhNIK/ZjPVSAZ0/I+x Pb9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VL1HvJMWv5vpUExbqykDYQ81VmpgLN1I8wPZc/3kjXk=; b=tDBhyX6Gx+tEYsjXsb94iX+RhXpmoXNSgtCZIY5jNys52eoUngsxHTEg+q5/T/3pMj V9+71BMtQyKKYjbz7b4MfMMMGnp3WQhzJGLG1mOgnzv4AZCz0d0D/jt650eIcEA9cHiL MwUNLZUwr79rvhzVGH5CTVFz6xuMoM4iZ5yyh+imPlC14ifimvyTLMnqXxCQ+wN9mRsl vPx4zRePaimjGa+2AH/tDeMg/RyuKvUZbEWQsGFD28d2KdTOgbNegmLBmjPDgEfg66x7 HnLT36rAtx90CDIjru8VjRT6c82kum+yQezyb0xzbaTxz6fqfbE+kF8XLTqg7yJSr57q kXlw== X-Gm-Message-State: AOAM531O38e+tjy8pqi9j4xp00DwkSAgxcPOqDawDUBuvmsrZLhIbiDx Hu5GGHx9ZOafpRPDS7lqPMXb67GYFIMsnq6KBqp8FINTk+E= X-Google-Smtp-Source: ABdhPJwrGLDeInwSskDPm9JV8QJ80jo0kRcAmRqjM3QqIdxV8VWMOgsX1lNautn4supInDvjiyhg8TnmvRb16vRusT4= X-Received: by 2002:a19:860b:: with SMTP id i11mr2556234lfd.330.1617205659184; Wed, 31 Mar 2021 08:47:39 -0700 (PDT) MIME-Version: 1.0 References: <388b2a9d-0e63-b70f-28ed-6297a524fb76@amd.com> <909002f5-691c-1cbb-1e44-a99217be8791@gmail.com> <3d3563f3-f093-f293-e237-b87306a4cede@amd.com> <7914f67b-e011-36ec-3f6d-1614ce96e3c4@amd.com> <0eee8e42-5da8-1ce3-bff7-fe6e2ab18cde@amd.com> <6a71add4-d2d0-c17a-de8a-6e2b6e248483@gmail.com> In-Reply-To: <6a71add4-d2d0-c17a-de8a-6e2b6e248483@gmail.com> From: Alberto Salvia Novella Date: Wed, 31 Mar 2021 17:47:27 +0200 Message-ID: Subject: Re: Interlaced resolutions hang the desktop To: =?UTF-8?Q?Christian_K=C3=B6nig?= X-Mailman-Approved-At: Thu, 01 Apr 2021 06:56:05 +0000 X-BeenThere: amd-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion list for AMD gfx List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: alexander.deucher@amd.com, benh@kernel.crashing.org, linux-fbdev@vger.kernel.org, =?UTF-8?Q?Christian_K=C3=B6nig?= , amd-gfx@lists.freedesktop.org Content-Type: multipart/mixed; boundary="===============1930839491==" Errors-To: amd-gfx-bounces@lists.freedesktop.org Sender: "amd-gfx" --===============1930839491== Content-Type: multipart/alternative; boundary="000000000000d8311305bed70876" --000000000000d8311305bed70876 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Restarting the *display manager* service works and, more importantly, makes the bug no longer reproducible. Restarting the *window manager* doesn't work. *Changing* display manager makes the bug still reproducible. Maybe this is due to xorg-server, isn't it? On Wed, 31 Mar 2021 at 16:55, Christian K=C3=B6nig < ckoenig.leichtzumerken@gmail.com> wrote: > Well the hardware is working fine as far as I can see. > > Can you try to kill the X server over SSH and see if you then get some > screen update? > > Regards, > Christian. > > Am 31.03.21 um 16:52 schrieb Alberto Salvia Novella: > > Output > > . > > On Wed, 31 Mar 2021 at 16:36, Christian K=C3=B6nig > wrote: > >> Mhm strange. >> >> Can you get me the output of "sudo cat >> /sys/kernel/debug/dri/0/radeon_fence_info" when the problem happens? >> >> Thanks, >> Christian. >> >> Am 31.03.21 um 16:33 schrieb Alberto Salvia Novella: >> >> - The computer still replies to *ping*. >> - The *journal* shows no errors, but a few warnings >> >> . >> - The *mouse* doesn't freeze. >> >> On Wed, 31 Mar 2021 at 10:09, Christian K=C3=B6nig >> wrote: >> >>> Can you access the system over the network and see if there is anything >>> in the system log? >>> >>> It sounds like the display stack has crashed, but when the sound keeps >>> playing the system is most likely still responsive over network. >>> >>> Thanks, >>> Christian. >>> >>> Am 31.03.21 um 10:05 schrieb Alberto Salvia Novella: >>> >>> What happens is this simple: after a few minutes, about 6 or so, the >>> entire content of the screen stays still. In some minor situations only= the >>> applications panel of KDE Plasma. >>> >>> If music is playing it continues playing, so only graphics are hung. Ye= t >>> in most cases the power button won't shut down the computer, as it usua= lly >>> does. >>> >>> At least this is the case using kwin on x11, and not on wayland. It onl= y >>> happens on "radeon" and not on Intel or "radeonhd". >>> >>> On Wed, 31 Mar 2021 at 09:48, Christian K=C3=B6nig >>> wrote: >>> >>>> Correct, but a TV is intended for videos only. That's why it implement= s >>>> only the lower HDMI standard. >>>> >>>> Interlaced transmits only halve the lines with each frame, so a 60Hz >>>> mode effectively either becomes a 30Hz mode, halving the vertical >>>> resolution or adaptive motion compensated which the know visual artifa= cts. >>>> Depending on what the deinterlacing setting on your TV is. >>>> >>>> You could just add a progressive 1920x540@60 or 1920x1080@30 mode >>>> manually and would have the same effect with probably better quality. = See >>>> https://de.wikipedia.org/wiki/Deinterlacing >>>> >>>> for reference. >>>> >>>> If you can give us some more information what is happening when the >>>> system freeze we could try to narrow this down, but we can't spend muc= h >>>> time on a very specific use case in a driver which is in maintenance m= ode. >>>> >>>> Regards, >>>> Christian. >>>> >>>> Am 31.03.21 um 09:21 schrieb Alberto Salvia Novella: >>>> >>>> 24fps is intended for video only. Anything interactive at 24fps, as >>>> just moving the mouse around, is extremely choppy. >>>> >>>> No way anyone would prefer that over an interlaced resolution or a >>>> lower resolution. That is, by far, the worst option. >>>> >>>> Just try it on your screen, set it to 24Hz or alike, and tell me your >>>> experience. You can't even tell where the mouse is going to go. >>>> >>>> On Wed, 31 Mar 2021 at 08:44, Christian K=C3=B6nig >>>> wrote: >>>> >>>>> Hi Alberto, >>>>> >>>>> well a frame rate of 24Hz is perfectly reasonable for a TV and deskto= p >>>>> usage. >>>>> >>>>> This is probably caused by the TVs limited HDMI bandwidth and a >>>>> refresh rate of 30/25 Hz for the interlaced mode isn't much better ei= ther. >>>>> >>>>> Regards, >>>>> Christian. >>>>> >>>>> Am 30.03.21 um 22:59 schrieb Alberto Salvia Novella: >>>>> >>>>> The frame-rate at 24Hz is extremely poor for normal desktop usage. >>>>> >>>>> If the highest resolution, aka 1080p, uses that refresh rate then the >>>>> desktop will default to that frame-rate. >>>>> >>>>> Other progressive modes don't exhibit any issue. >>>>> >>>>> On Tue, 30 Mar 2021 at 18:26, Christian K=C3=B6nig < >>>>> christian.koenig@amd.com> wrote: >>>>> >>>>>> Hi Alberto, >>>>>> >>>>>> I think the driver should only support resolutions that are >>>>>> *progressive*, but also at least of *50Hz*. >>>>>> >>>>>> >>>>>> Why do you think so?, the 24Hz resolution seems to be the native one >>>>>> of the display. >>>>>> >>>>>> Regards, >>>>>> Christian. >>>>>> >>>>>> Am 30.03.21 um 17:37 schrieb Alberto Salvia Novella: >>>>>> >>>>>> This is why I'm using interlaced: >>>>>> >>>>>> $ *xrandr* >>>>>> Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 819= 2 >>>>>> DisplayPort-0 disconnected (normal left inverted right x axis y axis= ) >>>>>> HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x >>>>>> axis y axis) 16mm x 9mm >>>>>> 1920x*1080i* 60.00*+ 50.00 59.94 >>>>>> 1920x1080 *24.00* 23.98 >>>>>> 1280x*720* 60.00 50.00 59.94 >>>>>> 1024x768 75.03 70.07 60.00 >>>>>> 832x624 74.55 >>>>>> 800x600 72.19 75.00 60.32 56.25 >>>>>> 720x576 50.00 >>>>>> 720x576i 50.00 >>>>>> 720x480 60.00 59.94 >>>>>> 720x480i 60.00 59.94 >>>>>> 640x480 75.00 72.81 66.67 60.00 59.94 >>>>>> 720x400 70.08 >>>>>> DVI-0 disconnected (normal left inverted right x axis y axis) >>>>>> >>>>>> I think the driver should only support resolutions that are >>>>>> *progressive*, but also at least of *50Hz*. >>>>>> >>>>>> On Tue, 30 Mar 2021 at 15:41, Christian K=C3=B6nig < >>>>>> ckoenig.leichtzumerken@gmail.com> wrote: >>>>>> >>>>>>> Mhm, no idea why an interlaced resolution would cause a crash. Mayb= e >>>>>>> some miscalculation in the display code. >>>>>>> >>>>>>> But apart from that if you just connected your PC to a TV I also >>>>>>> wouldn't recommend using an interlaced resolution in the first plac= e. >>>>>>> >>>>>>> See those resolutions only exists for backward compatibility with >>>>>>> analog hardware. >>>>>>> >>>>>>> I think we would just disable those modes instead of searching for >>>>>>> the bug. >>>>>>> >>>>>>> Regards, >>>>>>> Christian. >>>>>>> >>>>>>> Am 30.03.21 um 11:07 schrieb Alberto Salvia Novella: >>>>>>> >>>>>>> I guessed so. >>>>>>> >>>>>>> The GPU is a Radeon HD5870, and the screen is an old Telefunken TV >>>>>>> (TLFK22LEDPVR1). >>>>>>> >>>>>>> Since my real display got into repair I used this TV meanwhile, and >>>>>>> to my surprise it froze the system. >>>>>>> >>>>>>> On Tue, 30 Mar 2021 at 10:15, Christian K=C3=B6nig < >>>>>>> christian.koenig@amd.com> wrote: >>>>>>> >>>>>>>> Hi Alberto, >>>>>>>> >>>>>>>> well what hardware do you have? >>>>>>>> >>>>>>>> Interlaced resolutions are not used any more on modern hardware, s= o >>>>>>>> they >>>>>>>> are not well tested. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Christian. >>>>>>>> >>>>>>>> Am 30.03.21 um 10:04 schrieb Alberto Salvia Novella: >>>>>>>> > The entire desktop hangs after some minutes when using the modul= e >>>>>>>> > "radeon" with an interlaced resolution. >>>>>>>> > >>>>>>>> > Easier to trigger by playing a video on Firefox, at least on >>>>>>>> kwin_x11. >>>>>>>> > Wayland didn't exhibit the problem. >>>>>>>> > >>>>>>>> > Other display drivers, from different computers I have tried, >>>>>>>> didn't >>>>>>>> > allow those interlaced resolutions all together. It seems they >>>>>>>> know >>>>>>>> > there will be problems. >>>>>>>> >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> amd-gfx mailing listamd-gfx@lists.freedesktop.orghttps://lists.free= desktop.org/mailman/listinfo/amd-gfx >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > --000000000000d8311305bed70876 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Restarting the display manager service works a= nd, more importantly, makes the bug no longer reproducible.

<= /div>
Restarting the window manager doesn't work.
=
Changing display manager makes the bug still reproduc= ible.

Maybe this is due to xorg-server, isn't = it?

On Wed, 31 Mar 2021 at 16:55, Christian K=C3=B6nig <ckoenig.leichtzumerken@gmail.c= om> wrote:
=20
On Wed, 31 Mar 2021 at 16:36, Christian K=C3=B6nig <christian.koenig@amd.com> wrote:
Mhm strange.

Can you get me the output of "sudo cat /sys/kernel/debug/dri/0/radeon_fence_info" when the proble= m happens?

Thanks,
Christian.

Am 31.03.21 um 16:33 schrieb Alberto Salvia Novella:
- The computer still replies to ping.
- The journal shows no errors, but a few warnings.
- The mouse doesn't freeze.

On Wed, 31 Mar 2021 a= t 10:09, Christian K=C3=B6nig <christian.koenig@amd.com> wrote:
Can you access the system over the network and see if there is anything in the system log?

It sounds like the display stack has crashed, but when the sound keeps playing the system is most likely still responsive over network.

Thanks,
Christian.

Am 31.03.21 um 10:05 schrieb Alberto Salvia Novella:
What happens is this simple: after a few minutes, about 6 or so, the entire content of the screen stays still. In some minor situations only the applications panel of KDE Plasma.

If music is playing it continues playing, so only graphics are hung. Yet in most cases the power button won't shut down the computer= , as it usually does.

At least this is the case using kwin on x11, and not on wayland. It only happens on "radeon" and not on Intel or "rade= onhd".

On Wed, 31 Ma= r 2021 at 09:48, Christian K=C3=B6nig <christian.koenig@amd= .com> wrote:
Correct, but a TV is intended for videos only. That's why it implements only the lower HDMI standard.

Interlaced transmits only halve the lines with each frame, so a 60Hz mode effectively either becomes a 30Hz mode, halving the vertical resolution or adaptive motion compensated which the know visual artifacts. Depending on what the deinterlacing setting on your TV is.

You could just add a progressive 1920x540@60 or 1920x1080@30 mode manually and would have the same effect with probably better quality. See https://de.wikipedi= a.org/wiki/Deinterlacing for reference.

If you can give us some more information what is happening when the system freeze we could try to narrow this down, but we can't spend much time on a very specific use case in a driver which is in maintenance mode.

Regards,
Christian.

Am 31.03.21 um 09:21 schrieb Alberto Salvia Novella:
24fps is intended for video only. Anything interactive at 24fps, as just moving the mouse around, is extremely choppy.

No way anyone would prefer that over an interlaced resolution or a lower resolution. That is, by far, the worst option.

Just try it on your screen, set it to 24Hz or alike, and tell me your experience. You can't even tell where the mouse is going to go.

On Wed, 31 Mar 2021 at 08:44, Christian K=C3=B6nig <christian.koenig@amd.com> wrote:
Hi Alberto,

well a frame rate of 24Hz is perfectly reasonable for a TV and desktop usage.

This is probably caused by the TVs limited HDMI bandwidth and a refresh rate of 30/25 Hz for the interlaced mode isn't much better either.

Regards,
Christian.

Am 30.03.21 um 22:59 schrieb Alberto Salvia Novella:
The frame-rate at 24Hz is extremely poor for normal desktop usage.

If the highest resolution, aka 1080p, uses that refresh rate then the desktop will default to that frame-rate.

Other progressive modes don't exhibit any issue.

On Tue, 30 Mar 2021 at 18:26, Christian K=C3=B6nig <christian.koenig@amd.com>= ; wrote:
Hi Alberto,

I think the driver should only support resolutions that are progressive, but also at least of 50Hz<= /b>.

Why do you think so?, the 24Hz resolution seems to be the native one of the display.

Regards,
Christian.

Am 30.03.21 um 17:37 schrieb Alberto Salvia Novella:
This is why I'm using interlaced:

$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 16mm x 9mm
=C2=A0 =C2=A01920x1080= i =C2=A0 =C2=A060.00*+ =C2=A050.00= =C2=A0 =C2=A059.94 =C2=A0
=C2=A0 =C2=A01920x1080 = =C2=A0 =C2=A0 24.00 =C2=A0 =C2=A023.98 =C2=A0=
=C2=A0 =C2=A01280x720<= /b> =C2=A0 =C2=A0 =C2=A060.00 =C2=A0 =C2=A0= 50.00 =C2=A0 =C2=A059.94 =C2=A0
=C2=A0 =C2=A01024x768 =C2= =A0 =C2=A0 =C2=A075.03 =C2=A0 =C2=A070.07 =C2=A0= =C2=A060.00 =C2=A0
=C2=A0 =C2=A0832x624 =C2= =A0 =C2=A0 =C2=A0 74.55 =C2=A0
=C2=A0 =C2=A0800x600 =C2= =A0 =C2=A0 =C2=A0 72.19 =C2=A0 =C2=A075.00 =C2=A0= =C2=A060.32 =C2=A0 =C2=A056.25 =C2=A0
=C2=A0 =C2=A0720x576 =C2= =A0 =C2=A0 =C2=A0 50.00 =C2=A0
=C2=A0 =C2=A0720x576i =C2= =A0 =C2=A0 =C2=A050.00 =C2=A0
=C2=A0 =C2=A0720x480 =C2= =A0 =C2=A0 =C2=A0 60.00 =C2=A0 =C2=A059.94 =C2=A0=
=C2=A0 =C2=A0720x480i =C2= =A0 =C2=A0 =C2=A060.00 =C2=A0 =C2=A059.94 =C2=A0=
=C2=A0 =C2=A0640x480 =C2= =A0 =C2=A0 =C2=A0 75.00 =C2=A0 =C2=A072.81 =C2=A0= =C2=A066.67 =C2=A0 =C2=A060.00 =C2=A0 =C2=A0= 59.94 =C2=A0
=C2=A0 =C2=A0720x400 =C2= =A0 =C2=A0 =C2=A0 70.08 =C2=A0
DVI-0 disconnected (normal left inverted right x axis y axis)

I think the driver should only support resolutions that are p= rogressive, but also at least of 5= 0Hz.

On Tue, 30 Mar 2021 at 15:41, Christian K=C3=B6n= ig <ckoenig.leichtzumerken@gma= il.com> wrote:
Mhm, no idea why an interlaced resolution would cause a crash. Maybe some miscalculation in the display code.
But apart from that if you just connected your PC to a TV I also wouldn'= t recommend using an interlaced resolution in the first place.

See those resolutions only exists for backward compatibility with analog hardware.

I think we would just disable those modes instead of searching for the bug.

Regards,
Christian.

Am 30.03.21 um 11:07 schrieb Alberto Salvia Novella:
I guessed so.

The GPU is a Radeon HD5870, and the screen is an old Telefunken TV (TLFK22LEDPVR1).

Since my real display got into repair I used this TV meanwhile, and to my surprise it froze the system.

On Tue, 30 Mar 2021 at 10:15, Christian K=C3=B6nig <christian.koeni= g@amd.com> wrote:
Hi Alberto,

well what hardware do you have?

Interlaced resolutions are not used any more on modern hardware, so they
are not well tested.

Regards,
Christian.

Am 30.03.21 um 10:04 schrieb Alberto Salvia Novella:
> The entire desktop hangs after some minutes when using the module
> "radeon= " with an interlaced resolution.
>
> Easier to trigger by playing a video on Firefox, at least on kwin_x11.
> Wayland didn't exhibi= t the problem.
>
> Other display drivers, from different computers I have tried, didn't
> allow those interlaced resolutions all together. It seems they know
> there will be problems.


________________=
_______________________________
amd-gfx mailing list
amd-gfx@=
lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/am=
d-gfx







--000000000000d8311305bed70876-- --===============1930839491== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx --===============1930839491==--