<div dir="ltr"><div>This is why I'm using interlaced:<br></div><div><br></div><div>$ <b>xrandr</b><br>Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192<br>DisplayPort-0 disconnected (normal left inverted right x axis y axis)<br>HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 16mm x 9mm<br> 1920x<b>1080i</b> 60.00*+ 50.00 59.94 <br> 1920x1080 <b>24.00</b> 23.98 <br> 1280x<b>720</b> 60.00 50.00 59.94 <br> 1024x768 75.03 70.07 60.00 <br> 832x624 74.55 <br> 800x600 72.19 75.00 60.32 56.25 <br> 720x576 50.00 <br> 720x576i 50.00 <br> 720x480 60.00 59.94 <br> 720x480i 60.00 59.94 <br> 640x480 75.00 72.81 66.67 60.00 59.94 <br> 720x400 70.08 <br>DVI-0 disconnected (normal left inverted right x axis y axis)</div><div><br></div><div>I think the driver should only support resolutions that are <b>progressive</b>, but also at least of <b>50Hz</b>.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 30 Mar 2021 at 15:41, Christian König <<a href="mailto:ckoenig.leichtzumerken@gmail.com">ckoenig.leichtzumerken@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Mhm, no idea why an interlaced resolution would cause a crash. Maybe
some miscalculation in the display code.<br>
<br>
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.<br>
<br>
See those resolutions only exists for backward compatibility with
analog hardware.<br>
<br>
I think we would just disable those modes instead of searching for
the bug.<br>
<br>
Regards,<br>
Christian.<br>
<br>
<div>Am 30.03.21 um 11:07 schrieb Alberto
Salvia Novella:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>I guessed so.</div>
<div><br>
</div>
<div>The GPU is a Radeon HD5870, and the screen is an old
Telefunken TV (TLFK22LEDPVR1).</div>
<div><br>
</div>
<div>Since my real display got into repair I used this TV
meanwhile, and to my surprise it froze the system.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, 30 Mar 2021 at 10:15,
Christian König <<a href="mailto:christian.koenig@amd.com" target="_blank">christian.koenig@amd.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
Alberto,<br>
<br>
well what hardware do you have?<br>
<br>
Interlaced resolutions are not used any more on modern
hardware, so they <br>
are not well tested.<br>
<br>
Regards,<br>
Christian.<br>
<br>
Am 30.03.21 um 10:04 schrieb Alberto Salvia Novella:<br>
> The entire desktop hangs after some minutes when using
the module <br>
> "radeon" with an interlaced resolution.<br>
><br>
> Easier to trigger by playing a video on Firefox, at least
on kwin_x11. <br>
> Wayland didn't exhibit the problem.<br>
><br>
> Other display drivers, from different computers I have
tried, didn't <br>
> allow those interlaced resolutions all together. It seems
they know <br>
> there will be problems.<br>
<br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
amd-gfx mailing list
<a href="mailto:amd-gfx@lists.freedesktop.org" target="_blank">amd-gfx@lists.freedesktop.org</a>
<a href="https://lists.freedesktop.org/mailman/listinfo/amd-gfx" target="_blank">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div>