popcornmix

@vanfanel can you give this [test firmware](https://drive.google.com/uc?id=1VV_FhKXwA3HGskixkDaI7rMlNbMVQ2vt&export=download) a try? I think the issue is when arm throttles (due to high temperature) it was incorrectly reducing core frequency below that required...

Can you report output of `vcgencmd version` when using the test firmware? Can you confirm that display is fine when you have `throttled=0x0` or `throttled=0x80008`, but occurs when any addional...

This is very surprising, as I can reproduce your description easily (you can even set `temp_limit=65` to make it happen more quickly). With default firmware if I'm in a 4kp60...

Okay, it's ``` hdmi_group=2 hdmi_mode=39 # 1360x768 60Hz ``` that stops it working. If you remove that I suspect the issue will be resolved. Note that `hdmi_mode`/`hdmi_group` (and pretty much...

It does seem there are two similar issues here. The first involves core_freq being set too low when throttling. That is easy to reproduce. Use a high clock rate hdmi...

@JamesH65 it's 1360x768, and the display is fine up until the first throttle, so I don't think that thread is relevant.

@vanfanel can you try this [test firmware](https://drive.google.com/uc?id=10zOGA1phaAtMPV2xAezyTISAggKNONgk&export=download)

Fix should be in latest rpi-update firmware.

With a quick check it compiled and booted okay. The unbind/bin pair worked as expected. Hotplug/unplug also okay. I'll run with it and keep an eye on anything unexpected.

fkms works, but triggers a WARN: http://sprunge.us/4beqb2 Not surprising as we have no `vc4->hvs` in this mode. There's numerous ways we could hide this (downstream). e.g. ``` --- a/drivers/gpu/drm/vc4/vc4_hvs.c +++...