serial console messup during boot

[Paul Slootman]

With 2.6 kernels we've noticed that there's a period during booting that
the serial console output is messed up. Most probable cause is a wrong
baud rate.

This is on Dell rackmount servers, with the serial console running at
115200 baud. The BIOS works fine, GRUB works fine, the first part of the
kernel bootup shows up fine, and then:

  Real Time Clock Driver v1.12  
  i8042: ACPI detection disabled
  serio: i8042 AUX port at 0x60,0x64 irq 12
  serio: i8042 KBD port at 0x60,0x64 irq 1 
  Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxINIT: version 2.85 booting
  Activating swap.
  Adding 1052152k swap on /dev/md3.  Priority:1 extents:1
  Checking root file system...                           
  fsck 1.35 (28-Feb-2004)
  Reiserfs super block in block 16 on 0x900 of format 3.6 with standard journal
  Blocks (total/free): 264960/247705 by 4096 bytes
  Filesystem marked as cleanly umounted
  Filesystem seems mounted read-only. Skipping journal replay.
  Checking internal tree..finished                  

The xxxx characters were garbage characters that I didn't want to paste
into an otherwise ASCII message...
As soon as the serial driver is loaded, the baud rate (I guess) is
messed up until the time init is loaded (which probably resets the
serial console settings).

I've tried e.g. setting the default baudrate in the serial driver to 115200
to no avail, so I'm hoping someone here will be able to help. On at
least one occasion booting went wrong in the time that the output is
messed up, so we had to carry a CRT into the server room to watch the
VGA, so we'd be most grateful if this little problem could be fixed :-)

With 2.4 kernel this corruption of the output does not occur.


Thanks,
Paul Slootman

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/