[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
Installed the released kernel now available from updates. All works as expected. The HWE 22.10 kernel also works in 22.04.2. The 22.04.2 ISO installer still has a 5.19.0-32 kernel, though. It exhibits the blank screen issue when choosing the "Ubuntu Server with HWE kernel" installer option. I suspect that issue will get fixed in 22.04.3, but this issue can be easily worked around. Thanks to all of the Ubuntu crew for delivering this fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2007001 [Impact] Numerous VMWare users have reported that vmwgfx cannot reserve the memory region for the graphics framebuffer, leading their VMs to have blank screens. They see the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has failed to release this memory region for vmwgfx to occupy. Most affected users are on aarch64, with the host being Apple silicon systems. [Fix] The regression was introduced by the below commit in 5.19.0-30-generic: commit 5e01376124309b4dbd30d413f43c0d9c2f60edea Author: Thomas Zimmermann Date: Mon Jul 18 09:23:18 2022 +0200 Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea This commit was part of a larger refactoring of the video subsystem, and requires the entire series to function correctly. You can review the whole series below: https://patchwork.freedesktop.org/series/106040/ The patch series also requires quite a few additional fixups to fix bugs introduced by the series, making the size about 15 commits in total. The contents of the series don't really fix any bugs, and their purpose is to refactor the code for future changes to the fbdev subsystem, and really aren't appropriate to be backported to a stable kernel series. "video/aperture: Disable and unregister sysfb devices via aperture helpers" seems to have been selected for -stable by mistake by its fixes: tag, and was pulled into upstream stable by a robot with little human review. The best course of action is to revert. No action needed for Lunar, as the entire series is present in that release. [Testcase] This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 devices, like modern Apple computers. Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on Apple silicon, and see if the display comes up or not. Affected users will see a blank screen. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test If you install the test kernel and reboot, you will be able to see the screen on your VM like normal. [Where problems could occur] This commit changes when the sysfb is disabled and memory region for the graphics framebuffer is released to the proper device driver. If a regression were to occur, then graphics drivers may fail to reserve the framebuffer memory, and fail to start, leaving users with a blank screen. There are no workarounds, other than booting a previous kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
Thanks Matthew. I was erring on the side of caution as it was easy for me to at least give that variant a whirl on my trusty Jammy VM. I'll definitely take your lead on the need for future testing. Looking forward to release next week. I'll update you on my experiences - but I suspect that it'll be a non-event. Should I assume that the -proposed kernel will be made available to both Kinetic and Jammy HWE? I maintain a tips/techniques document for VMWare Fusion users on Apple Silicon. This issue is highlighted along with a few work-arounds. If this is fixed in both releases I can test both and remove a lot of work-around discussions. Thanks, Paul -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2007001 [Impact] Numerous VMWare users have reported that vmwgfx cannot reserve the memory region for the graphics framebuffer, leading their VMs to have blank screens. They see the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has failed to release this memory region for vmwgfx to occupy. Most affected users are on aarch64, with the host being Apple silicon systems. [Fix] The regression was introduced by the below commit in 5.19.0-30-generic: commit 5e01376124309b4dbd30d413f43c0d9c2f60edea Author: Thomas Zimmermann Date: Mon Jul 18 09:23:18 2022 +0200 Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea This commit was part of a larger refactoring of the video subsystem, and requires the entire series to function correctly. You can review the whole series below: https://patchwork.freedesktop.org/series/106040/ The patch series also requires quite a few additional fixups to fix bugs introduced by the series, making the size about 15 commits in total. The contents of the series don't really fix any bugs, and their purpose is to refactor the code for future changes to the fbdev subsystem, and really aren't appropriate to be backported to a stable kernel series. "video/aperture: Disable and unregister sysfb devices via aperture helpers" seems to have been selected for -stable by mistake by its fixes: tag, and was pulled into upstream stable by a robot with little human review. The best course of action is to revert. No action needed for Lunar, as the entire series is present in that release. [Testcase] This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 devices, like modern Apple computers. Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on Apple silicon, and see if the display comes up or not. Affected users will see a blank screen. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test If you install the test kernel and reboot, you will be able to see the screen on your VM like normal. [Where problems could occur] This commit changes when the sysfb is disabled and memory region for the graphics framebuffer is released to the proper device driver. If a regression were to occur, then graphics drivers may fail to reserve the framebuffer memory, and fail to start, leaving users with a blank screen. There are no workarounds, other than booting a previous kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
Apologies for the typo - I meant the linux-nvidia-5.19/5.19.0-1014.14 kernel in -proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2007001 [Impact] Numerous VMWare users have reported that vmwgfx cannot reserve the memory region for the graphics framebuffer, leading their VMs to have blank screens. They see the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has failed to release this memory region for vmwgfx to occupy. Most affected users are on aarch64, with the host being Apple silicon systems. [Fix] The regression was introduced by the below commit in 5.19.0-30-generic: commit 5e01376124309b4dbd30d413f43c0d9c2f60edea Author: Thomas Zimmermann Date: Mon Jul 18 09:23:18 2022 +0200 Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea This commit was part of a larger refactoring of the video subsystem, and requires the entire series to function correctly. You can review the whole series below: https://patchwork.freedesktop.org/series/106040/ The patch series also requires quite a few additional fixups to fix bugs introduced by the series, making the size about 15 commits in total. The contents of the series don't really fix any bugs, and their purpose is to refactor the code for future changes to the fbdev subsystem, and really aren't appropriate to be backported to a stable kernel series. "video/aperture: Disable and unregister sysfb devices via aperture helpers" seems to have been selected for -stable by mistake by its fixes: tag, and was pulled into upstream stable by a robot with little human review. The best course of action is to revert. No action needed for Lunar, as the entire series is present in that release. [Testcase] This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 devices, like modern Apple computers. Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on Apple silicon, and see if the display comes up or not. Affected users will see a blank screen. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test If you install the test kernel and reboot, you will be able to see the screen on your VM like normal. [Where problems could occur] This commit changes when the sysfb is disabled and memory region for the graphics framebuffer is released to the proper device driver. If a regression were to occur, then graphics drivers may fail to reserve the framebuffer memory, and fail to start, leaving users with a blank screen. There are no workarounds, other than booting a previous kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
I can verify that the 5.10.0-1014 kernel in -proposed does boot on a VMware Fusion VM running Jammy aarch64, and that the console appears as expected. I'm hesitant to change the tag to verification-done-jammy since I don't have anything nVidia on arm64. I can do that if my testing meets what you're looking for. I've verified that the vmwgfx driver has claimed the fb memory: dmesg shows: [0.867225] vmwgfx :00:0f.0: [drm] Register MMIO at 0x0x3d00 size is 4096 kiB [0.867229] vmwgfx :00:0f.0: [drm] VRAM at 0x7000 size is 131072 kiB [0.867234] vmwgfx :00:0f.0: [drm] Running on SVGA version 3. [0.867237] vmwgfx :00:0f.0: [drm] Capabilities: cursor, cursor bypass, alpha cursor, pitchlock, irq mask, traces, comma nd buffers, command buffers 2, gbobject, dx, hp cmd queue, no bb restriction, cap2 register, [0.867241] vmwgfx :00:0f.0: [drm] Capabilities2: grow otable, intra surface copy, dx2, gb memsize 2, screendma reg, ota ble ptdepth2, non ms to ms stretchblt, cursor mob, mshint, cb max size 4mb, dx3, frame type, trace full fb, extra regs, lo stag ing, [0.867243] vmwgfx :00:0f.0: [drm] DMA map mode: Caching DMA mappings. [0.867279] vmwgfx :00:0f.0: [drm] Legacy memory limits: VRAM = 4096 kB, FIFO = 256 kB, surface = 524288 kB [0.867281] vmwgfx :00:0f.0: [drm] MOB limits: max mob size = 262144 kB, max mob pages = 196608 [0.867283] vmwgfx :00:0f.0: [drm] Maximum display memory size is 262144 kiB and cat /proc/iomem shows: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-77ff : vmwgfx probe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2007001 [Impact] Numerous VMWare users have reported that vmwgfx cannot reserve the memory region for the graphics framebuffer, leading their VMs to have blank screens. They see the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has failed to release this memory region for vmwgfx to occupy. Most affected users are on aarch64, with the host being Apple silicon systems. [Fix] The regression was introduced by the below commit in 5.19.0-30-generic: commit 5e01376124309b4dbd30d413f43c0d9c2f60edea Author: Thomas Zimmermann Date: Mon Jul 18 09:23:18 2022 +0200 Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea This commit was part of a larger refactoring of the video subsystem, and requires the entire series to function correctly. You can review the whole series below: https://patchwork.freedesktop.org/series/106040/ The patch series also requires quite a few additional fixups to fix bugs introduced by the series, making the size about 15 commits in total. The contents of the series don't really fix any bugs, and their purpose is to refactor the code for future changes to the fbdev subsystem, and really aren't appropriate to be backported to a stable kernel series. "video/aperture: Disable and unregister sysfb devices via aperture helpers" seems to have been selected for -stable by mistake by its fixes: tag, and was pulled into upstream stable by a robot with little human review. The best course of action is to revert. No action needed for Lunar, as the entire series is present in that release. [Testcase] This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 devices, like modern Apple computers. Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on Apple silicon, and see if the display comes up or not. Affected users will see a blank screen. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test If you install the test kernel and reboot, you will be able to see the screen on your VM like normal. [Where problems could occur] This commit changes when the sysfb is disabled and memory region for the graphics framebuffer is released to the proper device driver. If a regression were to occur, then graphics drivers may fail to reserve the framebuffer memory, and fail to start, leaving users with a blank screen. There are no workarounds, other than booti
[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display
Matthew, I installed the 5.19.0-44.45 kernel from -proposed, and the console now appears. It does seem to solve the problem. dmesg reports: [9.808628] vmwgfx :00:0f.0: [drm] Register MMIO at 0x0x3d00 size is 4096 kiB [9.808637] vmwgfx :00:0f.0: [drm] VRAM at 0x7000 size is 131072 kiB [9.808642] vmwgfx :00:0f.0: [drm] Running on SVGA version 3. [9.808644] vmwgfx :00:0f.0: [drm] Capabilities: cursor, cursor bypass, alpha cursor, pitchlock, irq mask, traces, c ommand buffers, command buffers 2, gbobject, dx, hp cmd queue, no bb restriction, cap2 register, [9.808647] vmwgfx :00:0f.0: [drm] Capabilities2: grow otable, intra surface copy, dx2, gb memsize 2, screendma reg, otable ptdepth2, non ms to ms stretchblt, cursor mob, mshint, cb max size 4mb, dx3, frame type, trace full fb, extra regs, lo staging, [9.808648] vmwgfx :00:0f.0: [drm] DMA map mode: Caching DMA mappings. [9.808693] vmwgfx :00:0f.0: [drm] Legacy memory limits: VRAM = 4096 kB, FIFO = 256 kB, surface = 524288 kB [9.808693] vmwgfx :00:0f.0: [drm] MOB limits: max mob size = 262144 kB, max mob pages = 196608 [9.808696] vmwgfx :00:0f.0: [drm] Maximum display memory size is 262144 kiB [9.818387] vmwgfx :00:0f.0: [drm] No GMR memory available. Graphics memory resources are very limited. [9.818514] vmwgfx :00:0f.0: [drm] Screen Target display unit initialized [9.818748] vmwgfx :00:0f.0: [drm] Using command buffers with DMA pool. [9.818753] vmwgfx :00:0f.0: [drm] Available shader model: Legacy. [9.819374] Console: switching to colour frame buffer device 128x48 [9.822461] [drm] Initialized vmwgfx 2.20.0 20211206 for :00:0f.0 on minor 0 and /proc/iomem reports 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-77ff : vmwgfx probe 7800-784f : PCI Bus :01 ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2007001 [Impact] Numerous VMWare users have reported that vmwgfx cannot reserve the memory region for the graphics framebuffer, leading their VMs to have blank screens. They see the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has failed to release this memory region for vmwgfx to occupy. Most affected users are on aarch64, with the host being Apple silicon systems. [Fix] The regression was introduced by the below commit in 5.19.0-30-generic: commit 5e01376124309b4dbd30d413f43c0d9c2f60edea Author: Thomas Zimmermann Date: Mon Jul 18 09:23:18 2022 +0200 Subject: video/aperture: Disable and unregister sysfb devices via aperture helpers Link: https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea This commit was part of a larger refactoring of the video subsystem, and requires the entire series to function correctly. You can review the whole series below: https://patchwork.freedesktop.org/series/106040/ The patch series also requires quite a few additional fixups to fix bugs introduced by the series, making the size about 15 commits in total. The contents of the series don't really fix any bugs, and their purpose is to refactor the code for future changes to the fbdev subsystem, and really aren't appropriate to be backported to a stable kernel series. "video/aperture: Disable and unregister sysfb devices via aperture helpers" seems to have been selected for -stable by mistake by its fixes: tag, and was pulled into upstream stable by a robot with little human review. The best course of action is to revert. No action needed for Lunar, as the entire series is present in that release. [Testcase] This bug affects users running Ubuntu in VMWare VMs, notably on aarch64 devices, like modern Apple computers. Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on Apple silicon, and see if the display comes up or not. Affected users will see a blank screen. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test If you install the test kernel and reboot, you will be able to see the screen on your VM like normal.
[Kernel-packages] [Bug 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
Whatever patch series is needed does seem to be included in Linus' 5.19 tree as the mainline kernel 5.19.17 (supposedly built from Linus' sources) does not have this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: dmi.product.family: VMware dmi.product.name: VMware20,1 dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
I'm not an Ubuntu kernel engineer, so I can't help identify the offending commit. What I do see is the following in dmesg: [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 0x7000-0x77ff 64bit pref] [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16 And a cat /proc/iomem shows this: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-702f : BOOTFB The kernel has refused to release BOOTFB, and that explains why vmwgfx could not obtain it. This did not happen in 5.19.0-29, and does not happen in mainline 6.1.12. Example from mainline kernel 6.1.12 dmesg (same system, only chose to boot from 6.1.2 kernel): [9.173979] vmwgfx :00:0f.0: [drm] Register MMIO at 0x0x3d00 size is 4096 kiB [9.173985] vmwgfx :00:0f.0: [drm] VRAM at 0x7000 size is 131072 kiB [9.173989] vmwgfx :00:0f.0: [drm] Running on SVGA version 3. [9.173992] vmwgfx :00:0f.0: [drm] Capabilities: cursor, cursor bypass, alpha cursor, pitchlock, irq mask, traces, command buffers, command buffers 2, gbobject, dx, hp cmd queue, no bb restriction, cap2 register, [9.173994] vmwgfx :00:0f.0: [drm] Capabilities2: grow otable, intra surface copy, dx2, gb memsize 2, screendma reg, otable ptdepth2, non ms to ms stretchblt, cursor mob, mshint, cb max size 4mb, dx3, frame type, trace full fb, extra regs, lo staging, [9.173995] vmwgfx :00:0f.0: [drm] DMA map mode: Caching DMA mappings. [9.174030] vmwgfx :00:0f.0: [drm] Legacy memory limits: VRAM = 4096 kB, FIFO = 256 kB, surface = 524288 kB [9.174031] vmwgfx :00:0f.0: [drm] MOB limits: max mob size = 262144 kB, max mob pages = 196608 [9.174032] vmwgfx :00:0f.0: [drm] Maximum display memory size is 262144 kiB [9.176279] vmwgfx :00:0f.0: [drm] No GMR memory available. Graphics memory resources are very limited. [9.176967] vmwgfx :00:0f.0: [drm] Screen Target display unit initialized [9.177214] vmwgfx :00:0f.0: [drm] Using command buffers with DMA pool. [9.177218] vmwgfx :00:0f.0: [drm] Available shader model: Legacy. [9.177749] Console: switching to colour frame buffer device 128x48 [9.181076] [drm] Initialized vmwgfx 2.20.0 20211206 for :00:0f.0 on minor 0 and /proc/iomem: 5000-7fff : PCI Bus :00 7000-77ff : :00:0f.0 7000-77ff : vmwgfx probe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
[Kernel-packages] [Bug 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
Kernel logging shows that the vmwgfx driver encounters an error when loading. The error indicates that a memory range could not be acquired by the driver. The error is eerily similar to https://bugzilla.kernel.org/show_bug.cgi?id=215678 which was fixed in kernel source in 5.19. The behavior seen in this kernel is a regression to past kernel version behavior. Is there anyone at Ubuntu that would care to look at this issue? It's been crickets for over a month. ** Bug watch added: Linux Kernel Bug Tracker #215678 https://bugzilla.kernel.org/show_bug.cgi?id=215678 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: dmi.product.family: VMware dmi.product.name: VMware20,1 dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
This same issue impacts Ubuntu 22.04.2 HWE 5.19.0-32 kernels on aarch64. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Confirmed Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: dmi.product.family: VMware dmi.product.name: VMware20,1 dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
** Summary changed: - Blank console display with aarch64 kernel 5.19.0-31 aarch64 + Blank console display with aarch64 kernel 5.19.0-31 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Confirmed Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: dmi.product.family: VMware dmi.product.name: VMware20,1 dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] [NEW] Blank console display with aarch64 kernel 5.19.0-31 aarch64
Public bug reported: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: dmi.product.family: VMware dmi.product.name: VMware20,1 dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug arm64 kinetic uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 aarch64 Status in linux package in Ubuntu: Confirmed Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: dmi.product.family: VMware dmi.product.name: VMware20,1 dmi.product.sku: 0001 dmi.product.version: 1 dmi.
