linux-kernel - Re: serial flow control appears broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 26 Jul 2007 14:34:20 +0200
From:	Uwe Kleine-König 
	<ukleinek@...ormatik.uni-freiburg.de>
To:	Lee Howard <faxguy@...ardsilvan.com>
Cc:	linux-serial@...r.kernel.org, tytso@....edu, rmk@....linux.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: serial flow control appears broken

Hello,

> This is evidenced in hardware flow control by a little LED labeled "RTS" 
> that is on the external modem.  This LED lights up when pin 7 of the DB9 
> serial connection is given +12Vdc current (signalling "RTS" is on - that 
> the host can accept data).  The LED goes dark when the current is 
> removed (signalling that the host cannot accept data).  This "RTS" LED 
> never flickers at all, as it should, when receiving these bursts of data 
> - the LED stays lit as long as the serial cable is connected to the 
> host... and yet I will see those "input overrun" messages.  Thus, it 
> seems quite clear that the Linux serial tty driver is not deasserting 
> RTS as it should in hardware flow control.  (And probably the analogous 
> problem exists in software flow control, too.)
I don't know the relevant timings for problem, but just to be sure that
your prerequisites are correct:  How did you check that the LED stays
lit all the time?  Just from looking might not be accurate.  You might
want to mesure the signal with an oscilloscope.

Just my 0.02¢
Uwe

-- 
Uwe Kleine-König

fib where fib = 0 : 1 : zipWith (+) fib (tail fib)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/