amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Alberto Salvia Novella <es20490446e@gmail.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: alexander.deucher@amd.com, benh@kernel.crashing.org,
	linux-fbdev@vger.kernel.org,
	"Christian König" <christian.koenig@amd.com>,
	amd-gfx@lists.freedesktop.org
Subject: Re: Interlaced resolutions hang the desktop
Date: Tue, 30 Mar 2021 17:37:18 +0200	[thread overview]
Message-ID: <CAHJvkbsMY689cK3uq_O+i6jiqgLmSAUcrD43oHxpSsVwyhJ1Mg@mail.gmail.com> (raw)
In-Reply-To: <909002f5-691c-1cbb-1e44-a99217be8791@gmail.com>


[-- 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

  reply	other threads:[~2021-03-30 16:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  8:04 Interlaced resolutions hang the desktop Alberto Salvia Novella
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 [this message]
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-04-01 15:13                                     ` Alberto Salvia Novella

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHJvkbsMY689cK3uq_O+i6jiqgLmSAUcrD43oHxpSsVwyhJ1Mg@mail.gmail.com \
    --to=es20490446e@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=benh@kernel.crashing.org \
    --cc=christian.koenig@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).