Bug 177328

Summary: Kernel 2.6.14-1.1656_FC4 hangs on boot x86_64
Product: [Fedora] Fedora Reporter: Jason Cwik <jason-redhat>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: pfrields, wtogami
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: 2006-05-05 12:54:27 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 from working boot of FC4 kernel. none

Description Jason Cwik 2006-01-09 17:59:26 UTC
Description of problem:
Kernel 2.6.14-1.1656_FC4 hangs on boot at "SELinux: Registering netfilter hooks"

I also tried the test kernel from
http://people.redhat.com/davej/kernels/Fedora/FC4 (2.6.15-1.1823_FC4) and it
hangs a few more lines down at "io scheduler cfq registered".

Hardware is HP dx5150MT, Athlon64 4000+, 3GB RAM.  New install of FC4 x86_64.

Version-Release number of selected component (if applicable):
kernel-2.6.14-1.1656_FC4

How reproducible:
Always

Steps to Reproduce:
1. Upgrade kernel
2. reboot
3. hang
  
Actual results:


Expected results:


Additional info:

Comment 1 Jason Cwik 2006-01-09 17:59:27 UTC
Created attachment 122958 [details]
dmesg from working boot of FC4 kernel.

Comment 2 Dave Jones 2006-02-03 06:47:05 UTC
This is a mass-update to all currently open kernel bugs.

A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

Thank you.


Comment 3 John Thacker 2006-05-05 12:54:27 UTC
Closing per previous comment.