* Interlaced resolutions hang the desktop
@ 2021-03-30 8:04 Alberto Salvia Novella
2021-03-30 8:15 ` Christian König
0 siblings, 1 reply; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-30 8:04 UTC (permalink / raw)
To: amd-gfx, linux-fbdev, alexander.deucher, christian.koenig, benh
[-- Attachment #1.1: Type: text/plain, Size: 376 bytes --]
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 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.
[-- Attachment #1.2: Type: text/html, Size: 483 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-30 8:04 Interlaced resolutions hang the desktop Alberto Salvia Novella
@ 2021-03-30 8:15 ` Christian König
0 siblings, 0 replies; 24+ messages in thread
From: Christian König @ 2021-03-30 8:15 UTC (permalink / raw)
To: Alberto Salvia Novella, amd-gfx, linux-fbdev, alexander.deucher, benh
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 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.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
@ 2021-03-30 8:15 ` Christian König
0 siblings, 0 replies; 24+ messages in thread
From: Christian König @ 2021-03-30 8:15 UTC (permalink / raw)
To: Alberto Salvia Novella, amd-gfx, linux-fbdev, alexander.deucher, benh
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 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 list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-30 8:15 ` Christian König
(?)
@ 2021-03-30 9:07 ` Alberto Salvia Novella
2021-03-30 13:41 ` Christian König
-1 siblings, 1 reply; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-30 9:07 UTC (permalink / raw)
To: Christian König; +Cc: alexander.deucher, benh, linux-fbdev, amd-gfx
[-- Attachment #1.1: Type: text/plain, Size: 967 bytes --]
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önig <christian.koenig@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 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.
>
>
[-- Attachment #1.2: Type: text/html, Size: 1397 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-30 9:07 ` Alberto Salvia Novella
@ 2021-03-30 13:41 ` Christian König
2021-03-30 15:37 ` Alberto Salvia Novella
0 siblings, 1 reply; 24+ messages in thread
From: Christian König @ 2021-03-30 13:41 UTC (permalink / raw)
To: Alberto Salvia Novella, Christian König
Cc: alexander.deucher, benh, linux-fbdev, amd-gfx
[-- Attachment #1.1: Type: text/plain, Size: 1719 bytes --]
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önig
> <christian.koenig@amd.com <mailto:christian.koenig@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 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 list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
[-- Attachment #1.2: Type: text/html, Size: 3273 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-30 13:41 ` Christian König
@ 2021-03-30 15:37 ` Alberto Salvia Novella
2021-03-30 16:08 ` Alex Deucher
2021-03-30 16:26 ` Christian König
0 siblings, 2 replies; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-30 15:37 UTC (permalink / raw)
To: Christian König
Cc: alexander.deucher, benh, linux-fbdev, Christian König, amd-gfx
[-- Attachment #1.1: Type: text/plain, Size: 2690 bytes --]
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
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önig <
ckoenig.leichtzumerken@gmail.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önig <christian.koenig@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 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.freedesktop.org/mailman/listinfo/amd-gfx
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 4525 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-30 15:37 ` Alberto Salvia Novella
@ 2021-03-30 16:08 ` Alex Deucher
2021-03-30 16:26 ` Christian König
1 sibling, 0 replies; 24+ messages in thread
From: Alex Deucher @ 2021-03-30 16:08 UTC (permalink / raw)
To: Alberto Salvia Novella
Cc: Christian König, Deucher, Alexander, Benjamin Herrenschmidt,
open list:EFIFB FRAMEBUFFER DRIVER, Christian König,
amd-gfx list
On Tue, Mar 30, 2021 at 12:06 PM Alberto Salvia Novella
<es20490446e@gmail.com> wrote:
>
> 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
> 1920x1080i 60.00*+ 50.00 59.94
> 1920x1080 24.00 23.98
> 1280x720 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.
The supported display modes are dictated by the monitor. Do you still
have problems with progressive modes? I'd hate to disable interlaced
modes if they are working fine for others.
Alex
>
> On Tue, 30 Mar 2021 at 15:41, Christian König <ckoenig.leichtzumerken@gmail.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önig <christian.koenig@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 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 list
>> amd-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>
>>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
@ 2021-03-30 16:08 ` Alex Deucher
0 siblings, 0 replies; 24+ messages in thread
From: Alex Deucher @ 2021-03-30 16:08 UTC (permalink / raw)
To: Alberto Salvia Novella
Cc: open list:EFIFB FRAMEBUFFER DRIVER, Christian König,
amd-gfx list, Benjamin Herrenschmidt, Deucher, Alexander,
Christian König
On Tue, Mar 30, 2021 at 12:06 PM Alberto Salvia Novella
<es20490446e@gmail.com> wrote:
>
> 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
> 1920x1080i 60.00*+ 50.00 59.94
> 1920x1080 24.00 23.98
> 1280x720 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.
The supported display modes are dictated by the monitor. Do you still
have problems with progressive modes? I'd hate to disable interlaced
modes if they are working fine for others.
Alex
>
> On Tue, 30 Mar 2021 at 15:41, Christian König <ckoenig.leichtzumerken@gmail.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önig <christian.koenig@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 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 list
>> amd-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>
>>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-30 15:37 ` Alberto Salvia Novella
2021-03-30 16:08 ` Alex Deucher
@ 2021-03-30 16:26 ` Christian König
2021-03-30 20:59 ` Alberto Salvia Novella
1 sibling, 1 reply; 24+ messages in thread
From: Christian König @ 2021-03-30 16:26 UTC (permalink / raw)
To: Alberto Salvia Novella, Christian König
Cc: alexander.deucher, benh, linux-fbdev, amd-gfx
[-- Attachment #1.1: Type: text/plain, Size: 3861 bytes --]
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 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
> 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önig
> <ckoenig.leichtzumerken@gmail.com
> <mailto:ckoenig.leichtzumerken@gmail.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önig
>> <christian.koenig@amd.com <mailto:christian.koenig@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 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 list
>> amd-gfx@lists.freedesktop.org <mailto:amd-gfx@lists.freedesktop.org>
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C71c42210b976438bfbb908d8f391bb3f%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527154536688236%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jfWL5eoMUhK5phoM1Xs6Nv7SLsKCst7wWwq5URYNazk%3D&reserved=0>
>
[-- Attachment #1.2: Type: text/html, Size: 7226 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-30 16:26 ` Christian König
@ 2021-03-30 20:59 ` Alberto Salvia Novella
2021-03-31 6:44 ` Christian König
0 siblings, 1 reply; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-30 20:59 UTC (permalink / raw)
To: Christian König
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 3863 bytes --]
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önig <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 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
> 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önig <
> ckoenig.leichtzumerken@gmail.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önig <christian.koenig@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 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.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C71c42210b976438bfbb908d8f391bb3f%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527154536688236%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jfWL5eoMUhK5phoM1Xs6Nv7SLsKCst7wWwq5URYNazk%3D&reserved=0>
>>
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 7075 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-30 20:59 ` Alberto Salvia Novella
@ 2021-03-31 6:44 ` Christian König
2021-03-31 7:21 ` Alberto Salvia Novella
0 siblings, 1 reply; 24+ messages in thread
From: Christian König @ 2021-03-31 6:44 UTC (permalink / raw)
To: Alberto Salvia Novella
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 4958 bytes --]
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önig
> <christian.koenig@amd.com <mailto: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 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
>> 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önig
>> <ckoenig.leichtzumerken@gmail.com
>> <mailto:ckoenig.leichtzumerken@gmail.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önig
>>> <christian.koenig@amd.com <mailto:christian.koenig@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 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 list
>>> amd-gfx@lists.freedesktop.org <mailto:amd-gfx@lists.freedesktop.org>
>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C24d157e6250d4979c5fc08d8f3beb949%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527347790767402%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=efPyW%2BUl4PhnDWqghsRmaE7DKAUYoylzMP529%2BWrHDU%3D&reserved=0>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 9825 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 6:44 ` Christian König
@ 2021-03-31 7:21 ` Alberto Salvia Novella
2021-03-31 7:48 ` Christian König
0 siblings, 1 reply; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-31 7:21 UTC (permalink / raw)
To: Christian König
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 4806 bytes --]
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önig <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önig <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 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
>> 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önig <
>> ckoenig.leichtzumerken@gmail.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önig <christian.koenig@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 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.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C24d157e6250d4979c5fc08d8f3beb949%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527347790767402%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=efPyW%2BUl4PhnDWqghsRmaE7DKAUYoylzMP529%2BWrHDU%3D&reserved=0>
>>>
>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 9796 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 7:21 ` Alberto Salvia Novella
@ 2021-03-31 7:48 ` Christian König
2021-03-31 8:05 ` Alberto Salvia Novella
0 siblings, 1 reply; 24+ messages in thread
From: Christian König @ 2021-03-31 7:48 UTC (permalink / raw)
To: Alberto Salvia Novella
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 6862 bytes --]
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.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 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önig
> <christian.koenig@amd.com <mailto: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önig
>> <christian.koenig@amd.com <mailto: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 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
>>> 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önig
>>> <ckoenig.leichtzumerken@gmail.com
>>> <mailto:ckoenig.leichtzumerken@gmail.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önig
>>>> <christian.koenig@amd.com
>>>> <mailto:christian.koenig@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 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 list
>>>> amd-gfx@lists.freedesktop.org <mailto:amd-gfx@lists.freedesktop.org>
>>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C9750c0b0074e4c7f68fd08d8f415aaae%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527721219552783%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=NAMuDs3cBxh0jEeqMF8z%2BvuR%2BogJdps7vNJvHGHZ%2FR0%3D&reserved=0>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 13970 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 7:48 ` Christian König
@ 2021-03-31 8:05 ` Alberto Salvia Novella
2021-03-31 8:09 ` Christian König
0 siblings, 1 reply; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-31 8:05 UTC (permalink / raw)
To: Christian König
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 6432 bytes --]
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 "radeonhd".
On Wed, 31 Mar 2021 at 09:48, Christian König <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.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 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önig <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önig <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 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
>>> 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önig <
>>> ckoenig.leichtzumerken@gmail.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önig <christian.koenig@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 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.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C9750c0b0074e4c7f68fd08d8f415aaae%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527721219552783%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=NAMuDs3cBxh0jEeqMF8z%2BvuR%2BogJdps7vNJvHGHZ%2FR0%3D&reserved=0>
>>>>
>>>>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 14020 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 8:05 ` Alberto Salvia Novella
@ 2021-03-31 8:09 ` Christian König
2021-03-31 14:33 ` Alberto Salvia Novella
0 siblings, 1 reply; 24+ messages in thread
From: Christian König @ 2021-03-31 8:09 UTC (permalink / raw)
To: Alberto Salvia Novella
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 8925 bytes --]
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 "radeonhd".
>
> On Wed, 31 Mar 2021 at 09:48, Christian König
> <christian.koenig@amd.com <mailto: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.wikipedia.org/wiki/Deinterlacing
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FDeinterlacing&data=04%7C01%7Cchristian.koenig%40amd.com%7Ccf4929c9c3024efb7c4608d8f41bc0d0%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527747331540923%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=7dTqbjDCQaDTGcXA3yt8jKzSnT%2BrqcdkMhukqyOGwg0%3D&reserved=0>
> 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önig
>> <christian.koenig@amd.com <mailto: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önig
>>> <christian.koenig@amd.com <mailto: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 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
>>>> 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önig
>>>> <ckoenig.leichtzumerken@gmail.com
>>>> <mailto:ckoenig.leichtzumerken@gmail.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önig
>>>>> <christian.koenig@amd.com
>>>>> <mailto:christian.koenig@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 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 list
>>>>> amd-gfx@lists.freedesktop.org <mailto:amd-gfx@lists.freedesktop.org>
>>>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7Ccf4929c9c3024efb7c4608d8f41bc0d0%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527747331550917%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5BcOM0IHbXdYbWjy1a7VQOFgbkFGoV0FMzbDmZe94l0%3D&reserved=0>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 18758 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 8:09 ` Christian König
@ 2021-03-31 14:33 ` Alberto Salvia Novella
2021-03-31 14:36 ` Christian König
0 siblings, 1 reply; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-31 14:33 UTC (permalink / raw)
To: Christian König
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 7681 bytes --]
- The computer still replies to *ping*.
- The *journal* shows no errors, but a few warnings
<https://bin.privacytools.io/?5a0bf22220398549#D8SPwPEh8A5BuKN6TkU78gAgEPgrUok4fCjcaucSEnyy>
.
- The *mouse* doesn't freeze.
On Wed, 31 Mar 2021 at 10:09, Christian König <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 "radeonhd".
>
> On Wed, 31 Mar 2021 at 09:48, Christian König <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.wikipedia.org/wiki/Deinterlacing
>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FDeinterlacing&data=04%7C01%7Cchristian.koenig%40amd.com%7Ccf4929c9c3024efb7c4608d8f41bc0d0%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527747331540923%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=7dTqbjDCQaDTGcXA3yt8jKzSnT%2BrqcdkMhukqyOGwg0%3D&reserved=0>
>> 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önig <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önig <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 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
>>>> 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önig <
>>>> ckoenig.leichtzumerken@gmail.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önig <
>>>>> christian.koenig@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 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.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7Ccf4929c9c3024efb7c4608d8f41bc0d0%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527747331550917%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5BcOM0IHbXdYbWjy1a7VQOFgbkFGoV0FMzbDmZe94l0%3D&reserved=0>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 18248 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 14:33 ` Alberto Salvia Novella
@ 2021-03-31 14:36 ` Christian König
2021-03-31 14:52 ` Alberto Salvia Novella
0 siblings, 1 reply; 24+ messages in thread
From: Christian König @ 2021-03-31 14:36 UTC (permalink / raw)
To: Alberto Salvia Novella
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 10730 bytes --]
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
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbin.privacytools.io%2F%3F5a0bf22220398549%23D8SPwPEh8A5BuKN6TkU78gAgEPgrUok4fCjcaucSEnyy&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411072897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1jQLb8pO7eJYTORNisjequdWSCoKPsrrv7y%2F4U%2BojLM%3D&reserved=0>.
> - The *mouse* doesn't freeze.
>
> On Wed, 31 Mar 2021 at 10:09, Christian König
> <christian.koenig@amd.com <mailto: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 "radeonhd".
>>
>> On Wed, 31 Mar 2021 at 09:48, Christian König
>> <christian.koenig@amd.com <mailto: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.wikipedia.org/wiki/Deinterlacing
>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FDeinterlacing&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411072897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UTefQjeEYVrJto%2FqBlna%2FQKihbJe2HQG%2BczlZViFPDY%3D&reserved=0>
>> 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önig
>>> <christian.koenig@amd.com <mailto: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önig
>>>> <christian.koenig@amd.com
>>>> <mailto: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 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
>>>>> 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önig
>>>>> <ckoenig.leichtzumerken@gmail.com
>>>>> <mailto:ckoenig.leichtzumerken@gmail.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önig
>>>>>> <christian.koenig@amd.com
>>>>>> <mailto:christian.koenig@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 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 list
>>>>>> amd-gfx@lists.freedesktop.org <mailto:amd-gfx@lists.freedesktop.org>
>>>>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411082891%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5HXXJnOGGnEYSV%2BY%2FyWu031sE4CxFTKS2QqcKvlhhPs%3D&reserved=0>
>>>>>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 24612 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 14:36 ` Christian König
@ 2021-03-31 14:52 ` Alberto Salvia Novella
2021-03-31 14:55 ` Christian König
0 siblings, 1 reply; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-31 14:52 UTC (permalink / raw)
To: Christian König
Cc: alexander.deucher, Christian König, linux-fbdev, amd-gfx, benh
[-- Attachment #1.1: Type: text/plain, Size: 8689 bytes --]
Output
<https://bin.privacytools.io/?0f3d7caa23b99655#CvUAikkFYSdQ9XixPHvBe7ebfaQ7nXcFVBhXAotYMPrG>
.
On Wed, 31 Mar 2021 at 16:36, Christian König <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 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
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbin.privacytools.io%2F%3F5a0bf22220398549%23D8SPwPEh8A5BuKN6TkU78gAgEPgrUok4fCjcaucSEnyy&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411072897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1jQLb8pO7eJYTORNisjequdWSCoKPsrrv7y%2F4U%2BojLM%3D&reserved=0>
> .
> - The *mouse* doesn't freeze.
>
> On Wed, 31 Mar 2021 at 10:09, Christian König <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 "radeonhd".
>>
>> On Wed, 31 Mar 2021 at 09:48, Christian König <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.wikipedia.org/wiki/Deinterlacing
>>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FDeinterlacing&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411072897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UTefQjeEYVrJto%2FqBlna%2FQKihbJe2HQG%2BczlZViFPDY%3D&reserved=0>
>>> 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önig <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önig <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 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
>>>>> 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önig <
>>>>> ckoenig.leichtzumerken@gmail.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önig <
>>>>>> christian.koenig@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 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.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411082891%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5HXXJnOGGnEYSV%2BY%2FyWu031sE4CxFTKS2QqcKvlhhPs%3D&reserved=0>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 23489 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 14:52 ` Alberto Salvia Novella
@ 2021-03-31 14:55 ` Christian König
2021-03-31 15:47 ` Alberto Salvia Novella
0 siblings, 1 reply; 24+ messages in thread
From: Christian König @ 2021-03-31 14:55 UTC (permalink / raw)
To: Alberto Salvia Novella, Christian König
Cc: alexander.deucher, benh, linux-fbdev, amd-gfx
[-- Attachment #1.1: Type: text/plain, Size: 12366 bytes --]
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
> <https://bin.privacytools.io/?0f3d7caa23b99655#CvUAikkFYSdQ9XixPHvBe7ebfaQ7nXcFVBhXAotYMPrG>.
>
> On Wed, 31 Mar 2021 at 16:36, Christian König
> <christian.koenig@amd.com <mailto: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 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
>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbin.privacytools.io%2F%3F5a0bf22220398549%23D8SPwPEh8A5BuKN6TkU78gAgEPgrUok4fCjcaucSEnyy&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411072897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1jQLb8pO7eJYTORNisjequdWSCoKPsrrv7y%2F4U%2BojLM%3D&reserved=0>.
>> - The *mouse* doesn't freeze.
>>
>> On Wed, 31 Mar 2021 at 10:09, Christian König
>> <christian.koenig@amd.com <mailto: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
>>> "radeonhd".
>>>
>>> On Wed, 31 Mar 2021 at 09:48, Christian König
>>> <christian.koenig@amd.com <mailto: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.wikipedia.org/wiki/Deinterlacing
>>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FDeinterlacing&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411072897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UTefQjeEYVrJto%2FqBlna%2FQKihbJe2HQG%2BczlZViFPDY%3D&reserved=0>
>>> 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önig
>>>> <christian.koenig@amd.com
>>>> <mailto: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önig
>>>>> <christian.koenig@amd.com
>>>>> <mailto: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 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
>>>>>> 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önig
>>>>>> <ckoenig.leichtzumerken@gmail.com
>>>>>> <mailto:ckoenig.leichtzumerken@gmail.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önig <christian.koenig@amd.com
>>>>>>> <mailto:christian.koenig@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 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 list
>>>>>>> amd-gfx@lists.freedesktop.org <mailto:amd-gfx@lists.freedesktop.org>
>>>>>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411082891%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5HXXJnOGGnEYSV%2BY%2FyWu031sE4CxFTKS2QqcKvlhhPs%3D&reserved=0>
>>>>>>
>>>>>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 31582 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 14:55 ` Christian König
@ 2021-03-31 15:47 ` Alberto Salvia Novella
2021-03-31 17:39 ` Christian König
0 siblings, 1 reply; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-03-31 15:47 UTC (permalink / raw)
To: Christian König
Cc: alexander.deucher, benh, linux-fbdev, Christian König, amd-gfx
[-- Attachment #1.1: Type: text/plain, Size: 9522 bytes --]
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önig <
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
> <https://bin.privacytools.io/?0f3d7caa23b99655#CvUAikkFYSdQ9XixPHvBe7ebfaQ7nXcFVBhXAotYMPrG>
> .
>
> On Wed, 31 Mar 2021 at 16:36, Christian König <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 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
>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbin.privacytools.io%2F%3F5a0bf22220398549%23D8SPwPEh8A5BuKN6TkU78gAgEPgrUok4fCjcaucSEnyy&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411072897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1jQLb8pO7eJYTORNisjequdWSCoKPsrrv7y%2F4U%2BojLM%3D&reserved=0>
>> .
>> - The *mouse* doesn't freeze.
>>
>> On Wed, 31 Mar 2021 at 10:09, Christian König <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 "radeonhd".
>>>
>>> On Wed, 31 Mar 2021 at 09:48, Christian König <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.wikipedia.org/wiki/Deinterlacing
>>>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FDeinterlacing&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411072897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UTefQjeEYVrJto%2FqBlna%2FQKihbJe2HQG%2BczlZViFPDY%3D&reserved=0>
>>>> 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önig <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önig <
>>>>> 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 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
>>>>>> 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önig <
>>>>>> ckoenig.leichtzumerken@gmail.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önig <
>>>>>>> christian.koenig@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 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.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C48392451d33d4b63e5f208d8f45204d7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637527980411082891%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5HXXJnOGGnEYSV%2BY%2FyWu031sE4CxFTKS2QqcKvlhhPs%3D&reserved=0>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 30723 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 15:47 ` Alberto Salvia Novella
@ 2021-03-31 17:39 ` Christian König
2021-03-31 18:01 ` Alex Deucher
0 siblings, 1 reply; 24+ messages in thread
From: Christian König @ 2021-03-31 17:39 UTC (permalink / raw)
To: Alberto Salvia Novella, Christian König
Cc: alexander.deucher, benh, linux-fbdev, amd-gfx
[-- Attachment #1.1: Type: text/plain, Size: 15150 bytes --]
Yeah, agree that must be some kind of bug in the upper layer of the stack.
Most likely some userspace component is not handling the specialties of
interlacing correctly (different vblank timing every other frame).
It probably only works on Intel and after restarting the display manager
by coincident.
Sorry, but as I said this is a use case which basically nobody is using
any more and because of this the different parts of the stack are not
tested well enough for this.
Christian.
Am 31.03.21 um 17:47 schrieb Alberto Salvia Novella:
> 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önig
> <ckoenig.leichtzumerken@gmail.com
> <mailto: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
>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbin.privacytools.io%2F%3F0f3d7caa23b99655%23CvUAikkFYSdQ9XixPHvBe7ebfaQ7nXcFVBhXAotYMPrG&data=04%7C01%7Cchristian.koenig%40amd.com%7C7640f7339c964ba77ef708d8f45c50fe%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637528024640576009%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1RIyUWLBE8srNTGyf4VujAABOKYB8xMowLUXhShn2u0%3D&reserved=0>.
>>
>> On Wed, 31 Mar 2021 at 16:36, Christian König
>> <christian.koenig@amd.com <mailto: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 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
>>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbin.privacytools.io%2F%3F5a0bf22220398549%23D8SPwPEh8A5BuKN6TkU78gAgEPgrUok4fCjcaucSEnyy&data=04%7C01%7Cchristian.koenig%40amd.com%7C7640f7339c964ba77ef708d8f45c50fe%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637528024640576009%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QFHXVQ9dHqxidVzjJ22S%2FxW%2FaWRuf4okzfoUZ0SlahM%3D&reserved=0>.
>>> - The *mouse* doesn't freeze.
>>>
>>> On Wed, 31 Mar 2021 at 10:09, Christian König
>>> <christian.koenig@amd.com <mailto: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 "radeonhd".
>>>>
>>>> On Wed, 31 Mar 2021 at 09:48, Christian König
>>>> <christian.koenig@amd.com
>>>> <mailto: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.wikipedia.org/wiki/Deinterlacing
>>>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FDeinterlacing&data=04%7C01%7Cchristian.koenig%40amd.com%7C7640f7339c964ba77ef708d8f45c50fe%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637528024640585999%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ooF4BCKR%2Bg605BO7bXh7IYvP3F9Q88vC%2BuM6RM%2BflE8%3D&reserved=0>
>>>> 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önig
>>>>> <christian.koenig@amd.com
>>>>> <mailto: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önig
>>>>>> <christian.koenig@amd.com
>>>>>> <mailto: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 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
>>>>>>> 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önig <ckoenig.leichtzumerken@gmail.com
>>>>>>> <mailto:ckoenig.leichtzumerken@gmail.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önig
>>>>>>>> <christian.koenig@amd.com
>>>>>>>> <mailto:christian.koenig@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 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 list
>>>>>>>> amd-gfx@lists.freedesktop.org <mailto:amd-gfx@lists.freedesktop.org>
>>>>>>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7Cchristian.koenig%40amd.com%7C7640f7339c964ba77ef708d8f45c50fe%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637528024640585999%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=y2RJRp4SEnJQ7qPYYJKnr0B4xRkYEZJcYY6sZ4B%2BQ5g%3D&reserved=0>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 39867 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 17:39 ` Christian König
@ 2021-03-31 18:01 ` Alex Deucher
0 siblings, 0 replies; 24+ messages in thread
From: Alex Deucher @ 2021-03-31 18:01 UTC (permalink / raw)
To: Christian König
Cc: Alberto Salvia Novella, Christian König, Deucher, Alexander,
Benjamin Herrenschmidt, open list:EFIFB FRAMEBUFFER DRIVER,
amd-gfx list
Does disabling pageflipping via the xorg.conf help?
Alex
On Wed, Mar 31, 2021 at 1:40 PM Christian König
<christian.koenig@amd.com> wrote:
>
> Yeah, agree that must be some kind of bug in the upper layer of the stack.
>
> Most likely some userspace component is not handling the specialties of interlacing correctly (different vblank timing every other frame).
>
> It probably only works on Intel and after restarting the display manager by coincident.
>
> Sorry, but as I said this is a use case which basically nobody is using any more and because of this the different parts of the stack are not tested well enough for this.
>
> Christian.
>
> Am 31.03.21 um 17:47 schrieb Alberto Salvia Novella:
>
> 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önig <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önig <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 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önig <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 "radeonhd".
>>>>
>>>> On Wed, 31 Mar 2021 at 09:48, Christian König <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.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 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önig <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önig <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 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
>>>>>>> 1920x1080i 60.00*+ 50.00 59.94
>>>>>>> 1920x1080 24.00 23.98
>>>>>>> 1280x720 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önig <ckoenig.leichtzumerken@gmail.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önig <christian.koenig@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 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 list
>>>>>>>> amd-gfx@lists.freedesktop.org
>>>>>>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
@ 2021-03-31 18:01 ` Alex Deucher
0 siblings, 0 replies; 24+ messages in thread
From: Alex Deucher @ 2021-03-31 18:01 UTC (permalink / raw)
To: Christian König
Cc: open list:EFIFB FRAMEBUFFER DRIVER, Christian König,
amd-gfx list, Deucher, Alexander, Benjamin Herrenschmidt,
Alberto Salvia Novella
Does disabling pageflipping via the xorg.conf help?
Alex
On Wed, Mar 31, 2021 at 1:40 PM Christian König
<christian.koenig@amd.com> wrote:
>
> Yeah, agree that must be some kind of bug in the upper layer of the stack.
>
> Most likely some userspace component is not handling the specialties of interlacing correctly (different vblank timing every other frame).
>
> It probably only works on Intel and after restarting the display manager by coincident.
>
> Sorry, but as I said this is a use case which basically nobody is using any more and because of this the different parts of the stack are not tested well enough for this.
>
> Christian.
>
> Am 31.03.21 um 17:47 schrieb Alberto Salvia Novella:
>
> 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önig <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önig <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 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önig <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 "radeonhd".
>>>>
>>>> On Wed, 31 Mar 2021 at 09:48, Christian König <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.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 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önig <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önig <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 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
>>>>>>> 1920x1080i 60.00*+ 50.00 59.94
>>>>>>> 1920x1080 24.00 23.98
>>>>>>> 1280x720 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önig <ckoenig.leichtzumerken@gmail.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önig <christian.koenig@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 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 list
>>>>>>>> amd-gfx@lists.freedesktop.org
>>>>>>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Interlaced resolutions hang the desktop
2021-03-31 18:01 ` Alex Deucher
(?)
@ 2021-04-01 15:13 ` Alberto Salvia Novella
-1 siblings, 0 replies; 24+ messages in thread
From: Alberto Salvia Novella @ 2021-04-01 15:13 UTC (permalink / raw)
To: Alex Deucher
Cc: open list:EFIFB FRAMEBUFFER DRIVER, Christian König,
amd-gfx list, Benjamin Herrenschmidt, Deucher, Alexander,
Christian König
[-- Attachment #1.1: Type: text/plain, Size: 9570 bytes --]
There's no "xorg.conf" on my system.
On Wed, 31 Mar 2021 at 20:01, Alex Deucher <alexdeucher@gmail.com> wrote:
> Does disabling pageflipping via the xorg.conf help?
>
> Alex
>
> On Wed, Mar 31, 2021 at 1:40 PM Christian König
> <christian.koenig@amd.com> wrote:
> >
> > Yeah, agree that must be some kind of bug in the upper layer of the
> stack.
> >
> > Most likely some userspace component is not handling the specialties of
> interlacing correctly (different vblank timing every other frame).
> >
> > It probably only works on Intel and after restarting the display manager
> by coincident.
> >
> > Sorry, but as I said this is a use case which basically nobody is using
> any more and because of this the different parts of the stack are not
> tested well enough for this.
> >
> > Christian.
> >
> > Am 31.03.21 um 17:47 schrieb Alberto Salvia Novella:
> >
> > 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önig <
> 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önig <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 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önig <
> 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 "radeonhd".
> >>>>
> >>>> On Wed, 31 Mar 2021 at 09:48, Christian König <
> 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.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 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önig <
> 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önig <
> 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
> 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
> >>>>>>> 1920x1080i 60.00*+ 50.00 59.94
> >>>>>>> 1920x1080 24.00 23.98
> >>>>>>> 1280x720 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önig <
> ckoenig.leichtzumerken@gmail.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önig <
> christian.koenig@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 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 list
> >>>>>>>> amd-gfx@lists.freedesktop.org
> >>>>>>>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
> > _______________________________________________
> > amd-gfx mailing list
> > amd-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>
[-- Attachment #1.2: Type: text/html, Size: 14645 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2021-04-01 15:26 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-30 8:04 Interlaced resolutions hang the desktop Alberto Salvia Novella
2021-03-30 8:15 ` Christian König
2021-03-30 8:15 ` Christian König
2021-03-30 9:07 ` Alberto Salvia Novella
2021-03-30 13:41 ` Christian König
2021-03-30 15:37 ` Alberto Salvia Novella
2021-03-30 16:08 ` Alex Deucher
2021-03-30 16:08 ` Alex Deucher
2021-03-30 16:26 ` Christian König
2021-03-30 20:59 ` Alberto Salvia Novella
2021-03-31 6:44 ` Christian König
2021-03-31 7:21 ` Alberto Salvia Novella
2021-03-31 7:48 ` Christian König
2021-03-31 8:05 ` Alberto Salvia Novella
2021-03-31 8:09 ` Christian König
2021-03-31 14:33 ` Alberto Salvia Novella
2021-03-31 14:36 ` Christian König
2021-03-31 14:52 ` Alberto Salvia Novella
2021-03-31 14:55 ` Christian König
2021-03-31 15:47 ` Alberto Salvia Novella
2021-03-31 17:39 ` Christian König
2021-03-31 18:01 ` Alex Deucher
2021-03-31 18:01 ` Alex Deucher
2021-04-01 15:13 ` Alberto Salvia Novella
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.