<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Yeah, agree that must be some kind of bug in the upper layer of the
stack.<br>
<br>
Most likely some userspace component is not handling the specialties
of interlacing correctly (different vblank timing every other
frame).<br>
<br>
It probably only works on Intel and after restarting the display
manager by coincident.<br>
<br>
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.<br>
<br>
Christian.<br>
<br>
<div class="moz-cite-prefix">Am 31.03.21 um 17:47 schrieb Alberto
Salvia Novella:<br>
</div>
<blockquote type="cite" cite="mid:CAHJvkbviwB3JLU84P+mb58rvxaKOahO+B9LPMw3n8nGKvTHAOg@mail.gmail.com">
<div dir="ltr">
<div>Restarting the <b>display manager</b> service works and,
more importantly, makes the bug no longer reproducible.</div>
<div><br>
</div>
<div>Restarting the <b>window manager</b> doesn't work.</div>
<div><br>
</div>
<div><b>Changing</b> display manager makes the bug still
reproducible.</div>
<div><br>
</div>
<div>Maybe this is due to xorg-server, isn't it?<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 31 Mar 2021 at 16:55,
Christian König <<a href="mailto:ckoenig.leichtzumerken@gmail.com" moz-do-not-send="true">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> Well the hardware is working fine as far as I can see.<br>
<br>
Can you try to kill the X server over SSH and see if you
then get some screen update?<br>
<br>
Regards,<br>
Christian.<br>
<br>
<div>Am 31.03.21 um 16:52 schrieb Alberto Salvia Novella:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><a href="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" originalsrc="https://bin.privacytools.io/?0f3d7caa23b99655#CvUAikkFYSdQ9XixPHvBe7ebfaQ7nXcFVBhXAotYMPrG" shash="yDeZVZqesFBDn0I/4GqshNG9z//CDCrITK0WOCyK3RfcYQ/OYiVw3SHzd3r/5G/u/v/JNnFiwuUF0TveQs9BZe4fEg8TfCQ3S2l+jY79sxrFswjFnPwf3cuzAaJfUdncsR3J3qPEHDmfib2ND+QQHgZkc2WkaqruRsFxUKL/xWg=" target="_blank" moz-do-not-send="true">Output</a>.<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 31 Mar 2021 at
16:36, Christian König <<a href="mailto:christian.koenig@amd.com" target="_blank" moz-do-not-send="true">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">
<div> Mhm strange.<br>
<br>
Can you get me the output of "sudo cat
/sys/kernel/debug/dri/0/radeon_fence_info" when the
problem happens?<br>
<br>
Thanks,<br>
Christian.<br>
<br>
<div>Am 31.03.21 um 16:33 schrieb Alberto Salvia
Novella:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>- The computer still replies to <b>ping</b>.</div>
<div>- The <b>journal</b> shows no errors, but
a few <a href="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" originalsrc="https://bin.privacytools.io/?5a0bf22220398549#D8SPwPEh8A5BuKN6TkU78gAgEPgrUok4fCjcaucSEnyy" shash="QA0oaQQlkknJNQGNDyrXgsnRzWRVHbDqR6neZke3RKVxQng4mP0U+n4vstYHKQWMk4MQOXAAwRzYNU0iuYZ3YeN8viebCS0EG/d4AVFJ8kYrFS/9WcYmSvjAeEWCWBVe07Y727GQ+PvWoP55PXWMy4knKbQTJUJ7UvKIkpNxvRQ=" target="_blank" moz-do-not-send="true">warnings</a>.</div>
<div>- The <b>mouse</b> doesn't freeze.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 31 Mar
2021 at 10:09, Christian König <<a href="mailto:christian.koenig@amd.com" target="_blank" moz-do-not-send="true">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">
<div> Can you access the system over the
network and see if there is anything in the
system log?<br>
<br>
It sounds like the display stack has
crashed, but when the sound keeps playing
the system is most likely still responsive
over network.<br>
<br>
Thanks,<br>
Christian.<br>
<br>
<div>Am 31.03.21 um 10:05 schrieb Alberto
Salvia Novella:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>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.</div>
<div><br>
</div>
<div>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.<br>
</div>
<div><br>
</div>
<div>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".</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On
Wed, 31 Mar 2021 at 09:48, Christian
König <<a href="mailto:christian.koenig@amd.com" target="_blank" moz-do-not-send="true">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">
<div> Correct, but a TV is intended
for videos only. That's why it
implements only the lower HDMI
standard.<br>
<br>
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.<br>
<br>
You could just add a progressive
1920x540@60 or 1920x1080@30 mode
manually and would have the same
effect with probably better quality.
See <a href="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" originalsrc="https://de.wikipedia.org/wiki/Deinterlacing" shash="vPWCLu2KWRiZKGLjr91+mJthFbsuRZuffiNZrJUahEonB8DvpCuvVPnW5U6/X/EAErqM9CJwmeogdrcOiDYGEJTckRS1iO2lm2VvXtaKceSG9UOpXzvn6apuZdU9gdl/Fcz337lWDp2YD3n8Kqt1ao2hYf29VJQVkKextOeHBV8=" target="_blank" moz-do-not-send="true">https://de.wikipedia.org/wiki/Deinterlacing</a>
for reference.<br>
<br>
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.<br>
<br>
Regards,<br>
Christian.<br>
<br>
<div>Am 31.03.21 um 09:21 schrieb
Alberto Salvia Novella:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>24fps is intended for video
only. Anything interactive at
24fps, as just moving the
mouse around, is extremely
choppy.</div>
<div><br>
</div>
<div>No way anyone would prefer
that over an interlaced
resolution or a lower
resolution. That is, by far,
the worst option.</div>
<div><br>
</div>
<div>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.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 31
Mar 2021 at 08:44, Christian
König <<a href="mailto:christian.koenig@amd.com" target="_blank" moz-do-not-send="true">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">
<div> Hi Alberto,<br>
<br>
well a frame rate of 24Hz is
perfectly reasonable for a
TV and desktop usage.<br>
<br>
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.<br>
<br>
Regards,<br>
Christian.<br>
<br>
<div>Am 30.03.21 um 22:59
schrieb Alberto Salvia
Novella:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>The frame-rate at
24Hz is extremely poor
for normal desktop
usage.<br>
</div>
<div><br>
</div>
<div>If the highest
resolution, aka 1080p,
uses that refresh rate
then the desktop will
default to that
frame-rate.</div>
<div><br>
</div>
<div>Other progressive
modes don't exhibit
any issue.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On
Tue, 30 Mar 2021 at
18:26, Christian König
<<a href="mailto:christian.koenig@amd.com" target="_blank" moz-do-not-send="true">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">
<div> Hi Alberto,<br>
<br>
<blockquote type="cite">I
think the driver
should only
support
resolutions that
are <b>progressive</b>,
but also at least
of <b>50Hz</b>.</blockquote>
<br>
Why do you think
so?, the 24Hz
resolution seems to
be the native one of
the display.<br>
<br>
Regards,<br>
Christian.<br>
<br>
<div>Am 30.03.21 um
17:37 schrieb
Alberto Salvia
Novella:<br>
</div>
<blockquote type="cite">
<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" target="_blank" moz-do-not-send="true">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" moz-do-not-send="true">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" moz-do-not-send="true">amd-gfx@lists.freedesktop.org</a>
<a href="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" originalsrc="https://lists.freedesktop.org/mailman/listinfo/amd-gfx" shash="Q99Ycc+B8WLq9g3/U3SbN3Av5gHfv/FvOGFS52+InPSpxBD2YuOXstri6eUeY7TD0w3/FRNhHLkDpuI0Hv69TD2vd71m52SGsNmHJhuc1wvTi7m+TuEvRasvpv9TK4JQZ9/LYFHCj2oXC7VomDL3g0K6ZsSPlqc1RSXzTQ2u3r8=" target="_blank" moz-do-not-send="true">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>