From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Alberto Salvia Novella" <es20490446e@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Cc: alexander.deucher@amd.com, benh@kernel.crashing.org,
linux-fbdev@vger.kernel.org, amd-gfx@lists.freedesktop.org
Subject: Re: Interlaced resolutions hang the desktop
Date: Tue, 30 Mar 2021 15:41:31 +0200 [thread overview]
Message-ID: <909002f5-691c-1cbb-1e44-a99217be8791@gmail.com> (raw)
In-Reply-To: <CAHJvkbuu5WB=QTu0EUgSGcoK6KMbP2j8NA0o+XTdtkwadNpsxg@mail.gmail.com>
[-- 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
next prev parent reply other threads:[~2021-03-30 13:41 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 [this message]
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
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=909002f5-691c-1cbb-1e44-a99217be8791@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=benh@kernel.crashing.org \
--cc=christian.koenig@amd.com \
--cc=es20490446e@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).