Tj <tj.iam...@proton.me> (2024-07-13): > After reverting the recent sysfb commits: > > linux$ git l -n 15 > e932a4281dfd4 2024-07-13 17:27:49 +0100 N Tj Revert "firmware/sysfb: Set > firmware-framebuffer parent device" > c16bbb2e6863d 2024-07-13 17:27:49 +0100 N Tj Revert "firmware/sysfb: Create > firmware device only for enabled PCI devices" > a0e9d42816f8b 2024-07-13 17:27:49 +0100 N Tj Revert "firmware/sysfb: Update > screen_info for relocated EFI framebuffers" > ccadd360898d6 2024-07-13 17:27:48 +0100 N Tj Revert "firmware/sysfb: fix an > error code in sysfb_init()" > 10b1da91d6e42 2024-07-13 17:27:48 +0100 N Tj Revert "firmware: sysfb: Fix > reference count of sysfb parent device" > 4b3921872d1e1 2024-07-12 09:20:11 +0100 N Tj defconfig: x86 debian+tj clang > 02b5bfe1d3d5a 2024-07-12 09:20:11 +0100 N Tj defconfigs: add x86 > debian+tj_defconfig > 137efe9707741 2024-07-12 09:20:11 +0100 N Tj ath: add module_param > country_default for regulatory domain control > 8f630feb117a2 2024-07-12 09:20:11 +0100 N Tj cfg80211: suppress regdom > warning when phy not ready > 0ebc0f862b706 2024-07-12 09:20:10 +0100 N Tj debian: call > linux-update-symlinks from postinst > 4e2330e67f16f 2024-07-12 09:20:10 +0100 N Tj debian: no -dbg package using > KDEB_NO_DBG=1 > 45970aeccdb2a 2024-07-12 09:20:10 +0100 N Tj firmware: report each loaded > firmware file > 28fdf45184830 2024-07-11 12:51:24 +0200 N Greg Kroah-Hartman Linux 6.9.9 > > This confirms those commits are the cause of the issue; here we have > the same successful result as with v6.8.12
With my d-i hat: thanks for the awesome investigative work! (And for forwarding this to the LKML.) While my usual QEMU-based testing wasn't directly impacted by it, I've just hit this issue in a different environment, and it's nice to know something's already in the works! Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
