Bug 127204

Summary: System startup with new kernel failure
Product: [Fedora] Fedora Reporter: Johan Mederyd <mr_mederman>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED CANTFIX QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: mattdm
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-24 20:31:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 124619    

Description Johan Mederyd 2004-07-03 23:42:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
I ran the up2date application and collected all updates.
When rebooting, the option to boot with a new kernel was added in the
grub menu.
As I select the new kernel I finally arrive to a screen displaying a
computer and a progress meter.
The meter gets to about 10% and then nothing more happens.



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

How reproducible:
Always

Steps to Reproduce:
1.Install Fedora 2
2.Run up2date.
3.Reboot with new kernel.
    

Actual Results:  Impossible to run operating system with new kernel.

Expected Results:  Normal startup with new kernel, old kernel bootup
option should then be removed.

Additional info:

When booting with old core I get the errors:
 mdmpd failed
 bootup smartd failed

Comment 1 Matthew Miller 2005-04-26 15:25:26 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 2 John Thacker 2006-04-24 20:31:18 UTC
Probably not an up2date issue, but closing due to no response from reporter
and the Fedora Legacy issue mentioned above.