Bug 496283

Summary: kernel-PAE hangs at boot
Product: [Fedora] Fedora Reporter: Mary Ellen Foster <mefoster>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: itamar, kernel-maint, nathaniel, quintela
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-07 03:37:12 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:

Description Mary Ellen Foster 2009-04-17 16:05:48 UTC 
Description of problem:
On a fully updaated Rawhide system, the PAE kernel hangs at boot. I originally installed from the live image, so my initial kernel was i586; then I "yum install"ed kernel-PAE which got me kernel-PAE-2.6.29.1-70.fc11.i686. With this kernel, booting always hangs (as far as I can tell, forever) at the end of the boot process, just before the login screen appears -- the last line on the boot screen refers to starting the Wine service. This happens with runlevel 3 and 5, so I don't think that it has to do with anything graphical.

kernel-2.6.29.1-70.fc11.i586 always boots cleanly on this computer, so it seems clear it's got something to do with the kernel rather than any other components.

The processor in this (brand-new) machine is "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz", which I'm told should support the PAE kernel.


Version-Release number of selected component (if applicable):
kernel-PAE-2.6.29.1-70.fc11.i686

How reproducible:
Every time

Steps to Reproduce:
1. Boot
  
Actual results:
Computer hangs and needs to be power cycled

Expected results:
Login screen

Additional info:
I can provide more hardware info (Smolt profile, etc.) later this evening
Comment 1 Nathaniel McCallum 2009-05-03 00:57:23 UTC 
this bug is a duplicate of Bug 493526
Comment 2 Chuck Ebbert 2009-05-07 03:37:12 UTC 

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