Further investigation:
Affects:
1) 5.13.19 does not suffer from this bug
2) The Ubuntu 5.15 kernels, and mainline 5.16 and 5.17 kernels *do* suffer from this bug.
Also of note: this only occurs the *first* time KMS tries to come up on the panel, and *only* if there is not a second monitor plugged in. Having a second monitor plugged in at boot results in a successful boot, *plugging in* a second monitor after triggering this bug results in *both* displays working fine, and *removing* a second monitor leaves the laptop panel working.
It looks like maybe a bug has been introduced in framebuffer allocation?
Further investigation:
Affects:
1) 5.13.19 does not suffer from this bug
2) The Ubuntu 5.15 kernels, and mainline 5.16 and 5.17 kernels *do* suffer from this bug.
Also of note: this only occurs the *first* time KMS tries to come up on the panel, and *only* if there is not a second monitor plugged in. Having a second monitor plugged in at boot results in a successful boot, *plugging in* a second monitor after triggering this bug results in *both* displays working fine, and *removing* a second monitor leaves the laptop panel working.
It looks like maybe a bug has been introduced in framebuffer allocation?