On Sun, Dec 27, 2015 at 09:32:45PM +0000, Tati Chevron wrote: > On Sun, Dec 27, 2015 at 07:04:10PM +0000, Stuart Henderson wrote: > >On 2015-12-27, Ted Unangst <t...@tedunangst.com> wrote: > >>LÉVAI Dániel wrote: > >>>So I guess it didn't panic, but just dropped to ddb from console, > >>>because ddb.console was set to 1. Is there something sent via the serial > >>>console that induces this? If I set ddb.console to 0 this doesn't > >>>happen, but I'm curious as to what is happening and if I can avoid it. > >> > >>a "break" was sent. or at least received. i've seen extra breaks sent when > >>trying to disconnect too. i mostly solved it by not disconnecting... > > > >"break" is just a signal low for longer than the time taken to send a > >normal character (plus framing), it's not that hard to have one detected > >when it's not intended. First I'd try setting things up to use a > >different port speed, especially if it's currently at a high speed > >then try slowing it down. If that doesn't help then I'd try a > >different usb/rs232 adapter. > > Possibly a shorter or better quality cable may help as well, especially > if it's a long cable run.
I've seen BREAK's when powering down the maching holding the usb-to-serial dongle. Just unplugging the dongle first helped. /Alexander
