From TFA:

> After looking at some logs we do end up with potentially bogus panel power sequencing delays, which may harm the LCD panel.

So sounds like it can cause some out of spec stuff at the analog level, which could plausibly result in damage, but also probably dependant on exactly what bogus values are sent in a particular case and how resilient a particular LCD is.

That it can damage the display is currently a hypothetical scenario. I don't think anyone has reported a broken panel. One of the i915 devs on the stable mailing list said:

> After looking at some logs we do end up with potentially bogus panel power sequencing delays, which may harm the LCD panel.

My framework laptop was affected by this. When I booted 5.19.12 my display was flickering like crazy. Rebooting with 5.19.11 corrected it. 6.0 is also fine.

[0] https://lore.kernel.org/all/YzwooNdMECzuI5+h@intel.com/

"Potentially" and "may" harm the actual display.

> After looking at some logs we do end up with potentially bogus panel power sequencing delays, which may harm the LCD panel.

https://lore.kernel.org/all/YzwooNdMECzuI5+h@intel.com/

I booted both of my Framework laptops on 5.19.12 and it didn’t break anything. I could type my LUKS password and still get into gdm fine. I still reverted back to 5.19.11 though.

No luck, I'm running 5.19.12, noticed flicker that looked like a bad LVDS cable. but it was wired because it happened while the laptop was not being moved. I would have not thought of a software issue as it was affecting the whole display. But most of the time the flicker would disappear, the display doesn't look to be damaged, as I ca use it normally when it's not flickering. Hopefully the revert will make the flicker disappear.

Well, I've got a Lenovo with an integrated Intel GPU and a discrete AMD one. I'm on 5.19.12 and I didn't notice anything, but still I can't conclude that maybe there isn't something wrong going on during boot that could cause damage. I'll look now for updates.