Bug 1833346 - Kernel doesn't boot on qemu on aarch64
Summary: Kernel doesn't boot on qemu on aarch64
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: TRACKER-bugs-affecting-libguestfs
TreeView+ depends on / blocked
 
Reported: 2020-05-08 13:44 UTC by Richard W.M. Jones
Modified: 2020-05-11 11:49 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
build.log (2.33 MB, text/plain)
2020-05-08 13:45 UTC, Richard W.M. Jones
no flags Details
root.log (164.58 KB, text/plain)
2020-05-08 13:45 UTC, Richard W.M. Jones
no flags Details

Description Richard W.M. Jones 2020-05-08 13:44:23 UTC
Kernel doesn't boot on qemu, again.  This time on aarch64.

The full log is attached, but the failure happens just as UEFI
enters the kernel:

EFI stub: Exiting boot services and installing virtual address map...
VirtioRngExitBoot: Context=0x7E567818
SetUefiImageMemoryAttributes - 0x000000007F600000 - 0x0000000000040000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x000000007C290000 - 0x0000000000040000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x000000007C240000 - 0x0000000000040000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x000000007C1F0000 - 0x0000000000040000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x000000007C150000 - 0x0000000000040000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x000000007C060000 - 0x0000000000040000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x000000007BF10000 - 0x0000000000040000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x000000007BE70000 - 0x0000000000040000 (0x0000000000000008)
[crashes here with no other message]

kernel-core 5.7.0-0.rc4.20200507gita811c1fa0a02.1.fc33

Suggest using qemu-sanity-check, which was written as long
ago as 2013 and is made for automatically avoiding these
kinds of bugs.

https://people.redhat.com/~rjones/qemu-sanity-check/

Comment 1 Richard W.M. Jones 2020-05-08 13:45:17 UTC
Created attachment 1686487 [details]
build.log

Comment 2 Richard W.M. Jones 2020-05-08 13:45:49 UTC
Created attachment 1686488 [details]
root.log


Note You need to log in before you can comment on or make changes to this bug.