Bug 209245 - Boot process hangs while loading io shceduler for 64 bit versions of 2187 (Core 5) and Test 3 (Core 6)
Summary: Boot process hangs while loading io shceduler for 64 bit versions of 2187 (Co...
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Whiteboard: bzcl34nup
: 209246 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-04 01:43 UTC by Walter
Modified: 2008-08-02 23:40 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2008-05-06 16:26:27 UTC

Attachments (Terms of Use)
hanged boot with initcall_debug (131.27 KB, image/jpeg)
2006-11-12 02:24 UTC, Michal Jaegermann
no flags Details

Description Walter 2006-10-04 01:43:35 UTC
Description of problem:

Using 64-bit versions, system (HP a1610n - dual AMD 64bit) hangs during boot 
load at io scheduler cfg registered (default) with 2.617-1.2187-FC5 64 bit and 
FC^ Test 3. Version 2.615-1.2054-FC5 64 bit does not display this problem.

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

32bit versions do not display this problem.

How reproducible:

Steps to Reproduce:
1. Install 2054 Core 5 Release
2. Update kernel to 2187
3. Reboot - hang occurs at previously mentioned location
Actual results:

Expected results:

Additional info:

Comment 1 Dave Jones 2006-10-07 04:41:15 UTC
*** Bug 209246 has been marked as a duplicate of this bug. ***

Comment 2 Dave Jones 2006-10-28 18:53:17 UTC
can you boot with the option initcall_debug  and see what the last line that
gets dumped says (if different to above?)
If cfq was broken I'd expect a more widespread problem, so it's likely that it's
silently blowing up in whatever gets initialised after cfq.

Comment 3 Michal Jaegermann 2006-11-12 02:24:43 UTC
Created attachment 140978 [details]
hanged boot with initcall_debug

Here is a picture from such hang with 2.6.18-1.2239.fc5.  A kernel
on an FC6 installer is doing that too.	It is actually quite possible
that this is the same as bug 212172 (and maybe a fixed BIOS, if
available, is an answer).

Comment 4 Dave Jones 2006-11-12 07:38:31 UTC
some things to try..


Comment 5 Bug Zapper 2008-04-04 03:54:17 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 6 Bug Zapper 2008-05-06 16:26:24 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.