popcornmix

I have a look, but not seen anything obvious. Increasing the timeout to 10s doesn't help. `HDMI_SCHEDULER_CONTROL=0xcb029` so we've requested hdmi mode but it's not reported as being active. aside:...

@z0rti adding `video=HDMI-A-1:D` to end of /boot/cmdline.txt might provide a workaround for this issue (while we continue to look into it).

@mripard before the failure (from /sys/kernel/debug/clk/clk_summary): `fw-clk-pixel 1 1 0 148500000 0 0 50000 Y` ``` $ vcgencmd measure_clock pixel frequency(29)=148500000 ``` and after: `fw-clk-pixel 0 0 0 148500000 0...

There are no logged error messages before the WARN. e.g. http://sprunge.us/HmP3nh I just tried unplugging. Waiting a few minutes. Replugging and it failed in the same way: http://sprunge.us/TOxFuc

With all drm debug enabled: http://sprunge.us/TpeHh4

@mripard did you try unplugging hdmi cable? (and replugging ten seconds later). That reliably caused it. Not every time, but more often than not. My monitor didn't provoke it on...

Just tried at work (so different pi/sdcard and monitor), Failed on second replug. I'm booting to console (no X). [config.txt](http://sprunge.us/uMWXLO) [cmdline.txt](http://sprunge.us/DaDEj4) ``` pi@b3plus:~ $ uname -a Linux b3plus 5.15.32-v7+ #1539...

I've tested an upstream kernel (5.18-rc6) and couldn't reproduce this. The comparable downstream kernel did have this issue, so I may be able to bisect it.

> Did you find any temporary workaround for this bugs ? Can you try adding `video=HDMI-A-1:D` to end of /boot/cmdline.txt (on same line). I think that will avoid the issue.

You can add the overscan settings back in. Boot without the change and check /proc/cmdline, and then use that with `:D` added. e.g. ``` video=HDMI-A-1:3840x2160M@60,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48:D ```