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 0000:00:0f.0: [drm] Register MMIO at 0x0x000000003d000000
size is 4096 kiB
[ 9.808637] vmwgfx 0000:00:0f.0: [drm] VRAM at 0x0000000070000000 size is
131072 kiB
[ 9.808642] vmwgfx 0000:00:0f.0: [drm] Running on SVGA version 3.
[ 9.808644] vmwgfx 0000: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 0000: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 0000:00:0f.0: [drm] DMA map mode: Caching DMA mappings.
[ 9.808693] vmwgfx 0000:00:0f.0: [drm] Legacy memory limits: VRAM = 4096 kB,
FIFO = 256 kB, surface = 524288 kB
[ 9.808693] vmwgfx 0000:00:0f.0: [drm] MOB limits: max mob size = 262144 kB,
max mob pages = 196608
[ 9.808696] vmwgfx 0000:00:0f.0: [drm] Maximum display memory size is 262144
kiB
[ 9.818387] vmwgfx 0000:00:0f.0: [drm] No GMR memory available. Graphics
memory resources are very limited.
[ 9.818514] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 9.818748] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 9.818753] vmwgfx 0000: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 0000:00:0f.0 on
minor 0
and /proc/iomem reports
50000000-7fffffff : PCI Bus 0000:00
70000000-77ffffff : 0000:00:0f.0
70000000-77ffffff : vmwgfx probe
78000000-784fffff : PCI Bus 0000: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 0000:00:0f.0: BAR 2: can't reserve [mem
0x70000000-0x77ffffff 64bit pref]
[ 11.135366] vmwgfx: probe of 0000:00:0f.0 failed with error -16
And a cat /proc/iomem shows this:
50000000-7fffffff : PCI Bus 0000:00
70000000-77ffffff : 0000:00:0f.0
70000000-702fffff : 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 <tzimmerm...@suse.de>
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
