Control: tags -1 + moreinfo

Hi Klaus,

On Sat, May 09, 2026 at 11:51:17PM +0200, Klaus Singvogel wrote:
> Package: linux-image-amd64
> Version: 6.12.86-1
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
>      I upgraded my system from Debian Bookworm to Debian Trixie three days 
> ago.
>      My system uses an AMD Ryzen 7 5700G with integrated Radeon Graphics and
>      two identical monitors, one connected via HDMI and one via DisplayPort.
> 
>      I tested with kernel versions 6.12.85-1 and 6.12.86-1 on Trixie. The 
> issue
>      occurs with both kernels.
>      The problem was not present on Debian Bookworm.
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
>      I started video playback on the HDMI-connected monitor using VLC and
>      Firefox (YouTube).
> 
>      Moving the video window from the HDMI monitor to the DisplayPort monitor
>      stops the problem. The issue does not occur on the DisplayPort-connected
>      monitor.
> 
>    * What was the outcome of this action?
> 
>      During video playback on the HDMI monitor, the screen repeatedly turns
>      black for about 4–6 seconds, then becomes visible again for 4–6 seconds,
>      and continues cycling like this.
> 
>    * What outcome did you expect instead?
> 
>      Video playback should work normally on both monitors without the HDMI
>      monitor turning black.

Sorry to hear about your regression. So since you seem to have an easy
"reproducer" might you be able to bisect the problem? In this case
since some major versions are involved it might be worth first trying
to narrow the range a bit, by fetching kernel images built for Debian
from the snaphots service where it is bumped to major upstream
version. Then once you have arange from a 6.n to a 6.m version where
things regress, to bisect it.

Additionally it would be great if you can confirm if the problem still
persissts in 7.0.4-1 to see if current upstream is still affected.
Additionally please provide full kernel logs for such  boot up to when
the problem is triggered.

Regards,
Salvatore

Reply via email to