Bug 1373602 - Kernel Panic 4.7.2.201.FC.24.x86.64 with Secure Boot Enable
Summary: Kernel Panic 4.7.2.201.FC.24.x86.64 with Secure Boot Enable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-06 17:13 UTC by LuisFer
Modified: 2017-01-18 17:07 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-15 00:59:26 UTC
Type: Bug

Attachments (Terms of Use)
Screenshot of kernel panic (272.38 KB, image/jpeg)
2016-09-13 17:05 UTC, Tom Atkinson 		no flags Details
Boot with slub_debug=P #1 (796.66 KB, image/jpeg)
2016-09-16 00:31 UTC, Tom Atkinson 		no flags Details
Boot with slub_debug=P #2 (785.06 KB, image/jpeg)
2016-09-16 00:31 UTC, Tom Atkinson 		no flags Details
Boot log from previous kernel (62.53 KB, text/plain)
2016-09-16 00:32 UTC, Tom Atkinson 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description LuisFer 2016-09-06 17:13:23 UTC 
Description of problem:EFI Problem loading Kernel x-509 certificate (-22) 


Version-Release number of selected component (if applicable):4.7.2.201.FC.24.x86.64


How reproducible:on every boot with Secure boot Enabled


Steps to Reproduce:
1. Change to Secure Boot Enable
2. Reboot with this kernel
3.

Actual results: Disable Secure boot works normally


Expected results:


Additional info: Toshiba Satellite F50t-B-11d Bios 1.50 12/09/2014
Comment 1 LuisFer 2016-09-06 17:17:51 UTC 
The workaround is disable the secure boot on BIOS
Kernel 4.6.4.301.fc.24.x86.64 works with Secure Boot Enabled
Comment 2 Laura Abbott 2016-09-06 19:49:02 UTC 
Is the only issue the warning or is there something else? we've seen that warning reported before but it has not caused an issue.
Comment 3 Tom Atkinson 2016-09-13 17:05:53 UTC 
Created attachment 1200565 [details]
Screenshot of kernel panic
Comment 4 Tom Atkinson 2016-09-13 17:11:31 UTC 
I have the same problem with my Toshiba Satellite. Previous kernels display the same warning but no panic. Issue still present in 4.7.3-200.
Comment 5 Laura Abbott 2016-09-15 22:13:42 UTC 
Can you try booting with slub_debug=P on the command line and attach the full bootup logs from a previous kernel with the certificate warning? This might be a case of error handling somewhere.
Comment 6 Tom Atkinson 2016-09-16 00:31:31 UTC 
Created attachment 1201491 [details]
Boot with slub_debug=P #1
Comment 7 Tom Atkinson 2016-09-16 00:31:54 UTC 
Created attachment 1201492 [details]
Boot with slub_debug=P #2
Comment 8 Tom Atkinson 2016-09-16 00:32:33 UTC 
Created attachment 1201493 [details]
Boot log from previous kernel
Comment 9 Tom Atkinson 2016-12-14 13:04:20 UTC 
This is working again with 4.9.0
Comment 10 Laura Abbott 2016-12-15 00:59:26 UTC 
There was a certificate parsing fix that came in with 4.9. Thank you for letting us know.
Comment 11 LuisFer 2017-01-18 17:07:16 UTC 
Works correctly with the 4.9.3-200.fc25.x86_64 #1 SMP  kernel.
Thanks
Note You need to log in before you can comment on or make changes to this bug.