On 2017/07/03 21:05, Hrvoje Popovski wrote:
> Hi all,
> 
> i'm having two firewalls fw1 and fw2 and on fw1 i'm sending console
> output to com0.
> 
> root@fw1:~
> # cat /etc/boot.conf
> stty com0 115200
> set tty com0
> 
> root@fw1:~
> # cat /etc/ttys | grep tty00
> tty00   "/usr/libexec/getty std.115200" vt220   on  secure
> 
> 
> on fw2 i'm using "cu -s 115200" to play with wonderful net MP stuff on
> fw1 :)
> 
> on fw1 in sysctl i'm having ddb.console=1 ... and here's funny part...
> 
> when i reboot fw2 and while fw2 is booting at some point it seems that
> fw2 send some break sequence to fw1 and fw1 drops to ddb prompt.
> when i put ddb.console=0 everything seems fine ...
> 
> i don't know is this feature or bug :)

The phrase "break sequence" is often used, but it's a bit of a misnomer.
When a serial port is connected but not actively transmitting data the tx
line is usually held high. A "break" is when that line is low for more 
than a frame duration (the length of which depends on the port speed).

If the tx line is only being held low for a short time during reboot,
I wonder if you might get lucky by selecting a lower port speed.
(Avoid going too low, especially if you have enabled extra debug
messages, or it's likely to interfere with other kernel operations
while it's printing to the console.)

Reply via email to