Red Hat Bugzilla – Bug 196155
installation via serial console hangs on Xserve G5 headless node
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
Attempting to install FC5 via serial console on an Xserve G5 cluster node
(completely headless) from external Firewire drive hangs shortly after kernel
Version-Release number of selected component (if applicable):
FC5 installation cd 1
Steps to Reproduce:
1.put cd in external firewire drive
2.reboot xserve to open firmware
3.boot installation from external firewire
Hangs shortly after the smp_core99_probe line:
PID hash table entries: 4096 (order: 12, 131072 bytes)
time_init: decrementer frequency = 33.333333 MHz
time_init: processor frequency = 2000.000000 MHz
core99_setup_cpu 0 done
#1 SMP Tue Mar 14 15:57:06 EST 2006
Created attachment 131313 [details]
log of attempt to boot FC6 test1 resque cd from Xserve serial console
I tried several flags to the boot command to see if I could get the
serial console install to work with FC6 test1 also. But nothing worked.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
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 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.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen
I never received any email from comment 3 above, so I was unaware that the
bug was in a NEEDINFO state. I only received email for comment 4 showing
I am reopening the bug, and will test with rawhide. 2.6.24 has changed
the device that zilog serial controller uses. This eliminates the need for
a special workaround for zilog.
I'll put this back in NEEDINFO until you can test with rawhide. Also, beware
that F9 Alpha is just around the corner, so you may want to test with that
(there have been some issues the last few days with rawhide actually being
installable - not sure on the status of that, I think it's resolved except for
maybe some firstboot weirdness)
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
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
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
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.