Bug 607806
Summary: | udev hangs on boot with 2.6.18-194.3.1.el5xen | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Orion Poplawski <orion> | ||||||
Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 5.5 | CC: | drjones, orion, rhod, xen-maint | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2014-07-03 13:20:09 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: | |||||||||
Attachments: |
|
Description
Orion Poplawski
2010-06-24 21:27:37 UTC
If you can boot a different kernel with the same udev, then it's a kernel bug. You might want to check, if it is a kernel module, which is hanging, by adding "modprobedebug" to the kernel command line and remove "rhgb quiet". If I change udev_log to "info" in /etc/udev/udev.conf, the system boots fine, so it seems like some kind of timing issue. modprobedebug lists the follow modules as the last loaded (all that fit on the screen): joydev sg snd-seq-oss snd-seq-midi-event snd-seq snd-seq-device snd-pcm-oss snd-mixer-oss snd-pcm Tried making a /etc/modprobe.d/blacklist-test file with those modules listed, e.g.: blacklist joydev to no effect. I am seeing these in the -194 logs, but not in -164: hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x000f0000 ACPI: Mapper loaded dell-wmi: No known WMI GUID found w83627ehf: Found W83627EHG chip at 0x290 Created attachment 426936 [details]
dmesg-2.6.18-164.15.1.el5xen
Created attachment 426937 [details]
dmesg-2.6.18-194.3.1.el5xen
Nothing in the dmesg differences between -164 and -194 looks interesting. Are you saying that with the same udev you can boot on 164, but not 194? What about bare-metal 194? (In reply to comment #5) > Nothing in the dmesg differences between -164 and -194 looks interesting. Are > you saying that with the same udev you can boot on 164, but not 194? What about > bare-metal 194? Yes, current udev and -164 xen boot fine. Tried three time with bare-metal 194 - got 1 good boot, one udev hang, and one kernel panic. My guesses are either loading the sym53c8xx driver and related - I have two tape drives attached that can get into bad states at times, or 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) as the latest boot seemed to indicate udev might have been waiting for that to load. This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug. I'm no longer using EL5 or xen. Closing. Too old RHEL5 bug. |