[Kernel-packages] [Bug 2036273] Re: 5.15+ GCE Instances are unable to create fb0 with virt mon attached
Hi guys Is there an update here? Many thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2036273 Title: 5.15+ GCE Instances are unable to create fb0 with virt mon attached Status in linux-gcp package in Ubuntu: New Bug description: This is a public facing LP issue to address the content in Canonical's SF#00366439. Summary: Post 18.04 ( or 20.04 prior to moving to 5.15 ), efifb fails to stand up fb0. It is assigned, but fb0 is never created, nor are there any errors that I noted. Here is an example from a focal using linux-gcp --- 5.15.0-1041-gcp #49~20.04.1-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [0.925827] pci :00:05.0: BAR 0: assigned to efifb --- If you then install the generic HWE kernel and reboot, you can see that fb0 is successfully summoned: --- 5.15.0-83-generic #92~20.04.1-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [2.128815] pci :00:05.0: BAR 0: assigned to efifb [3.021819] efifb: probing for efifb [3.022511] efifb: framebuffer at 0xc000, using 6076k, total 6075k [3.023925] efifb: mode is 1920x1080x24, linelength=5760, pages=1 [3.025382] efifb: scrolling: redraw [3.026347] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0 --- and finally, using linux-gcp-lts on 20.04, it does work (as it's 5.4): --- 5.4.0-1112-gcp #121-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [0.834541] pci :00:05.0: BAR 0: assigned to efifb [1.057258] efifb: probing for efifb [1.058182] efifb: framebuffer at 0xc000, using 6076k, total 6075k [1.059210] efifb: mode is 1920x1080x24, linelength=5760, pages=1 [1.060203] efifb: scrolling: redraw [1.060722] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0 --- So some linux-gcp backport or config seems to be breaking this. Supplementary to this, the framebuffer can not be leveraged by X and throws a fatal error around the time shadow is loaded. This part is replicable on -generic, as well as on debian using gdm3/X, so this is likely an upstream problem. I tried disabling shadow with an X conf, but as it uses 24bppp, it forces it. For the scope of this LP, we need to figure out the -gcp specific breakage. I've reached out to google to see if we can get some contacts on the virt mon team to push the other aspect forward. Replication: Launch any ubuntu 20.04+ GCE instance with the "Display Device" option enabled. Expected Behavior: We should see the above output in dmesg and also observe /dev/fb0 being created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2036273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036273] Re: 5.15+ GCE Instances are unable to create fb0 with virt mon attached
Many thanks Kyler. Jawed, could you provide an update from Google's side? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2036273 Title: 5.15+ GCE Instances are unable to create fb0 with virt mon attached Status in linux-gcp package in Ubuntu: New Bug description: This is a public facing LP issue to address the content in Canonical's SF#00366439. Summary: Post 18.04 ( or 20.04 prior to moving to 5.15 ), efifb fails to stand up fb0. It is assigned, but fb0 is never created, nor are there any errors that I noted. Here is an example from a focal using linux-gcp --- 5.15.0-1041-gcp #49~20.04.1-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [0.925827] pci :00:05.0: BAR 0: assigned to efifb --- If you then install the generic HWE kernel and reboot, you can see that fb0 is successfully summoned: --- 5.15.0-83-generic #92~20.04.1-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [2.128815] pci :00:05.0: BAR 0: assigned to efifb [3.021819] efifb: probing for efifb [3.022511] efifb: framebuffer at 0xc000, using 6076k, total 6075k [3.023925] efifb: mode is 1920x1080x24, linelength=5760, pages=1 [3.025382] efifb: scrolling: redraw [3.026347] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0 --- and finally, using linux-gcp-lts on 20.04, it does work (as it's 5.4): --- 5.4.0-1112-gcp #121-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [0.834541] pci :00:05.0: BAR 0: assigned to efifb [1.057258] efifb: probing for efifb [1.058182] efifb: framebuffer at 0xc000, using 6076k, total 6075k [1.059210] efifb: mode is 1920x1080x24, linelength=5760, pages=1 [1.060203] efifb: scrolling: redraw [1.060722] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0 --- So some linux-gcp backport or config seems to be breaking this. Supplementary to this, the framebuffer can not be leveraged by X and throws a fatal error around the time shadow is loaded. This part is replicable on -generic, as well as on debian using gdm3/X, so this is likely an upstream problem. I tried disabling shadow with an X conf, but as it uses 24bppp, it forces it. For the scope of this LP, we need to figure out the -gcp specific breakage. I've reached out to google to see if we can get some contacts on the virt mon team to push the other aspect forward. Replication: Launch any ubuntu 20.04+ GCE instance with the "Display Device" option enabled. Expected Behavior: We should see the above output in dmesg and also observe /dev/fb0 being created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2036273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039732] Re: No graphic desktop environment on Google GCP instances
Jawed, can you confirm that somebody at Google will be taking a look at this? Many thanks, Pete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. [Other Info] * SF #00366439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
