Bug 481228 - Can't finish boot since kernel 2.6.27.8-144.fc10
Summary: Can't finish boot since kernel 2.6.27.8-144.fc10
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-22 21:30 UTC by Florent Le Coz
Modified: 2009-08-26 18:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-26 18:10:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Florent Le Coz 2009-01-22 21:30:22 UTC
Description of problem:
I have those kernels installed :
kernel.x86_64                                   2.6.27.5-117.fc10                                   installed
kernel.x86_64                                   2.6.27.8-144.fc10                                   installed
kernel.x86_64                                   2.6.27.9-159.fc10                                   installed
kernel.x86_64                                   2.6.28.1-19.fc10                                    installed

I can only boot the first one correctly.
All the others fail after the end of the boot, just when GDM is supposed to appear.
It takes some times to make plymouth disappear and to make my wallpaper appear, then I see only the mouse. 10 seconds later it freezes. (with still no GDM in view, only the wallpaper and the mouse) 

Version-Release number of selected component (if applicable):
2.6.27.8-144.fc10 and above

How reproducible:
always

Steps to Reproduce:
1. boot normaly
2. fail just before the GDM

Additional info:
I don't know exactly what information (log ?) I could give, please ask them.

Comment 1 Vedran Miletić 2009-08-26 13:55:06 UTC
Please retest with Fedora 11.

Comment 2 Florent Le Coz 2009-08-26 17:39:10 UTC
Works correctly on fedora 11.

Fixed, then. :)


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