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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 17 May 2008 20:46:27 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"Jay Cliburn" <jacliburn@...lsouth.net>
Cc:	"Chris Rankin" <rankincj@...oo.com>, linux-kernel@...r.kernel.org,
	linux-serial@...r.kernel.org,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: 2.6.25.3: serial problem (minicom)

On Sat, May 17, 2008 at 5:10 PM, Jay Cliburn <jacliburn@...lsouth.net> wrote:
> On Sat, 17 May 2008 15:49:08 +0100 (BST)
> Chris Rankin <rankincj@...oo.com> wrote:
>
>> Does yours still work if you raise the baud rate to 115200?
>
> No, but I also get garbage characters and a generally unusable logging
> device.  57600 is slightly better, but not much.  I remember going
> through this progressive reduction in baud rate a long time ago,
> trying to find a speed that works reliably, which is why I settled on
> 38400. I get unpredictable results for anything higher.

If you have a digital oscilloscope available it would be very
interesting to measure whether the timing of the signals sent out on
the Tx line is correct. Small deviations between the frequency of the
clock crystal that drives a UART and the value configured via
setserial can cause trouble with serial communication (baud_base must
be configured to UART clock crystal frequency / 16).

# setserial -g -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test

Bart.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ