On an otherwise now reliable system see [bug 26977], my system reliably
stalls during boot just after displaying
Real Time Clock Driver v1.09
until a keypress. I have not waited longer than 20s to see if it's just a
weird timing thing, but after several different reboots for other reasons
(see above bug), the boot continues *every time* *immediately* after a
FWIW, I usually use the shift key as it rarely generates input that might
confuse the situation. :-)
I installed a rebuilt i586 kernel, but noticed this as well on an md5
verified RH disti i586 kernel. i386 untested, I'm trying to beat my poor
p120 hard enough as it is....
sorry, forgot to rank this as high...if I put this kernel on remote servers in a
NOC, I can't remotely reboot them with confidence.
I'd like to add a "me too". Hangs as described on a Dell XPS P90c with an
upgraded CPU (Evergreen Spectra 233). This system worked perfectly w/ the
2.2.16 kernel and the multiple RH 6.2 kernels.
According to my syslog, it's right before
Toshiba System Managment Mode driver v1.7 22/6/2000
So, it could be that as well?
Have furthermore tested this stall to several minutes. I would assume infinite,
but I'm not going to test out that far.
According to ftp://ftp.us.kernel.org/pub/linux/kernel/v2.2/linux-2.2.17.log.html
, could it be that the 'added SMM driver for Toshiba laptops [update]' is
involved? This gw2k doesn't look like it has Toshiba on it.
Similar stall on IBM 330-P100 after Real Time Clock Driver v1.09
on both i586 and i386 rpm releases. Requires keystroke to continue boot.
This may be fixed as of the 2.2.19 release, given that it fixes [bug 29558],
which was reported on RH7 and apparently got better attention.
Allthough this is still nominally open as a 2.2.17 issue, given that 2.2.19
works for me, *I* don't mind if it gets closed/discarded/whatever; those other
folks might though.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/