Bug 7032 - Failure to reliably auto-boot with a serial console
Failure to reliably auto-boot with a serial console
Product: Red Hat Linux
Classification: Retired
Component: lilo (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-11-15 18:50 EST by Chris Siebenmann
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:47:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Siebenmann 1999-11-15 18:50:23 EST
System: Dell PowerEdge 2300 server, dual CPUs, with a
serial console configured on /dev/ttyS0 at 9600 baud in
LILO and the kernel.

 After upgrading from RH 6.0 to 6.1, our system (running
the exact same kernel as before the upgrade, as we use a
custom kernel) developed an inability to consistently do
unattended reboots. If we left LILO boot the system via
its timeout, it would print:
	Loading <kernel version>...........
and then there would be a long string of ASCII NUL's dumped
out the serial port and nothing much would happen. (In some
experiments, the monitor would display the kernel hanging
right after the 'Console: colour VGA+ 80x25' line.) It
appears that if we explicitly hit return on the serial
console at the LILO promtp, the system would come up.

(It's hard to be precise on the diagnostics, because this
 is our production server and only reboots in situations
 where it needs to be up as soon as possible afterwards.)

 We reverted LILO back to lilo-0.21-6, the version from
RH 6.0, and in one test since then the problem has gone
away. (And the system was trouble-free until our upgrade
to 6.1.)
Comment 1 Cristian Gafton 2000-01-04 17:27:59 EST
Assigned to dledford
Comment 2 Jeremy Katz 2002-06-04 00:54:11 EDT
Do you continue to see this problem with newer versions of Red Hat Linux?
Comment 3 Jeremy Katz 2002-06-29 17:47:55 EDT
Closing due to inactivity.  If you have further information, please reopen this bug.
Comment 4 Red Hat Bugzilla 2006-02-21 13:47:33 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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