This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1953671

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
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/1953671

Title:
  5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro
  per:

  https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech-
  preview-now-available.html

  I am successfully using the 5.14 kernel series (currently
  5.14.21-051421-generic) but note this is now EOL.

  However whenever I try to upgrade to either the 5.15 or 5.16 series my
  VM hangs at boot time after:

  EFI stub: Booting Linux Kernel...
  EFI stub: EFI_RNG_PROTOCOL unavailable
  EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
  EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region
  EFI stub: Using DIB from configuration table
  EFI stub: Exiting boot services...

  I see the same "hang" for both 5.15.7 and 5.16-rc4.

  FYI this has also been reported by others who note that the problem
  appears to be specific to Ubuntu:

  https://communities.vmware.com/t5/Fusion-for-Apple-Silicon-
  Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362

  Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't
  provide the output from:

  cat /proc/version

  However I attach the output from lspci.

  Please let me know what other information I can provide to help
  diagnose this issue.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+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