Bug 139528 - Must turn off computer in order for kernel to load after reboot
Summary: Must turn off computer in order for kernel to load after reboot
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: grub
Version: 3
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-16 16:11 UTC by Seth Doty
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-03 18:34:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Seth Doty 2004-11-16 16:11:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
If I reboot my computer it will load the grub screen and then attempt
to load the kernel. it will only get as far as:  

root (hd0,0)
        kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00
        initrd /initrd-2.6.9-1.667.img


It will then just sit here for a few seconds and then say kernel
cannot be loaded press any key to restart.   If I turn off the
computer completely before or after this point the kernel will load
fine and boot cleanly

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

How reproducible:
Always

Steps to Reproduce:
1.reboot Fedora core
2.let grub boot either automatically or by menu selection
3.watch kernel not load
    

Actual Results:  kernel will not load and will say kernel cannot be
loaded press any key to restart

Expected Results:  kernel should boot

Additional info:

All it takes for me to make the system boot is to shutdown then turn
it on and let it boot. reboot will have this effect everytime.  I can
press a button as it says for days and it will error out the same
until the computer is turned off and then turned back on

Comment 1 Jeremy Katz 2004-11-16 16:39:29 UTC
Is there an updated BIOS available for your machine?  Things like this
are often caused by bugs in BIOS implementations of soft reboots.


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