Bug 1778520 - kernel BUG at arch/powerpc/include/asm/book3s/64/pgtable.h:612
Summary: kernel BUG at arch/powerpc/include/asm/book3s/64/pgtable.h:612
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-01 20:29 UTC by Richard W.M. Jones
Modified: 2026-07-24 14:54 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
build.log containing kernel logs (916.15 KB, text/plain)
2019-12-01 20:29 UTC, Richard W.M. Jones
no flags Details

Description Richard W.M. Jones 2019-12-01 20:29:48 UTC
Created attachment 1641160 [details]
build.log containing kernel logs

1. Please describe the problem:

Kernel cannot boot on qemu in Rawhide.

2. What is the Version-Release number of the kernel:

kernel ppc64le 5.4.0-2.fc32
qemu ppc64le 2:4.2.0-0.2.rc2.fc32

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Yes it previously worked, about 2 weeks ago.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Run libguestfs-test-tool or qemu-sanity-check

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes, see above.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Charles Haithcock 2026-07-24 14:54:17 UTC
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. 

NOTE: This is an automated mass update.


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