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 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 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 0000:00:0f.0: [drm] Register MMIO at 0x0x000000003d000000 
size is 4096 kiB
[    9.173985] vmwgfx 0000:00:0f.0: [drm] VRAM at 0x0000000070000000 size is 
131072 kiB
[    9.173989] vmwgfx 0000:00:0f.0: [drm] Running on SVGA version 3.
[    9.173992] vmwgfx 0000: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 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.173995] vmwgfx 0000:00:0f.0: [drm] DMA map mode: Caching DMA mappings.
[    9.174030] vmwgfx 0000:00:0f.0: [drm] Legacy memory limits: VRAM = 4096 kB, 
FIFO = 256 kB, surface = 524288 kB
[    9.174031] vmwgfx 0000:00:0f.0: [drm] MOB limits: max mob size = 262144 kB, 
max mob pages = 196608
[    9.174032] vmwgfx 0000:00:0f.0: [drm] Maximum display memory size is 262144 
kiB
[    9.176279] vmwgfx 0000:00:0f.0: [drm] No GMR memory available. Graphics 
memory resources are very limited.
[    9.176967] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[    9.177214] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[    9.177218] vmwgfx 0000: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 0000:00:0f.0 on 
minor 0

and /proc/iomem:

50000000-7fffffff : PCI Bus 0000:00
  70000000-77ffffff : 0000:00:0f.0
    70000000-77ffffff : 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:
   lo        no wireless extensions.
   
   ens160    no wireless extensions.
  MachineType: VMware, Inc. VMware20,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   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:sku0000000000000001:
  dmi.product.family: VMware
  dmi.product.name: VMware20,1
  dmi.product.sku: 0000000000000001
  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

Reply via email to