Weirdest problem with serial console

jinjer

Renowned Member
Oct 4, 2010
204
7
83
Hi,

Want to hear the weirdest problem I've had so far with proxmox ?

I've been running serial consoles on my servers for more than I can remember.

What happens is that when the serial console is enabled (linux ... console=tty0 console=ttyS0,115200n8) I have a pause during the boot process. As soon I press a key on the physical keyboard, the boot proceeds and succeeds.

If I press a key on the serial console, nothing happens.

If I remove the serial console (i.e. linux ... console=tty0), the boot works properly
if I only leave the serial console, It still hangs, and still requires a keypress (enter) on the physical keyboard.

This beats me... I spent the good part of today trying to replicate it to no avail.

Tried reinstalling grub, making new initrd, booting with various options.

On the console I see a bunch of characters (like when baud rate is not correct) and then I need to press enter on the keyboard.
Here are the last lines from the console, before I need to press enter to continue.
Code:
ioatdma: Intel(R) QuickData Technology Driver 4.00
ioatdma 0000:00:08.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
EDAC MC: Ver: 2.1.0 Aug  6 2013
EDAC MC0: Giving out device to 'i5000_edac.c' 'I5000': DEV 0000:00:10.0
EDAC PCI0: Giving out device to module 'i5000_edac' controller 'EDAC PCI controller': DEV '0000)
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07rh
iTCO_wdt: Found a 631xESB/632xESB TCO device (Version=2, TCOBASE=0x1060)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
input: PC Speaker as /devices/platform/pcspkr/input/input5
Intel ICH 0000:00:1e.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17
intel8x0_measure_ac97_clock: measured 50895 usecs (2453 samples)
intel8x0: clocking to 48000
done.
Setting parameters of disc: (none).
?. 
   ^[[24;4R
The "done." is the last statement print from the initrd.


ouch! Debian forums are not helpfull.
I have another upgraded server that works properly.

Any ideas are welcome :?
 
Last edited:
I have a very similar problem. On serial console, the boot pauses at exactly the same place with very similar gibberish, but I must type CTRL-C to resume, at which point it boots normally.

Did you ever find the cause?

Code:
[FONT=Menlo]INIT: version 2.88 booting[/FONT]
[FONT=Menlo]Using makefile-style concurrent boot in runlevel S.[/FONT]
[FONT=Menlo]Starting the hotplug events dispatcher: udevd.[/FONT]
[FONT=Menlo]Synthesizing the initial hotplug events...done.[/FONT]
[FONT=Menlo]Waiting for /dev to be fully populated...done.[/FONT]
[FONT=Menlo]Setting parameters of disc: (none).[/FONT]
[FONT=Menlo][/FONT]
[FONT=Menlo] ^[[12;2R[/FONT]
[FONT=Menlo]
[/FONT]
[FONT=Menlo]^CActivating swap...done.[/FONT]
 
My best guess is that a script requires access to a proper terminal (tty) eg. expects to write information of some kind or maybe testing for existence of a tty.