Bug 1669846

Summary: kernel BUG at mm/page_alloc.c:798! invalid opcode: 0000 [#1] SMP PTI
Product: [Fedora] Fedora Reporter: Nate Pearlstein <darknater>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 29CC: airlied, bskeggs, darknater, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-03 05:20:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
output from earlyprintk none

Description Nate Pearlstein 2019-01-27 15:10:59 UTC
Created attachment 1524025 [details]
output from earlyprintk

1. Please describe the problem:

Dell T7500 won't boot any fedora 29 kernel starting with 4.19.13-300.fc29.x86_64
Appears to hang right after "Probing EDD"

2. What is the Version-Release number of the kernel: 4.19.13-300.fc29.x86_64

4.19.13-300.fc29.x86_64
4.19.15-300.fc29.x86_64
4.20.3-200.fc29.x86_64

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 :

Worked previously, stopped working at 4.19.13-300.fc29.x86_64 https://koji.fedoraproject.org/koji/buildinfo?buildID=1176140

Verified that 4.19.11-300.fc29.x86_64, 4.19.12-301.fc29.x86_64 work fine.



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

Attempt to boot with any fedora 29 kernel 4.19.13-300.fc29.x86_64 or later exhibits problem.


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``:

Unknown

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

yes, but panic happens so early those modules aren't loaded.


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.

Attaching output from earlyprintk

Comment 1 Nate Pearlstein 2019-02-03 05:20:01 UTC
This one is likely a duplicate of 1666948

*** This bug has been marked as a duplicate of bug 1666948 ***