Bug 1287198

Summary: kernel-4.4.0-0.rc2.git2.1.fc24.x86_64 - panic on boot from a fatal exception on interrupt
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal.jnn>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, michal.jnn
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-01 18:21:36 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
a screen picture with a kernel panic none

Description Michal Jaegermann 2015-12-01 18:06:46 UTC
Created attachment 1100981 [details]
a screen picture with a kernel panic

Description of problem:

An attempt to boot kernel-4.4.0-0.rc2.git2.1.fc24.x86_64 ends up with 
Kernel panic - not syncing: Fatal exception in interrupt.

The whole affair starts with 
BUG: Unable to handle NULL pointer dereference at 0000000000000130
IP: [<ffffffff81164705>]  pids_cancel.constprop.6+0x5/0x40

Details I was able to capture with a photo of a screen on an attached picture.

Version-Release number of selected component (if applicable):
kernel-4.4.0-0.rc2.git2.1.fc24.x86_64

How reproducible:
So far on every try (except of one - see further down).

Additional info:
1. I managed to boot the kernel in question _once_.  That was before an extensive series of rawhide updates but I do not see how a user space can be involved in this.
2. This kernel panic is preceded earlier by a backtrace which may be something like from bug 1284109.  It scrolls too quickly for me to be sure and nothing is recorded in logs.  No suprise here as file systems are not mounted yet when the whole thing goes belly up.
3. kernel-4.4.0-0.rc0.git9.1.fc24.x86_64 used to boot but it does not anymore; it is getting a panic too.
4. None of rc1 kernels I tried I was able to boot but they were just stuck somewhere in initrd without any progress and I did not see any panics or warnings.
5. kernel-4.2.6-301.fc23.x86_64 from f23 release boots the same installation without any panics, backtraces or other dramas.  Lucky me!

Comment 1 Josh Boyer 2015-12-01 18:21:36 UTC

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