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 826920

Summary:	At shutdown / restart caps indicator flashes
Product:	[Fedora] Fedora	Reporter:	Eric Rollo <eric>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17	CC:	dennis, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-05 18:46:58 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 Eric Rollo 2012-05-31 09:09:54 UTC

Description of problem:  Upgrade from F16 to F17 Unable to restart or shut down.  Caps lock key indicator flashing and freezing at end of shutdown scripts.


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


How reproducible:  Every shutdown since upgrade


Steps to Reproduce:
1.Select Log Off
2.Select shutdown / restart
3.
  
Actual results:
Shuts as normal but then caps lock indicator starts to flash and system freezes requires forced shutdown.


Expected results:
Shuts down or restarts as requested

Additional info:

Comment 1 Josh Boyer 2012-07-05 18:46:58 UTC

There was a common bug where upgrades from f16 would boot the f16 kernel.  That had a mismatch in the initramfs from what the f17 userspace was expecting, which would result in a kernel panic.  Booting an f17 kernel should work just fine.

I'm going to mark this as a duplicate of that bug based on the little information we have here.  If you are still seeing this with one of the 3.4.x F17 kernel updates, please reopen.

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