Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #82976 > unrolled thread

Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl Tj <tj.iam.tj@proton.me> - 2024-07-13 19:10 +0200
    Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl Cyril Brulebois <kibi@debian.org> - 2024-07-15 01:20 +0200

#82976 — Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

Package: linux-image-6.9.7+debian+tj
Followup-For: Bug #1075713
X-Debbugs-Cc: tj.iam.tj@proton.me

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

~ # uname -r; grep fbdev /var/log/Xorg.0.log
6.9.9+debian+tj
[    18.029] (==) Matched fbdev as autoconfigured driver 2
[    18.029] (II) LoadModule: "fbdev"
[    18.029] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    18.030] (II) Module fbdev: vendor="X.Org Foundation"
[    18.030] (II) FBDEV: driver for framebuffer: fbdev
[    18.063] fbdev trace: FBDevPciProbe()
[    18.063] (II) Loading sub module "fbdevhw"
[    18.063] (II) LoadModule: "fbdevhw"
[    18.063] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    18.063] (II) Module fbdevhw: vendor="X.Org Foundation"
[    18.063] fbdev trace: FBDevPciProbe() return
[    18.063] (WW) Falling back to old probe method for fbdev
[    18.063] fbdev trace: FBDevProbe()
[    18.063] (II) Loading sub module "fbdevhw"
[    18.063] (II) LoadModule: "fbdevhw"
[    18.063] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    18.063] (II) Module fbdevhw: vendor="X.Org Foundation"
[    18.063] fbdev: FBDevProbe() for() numDevSection=0
[    18.063] fbdev: FBDevProbe() isPci0 isISA=0
[    18.063] fbdev: FBDevProbe() calling fbdevHWProbe(NULL, '(null)', NULL)
[    18.063] (II) fbdev_open(scrnIndex=-1, dev=(null), namep=(nil))
[    18.063] (II) fbdev_open() using dev from env FRAMEBUFFER=(null)
[    18.063] (II) fbdev_open() using default dev=/dev/fb0
[    18.063] (II) fbdev_open() sysfs_path=/sys/class/graphics/fb0
[    18.063] (II) fbdev_open() buf=../../devices/platform/vesa-framebuffer.0/graphics/fb0
[    18.063] (II) fbdev_open() returning file descriptor 11
[    18.063] fbdev trace: FBDevProbe() fbdevHWProbe()
[    18.063] fbdev trace: FBDevProbe() else xf86ClaimFbSlot()
[    18.063] fbdev trace: FBDevProbe() return
[    18.063] (II) UnloadModule: "fbdev"
[    18.063] (II) UnloadSubModule: "fbdevhw"
[    18.063] fbdev: PreInit 0
[    18.063] (II) FBDEV(0): fbdev_open(scrnIndex=0, dev=(null), namep=(nil))
[    18.063] (II) FBDEV(0): fbdev_open() using dev from env FRAMEBUFFER=(null)
[    18.063] (II) FBDEV(0): fbdev_open() using default dev=/dev/fb0
[    18.063] (II) FBDEV(0): fbdev_open() sysfs_path=/sys/class/graphics/fb0
[    18.063] (II) FBDEV(0): fbdev_open() buf=../../devices/platform/vesa-framebuffer.0/graphics/fb0
[    18.063] (II) FBDEV(0): fbdev_open() returning file descriptor 12

[toc] | [next] | [standalone]

#82991

[Multipart message — attachments visible in raw view] — view raw

Tj <tj.iam.tj@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 (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web