Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 579122 - udev error on Compaq nx7400 with "stable" kernel 2.6.32.10
Summary: udev error on Compaq nx7400 with "stable" kernel 2.6.32.10
Keywords:
Status: CLOSED DUPLICATE of bug 578217
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-02 18:26 UTC by yboc1234-fedora
Modified: 2010-04-05 14:33 UTC (History)
8 users (show)

Fixed In Version: kernel-2.6.32.10-94.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-05 14:33:52 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description yboc1234-fedora 2010-04-02 18:26:09 UTC 
Description of problem:
udev error on Compaq nx7400 with "stable" kernel 2.6.32.10

Specific error reached while booting: 
Starting udev: udevd-work[522] : ' /sbin/modprobe -b pci : v000014E4d0000170Csv0000103Csd000030A2bc02sc00i00' unexpected exit with status 0x00009
This error makes booting impossible with this kernel.

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


How reproducible:
Hardware specific.

Steps to Reproduce:
1. Install the kernel on a Compaq nx7400 
2. watch boot sequence fail
Comment 1 Göran Wallin 2010-04-04 13:37:33 UTC 
I'm having the same issue on my Dell Inspiron 8600. See bug 577463 for a likely fix.
Comment 2 yboc1234-fedora 2010-04-04 16:59:56 UTC 
This problem may indeed be the same. Regardless this kernel needs patching.
Comment 3 John W. Linville 2010-04-05 14:33:52 UTC 

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