Bug 216011 - Commit fbdev: vesafb: Cleanup fb_info in .fb_destroy rather than .remove broke my boot
Summary: Commit fbdev: vesafb: Cleanup fb_info in .fb_destroy rather than .remove brok...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Console/Framebuffers (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: James Simmons
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-21 11:42 UTC by Adrian Bassett
Modified: 2022-05-21 13:26 UTC (History)
0 users

See Also:
Kernel Version: 5.17.9
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description Adrian Bassett 2022-05-21 11:42:09 UTC
Upgrading from linux kernel 5.17.8 to 5.17.9 on a self-configured/self-compiled unaltered upstream kernel led to my amd64 system no longer booting.

The last thing I saw on my screen was:

'fb0: switching to i915drmfb from VESA FGA'

However, booting from a distribution kernel, it was not difficult to determine that that succeeded because it was setting both CONFIG_SYSFB_SIMPLEFB and CONFIG_DRM_SIMPLEDRM, neither of which were present in my failing config:  adding them fixed the problem.

I am filing this in case there is either a/ a bug in the changed 5.17.9 code;  or b/ the changes there have exposed a bug elsewhere, possibly in the fb infrastructure as a whole. or else in a particular fb driver.

Of course, it might be that CONFIG_SYSFB_SIMPLEFB and CONFIG_DRM_SIMPLEDRM ought generally to be set.  However, that was not previously necessary in my case.

Note You need to log in before you can comment on or make changes to this bug.