Bug 789503 - reboot fails and drops to a dracut shell
Summary: reboot fails and drops to a dracut shell
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: dracut-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-10 22:20 UTC by kevin martin
Modified: 2012-02-13 16:22 UTC (History)
3 users (show)

Fixed In Version: dracut-015-9.git20120213.fc17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-13 10:13:53 UTC
Type: ---


Attachments (Terms of Use)

Description kevin martin 2012-02-10 22:20:52 UTC
Description of problem:

reboot fails and drops to a dracut shell.  trying ./shutdown from the dracut shell gives me:

Warning: signal caught!
Cannot open font file latarcyrheb_sun16
Cannot open us
Dropping to debug shell

Only way to reboot at this time is to power off the machine by holding down the power button for 5+ seconds.

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

dracut-015-3.git20120208.fc18


How reproducible:

every time

Steps to Reproduce:
1. type reboot and hit enter
2. drop to the dracut shell
3.
  
Actual results:

doesn't reboot, only drops to dracut shell

Expected results:

reboots.

Additional info:

Comment 1 kevin martin 2012-02-11 14:58:47 UTC
more info.

I rebuilt the initramfs with "dracut -f" and applied the patch referenced in bugzilla 789119 and nothing has changed.  FWIW, just prior to dracut reporting that it's caught a signal I see:

dracut: Disassembling device-mapper devices
dracut: Disassembling mdraid devices

Then it catches the signal, reports it can't open the font file and the keytable (latarcyrheb_sun16 and us), and drops to the shell prompt.  If I exit the shell I get a kernel panic and have to hard reboot.

Comment 2 Harald Hoyer 2012-02-13 10:13:53 UTC
dracut-015-9.git20120213.fc17

Comment 3 kevin martin 2012-02-13 16:22:15 UTC
Yep, that seems to have fixed it.  Thanks.


Note You need to log in before you can comment on or make changes to this bug.