Bug 732222 - System fails to boot with f15 kernels based on Linux 3.0.x
Summary: System fails to boot with f15 kernels based on Linux 3.0.x
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-21 00:39 UTC by Shiv Manas
Modified: 2012-06-06 22:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 22:47:10 UTC


Attachments (Terms of Use)

Description Shiv Manas 2011-08-21 00:39:12 UTC
Description of problem:

My freshly installed and updated f15 system doesn't boot using any of the 3.0 based kernels - including the official f15 2.6.40 kernel updates. They all get stuck after the "Started /home" message. Booting in runlevels 3 and 1 don't help either (gets stuck at the same place).


Version-Release number of selected component (if applicable):
2.6.40.x


How reproducible:
Install any of the 3.0 based kernel updates, reboot system.


Steps to Reproduce:
1. Update the system so 3.0 based kernels get instaled
2. Reboot the system


Actual results:
System fails to boot up in any runlevel. Initially hangs for a while at "Started /home". After a few minutes, some more messages come up and finally it stops at udevd[###]: worker [###] failed while handling '/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.0/video4linux/video0'


Expected results:
System should bootup normally. Had no issues with earlier kernels.


Additional info:
 - Other distros (Ubuntu Oneric) boot fine with the new kernels on this system. 
 - No proprietary drivers are in use.
 - My hardware is a DELL INSPIRON M102z AMD Fusion (E-350) based netbook.
 - lshw: http://fpaste.org/FcEM
 - lspci: http://fpaste.org/P86J
 - More info with screenshots: http://forums.fedoraforum.org/showthread.php?t=268395

Comment 1 Josh Boyer 2012-06-06 18:30:25 UTC
Is this still happening with 2.6.43/3.3?

Comment 2 Shiv Manas 2012-06-06 22:47:10 UTC
(In reply to comment #1)
> Is this still happening with 2.6.43/3.3?

Nope, this was fixed a couple of kernel updates later. The current kernels work fine.

Comment 3 Josh Boyer 2012-06-06 22:55:39 UTC
Thank you for letting us know.


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