Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1317680

Summary:	booting custom kernel with secure boot causes 'double free'
Product:	[Fedora] Fedora	Reporter:	Don Zickus <dzickus>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	bcl, lkundrak, mads, pjones
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:	2016-03-14 21:24: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:

Description Don Zickus 2016-03-14 20:42:03 UTC

Description of problem:

I installed F24 on a machine that had 'secure boot' enable (unbeknownst to me).  I went to load a custom kernel to debug the bluetooth driver and grub2 barfed with a 'double free' after loading the kernel.

That was all that was on the screen: 'double free <address>'

A couple of 'echo' statements inside grub2.cfg led me to realize it was failing on loading the kernel.

It wasn't until I compiled my own grub2 rpm, that things went south on next boot, when the MOK manager popped up complaining about invalid key.

I then realized secure boot was enabled, and disabling it resolved my problem.


What am I reporting in this bugzilla?  The double free and/or the lack of a better error message on the failed kernel attempt.  I was hoping a better error message would have saved me a few hours of kernel compiling and grub2 compiling.



Version-Release number of selected component (if applicable):


How reproducible:

100%

Steps to Reproduce:
1. install non-signed kernel
2. boot
3.

Actual results:

double free

Expected results:

"unsigned kernel: not booting" or some silly message to make it more clear what failed.

Additional info:

Comment 1 Brian Lane 2016-03-14 21:24:36 UTC


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