Bug 579994 - Can't boot with the kernel 2.6.32.10-90.fc12.i686.PAE
Summary: Can't boot with the kernel 2.6.32.10-90.fc12.i686.PAE
Keywords:
Status: CLOSED DUPLICATE of bug 579618
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-07 08:41 UTC by Laurent Vaills
Modified: 2010-04-07 12:13 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-07 12:13:50 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Error on udev at boot (1.32 MB, image/jpeg)
2010-04-07 08:41 UTC, Laurent Vaills 		no flags Details
View All

Description Laurent Vaills 2010-04-07 08:41:40 UTC 
Created attachment 404865 [details]
Error on udev at boot

Description of problem:
Since I've updated to the kernel 2.6.32.10-90.fc12.i686.PAE my laptop (DELL Inspiron 1720) does not want to boot. 

Version-Release number of selected component (if applicable):
2.6.32.10-90.fc12.i686.PAE

How reproducible:


Steps to Reproduce:
1.Update to the kernel 2.6.32.10-90.fc12.i686.PAE
2.Reboot
3.
  
Actual results:
My laptop freezes.

Expected results:
My laptop should boot.

Additional info:
Here is the grub definitions :
title Fedora (2.6.32.10-90.fc12.i686.PAE)
	root (hd0,5)
	kernel /vmlinuz-2.6.32.10-90.fc12.i686.PAE ro root=/dev/mapper/VolGroup00-LogVol00_root rhgb quiet vga=0x365 SYSFONT=latarcyrheb-sun16 LANG=fr_FR.UTF-8 KEYTABLE=fr-latin9
	initrd /initramfs-2.6.32.10-90.fc12.i686.PAE.img

When I hit the esc key, I can see an error about udev (please see the picture in attachment)
Comment 1 Dirk Hoffmann 2010-04-07 09:27:08 UTC 
Duplicate of Bug #579618?

I am submitting a similar report there. There are also answers or rather an indication of hope in that thread.
Comment 2 Laurent Vaills 2010-04-07 12:13:50 UTC 

*** This bug has been marked as a duplicate of bug 579618 ***
Note You need to log in before you can comment on or make changes to this bug.