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 238006

Summary: hard system lockup during 'Starting udev:'
Product: [Fedora] Fedora Reporter: Charlie Bennett <ccb>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 6CC: cbennett, jonstanley
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-08 04:24:42 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:
Bug Depends On:    
Bug Blocks: 427887    
Attachments:
Description Flags
RPM list
none
lspci listings for our Dell 2950 configuration
none
lspci listings for our Gateway 9515R configurations none

Description Charlie Bennett 2007-04-26 14:48:36 UTC 
Description of problem:

During reboot I'm frequently seeing hard lockups of the
system during udev startup.  I've turned on udev debugging
and I see this

udevd-event[754]: run_program: '/bin/sh' (stderr) 'FATAL: Module pnp:dIPI001
not found.'
..
udevd-event[759]: run_program: '/lib/udev/udev_run_hotplugd'
udevd-event[971]: pass_env_to_socket: passed -1 bytes to socket
/org/freedesktop/hal/udev_event
udevd-event[812]: run_program" '/lib/udev/modprobe' (stderr) 'FATAL: Module
pci:v00008086d000025F0sv00001028sd000001B2bc06sc00i00 not found.'
udevd-event[978]: run_program: '/lib/udev/udev_run_hotplugd' returned with
statu

And the system is locked hard requiring power cycle.

This happens most frequently on Dell 2950:
  dual-die dual-core in 32-bit mode
  8 GB RAM
  HW RAID via Dell Perc5/i (megaraid_sas)

I've also seen it on Gateway 9515R, also dual-die dual-core.
  dual-die dual-core in 32-bit mode
  4 GB RAM
  Fibre SAN via Emulex LP-101 (lpfc)


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

Happens on kernels:
kernel-PAE-2.6.19-1.2911.6.5
kernel-PAE-2.6.20-1.2933
kernel-PAE-2.6.20-1.2944



How reproducible:

Cycle the machines frequently.  Sometimes they
start fine, sometimes they lock.


Steps to Reproduce:
1. Install the machines, list of RPMs installed attached
2. Install our application
3. Reboot liberally
  
Actual results:

Lockup as described above

Expected results:

No lockups

Additional info:

This is an in-house derived distro.  I've attached our
RPM list to verify that nothing is missing.
Comment 1 Charlie Bennett 2007-04-26 14:48:37 UTC 
Created attachment 153517 [details]
RPM list
Comment 2 Charlie Bennett 2007-04-26 14:52:23 UTC 
Created attachment 153518 [details]
lspci listings for our Dell 2950 configuration
Comment 3 Charlie Bennett 2007-04-26 14:55:34 UTC 
Created attachment 153520 [details]
lspci listings for our Gateway 9515R configurations

If more info is needed, drop me a line.
Comment 4 Jon Stanley 2008-01-08 01:47:24 UTC 
(This is a mass-update to all current FC6 kernel bugs in NEW state)

Hello,

I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!
Comment 5 Jon Stanley 2008-02-08 04:24:42 UTC 
Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA,
since no information has been lodged for over 30 days.

Please re-open this bug or file a new one if you can provide the requested data,
and thanks for filing the original report!