I'm working on an embedded system running a 2.6.32 kernel originally derived from RHEL6. The hardware architecture is similar to a PC. The device is a specialized server. It uses an 8250 compatible serial port for the console. When it's booting up, everything looks fine until it initializes the serial driver. At that point the output to the console becomes garbled until (I think...) getty runs for the console port. Then it's readable again. It looks as though the initialization of the serial driver is setting the wrong baud rate, or perhaps some other configuration. During the boot process, this garbled output happens for about 1 second, during which probably a few thousand characters of garbage are output. The grub boot parameter specifies "console=ttys0,57600" The getty line for the console specifies "T0:23:respawn:/sbin/getty -L ttys0 57600 vt100" It's not clear to me how the serial driver is supposed to be initialized to the right baud rate. Is the parameter from the boot line supposed to be used? (Just to complicate matters, we're using a Debian userspace with this kernel). Here's how it looks on the console: [ 4.429923] Non-volatile memory driver v1.3 [ 4.438325] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled ÿ[ 4.615305] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a ST16650V2 ;s¶6T=$ɽ¤©;s¶v´=ĽÁÔP%1D²äÍÓÉK æÑ- %1¹©;s¶5V=ÔÍê£!¬E¹)¥°? U000&ÉP%19)$%°©;s61v=¡ 0¦0¦1r2CÔJ °æÁ0424¬Ñ6/F3d °0 ÕÁ4! Much garbage deleted... ؤµ!V°ÉD¨«Í'µõ;Ðs°W¶G=dÉ©¥®5ÕV$´Ô¥½Y§ ³°&V%jê;Ðs1&·Ë=t²E%²ÑiÑ)¤D!6f¸ÕêLoading, please wait... PuTTYPuTTYPuTTYBegin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... PuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYdone. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. If anyone can point me in the right direction to understand this, that would be great. I think the repeated 'PuTTY' strings result from control characters being sent to the terminal, which is PuTTY. It's answerback string is 'PuTTY' by default. Thanks, Neil Baylis