Bug 703508

Summary: kernel-2.6.35.13 fails to complete startup; kernel-2.6.35.12 starts OK
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-12 16:20:46 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 Flags
dmesg output
none
previous dmesg for comparison purposes
none
requested contents of /proc/cpuinfo none

Description Peter H. Jones 2011-05-10 14:45:10 UTC
Created attachment 498035 [details]
dmesg output

Description of problem:
Booting kernel-2.6.35.13 hangs

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

How reproducible:
Always

Steps to Reproduce:
1. Try to boot
2.
3.
  
Actual results:
Slow, hangs with blue Fedora icon on screen.

Expected results:
Normal boot to login screen

Additional info:
Used mode 1 to get dmesg info for this version and previous version.
In the new version, "shutdown -h now" also seemed to hang. I had to
power off manually.

Hangup can be seen in dmesg.output, starting at line:
[   91.464150] dracut: udevadm settle - timeout of 30 seconds reached, the event queue contains:

Comment 1 Peter H. Jones 2011-05-10 14:46:31 UTC
Created attachment 498039 [details]
previous dmesg for comparison purposes

Comment 2 Chuck Ebbert 2011-05-11 00:01:22 UTC
dracut: 
dracut: udevadm settle - timeout of 30 seconds reached, the event queue contains:
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0 (743)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/drm/controlD64 (826)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/drm/card0 (827)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/drm/card0/card0-VGA-1 (837)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/drm/card0 (838)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/drm/card0/card0-LVDS-1 (840)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/drm/card0 (841)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/drm/card0/card0-HDMI-A-1 (843)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/drm/card0 (844)
dracut: /sys/devices/pci0000:00/0000:00:01.0/0000:01:05.0/graphics/fb0 (845)

I don't see anything in the 2.6.35.13 update that would cause that.

Can you attach the contents of /proc/cpuinfo?

Comment 3 Peter H. Jones 2011-05-11 09:34:00 UTC
Created attachment 498238 [details]
requested contents of /proc/cpuinfo

Comment 4 Chuck Ebbert 2011-05-12 16:20:46 UTC

*** This bug has been marked as a duplicate of bug 704059 ***

Comment 5 Chuck Ebbert 2011-05-12 16:36:13 UTC
(In reply to comment #3)
> Created attachment 498238 [details]
> requested contents of /proc/cpuinfo

Which /proc/cpuinfo was that, the one from 2.6.35.12 or the one from 2.6.35.13? Can you compare the "flags" lines and see if anything changes when running the two different kernels?