linux-kernel - Re: 2.6.25.3: serial problem (minicom)

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]

Message-Id: <20080515202300.4d0465ac.akpm@linux-foundation.org>
Date:	Thu, 15 May 2008 20:23:00 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Chris Rankin <rankincj@...oo.com>
Cc:	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)

On Thu, 15 May 2008 20:06:23 +0100 (BST) Chris Rankin <rankincj@...oo.com> wrote:

> I have two Linux boxes connected by a null-modem cable between their serial ports; one box exports
> a serial console, which the other reads using the minicom program. However, I have noticed that
> minicom can no longer use the serial console when it is running on a 2.6.25.3 kernel, although it
> works fine running on a 2.6.24.4 kernel.
> 
> Specifically, with minicom running on 2.6.25.3, the console does not accept keystrokes although it
> does receive the boot log from the remote machine.
> 
> The serial console is being exported by a 2.6.25.3 kernel, and appears to be working correctly.

We did make some changes to serial_core.c in that timeframe which might
have caused this, such as:

Author: Russell King <rmk+lkml@....linux.org.uk>  2008-02-04 22:27:52
Committer: Linus Torvalds <torvalds@...dy.linux-foundation.org>  2008-02-05 09:44:10
Parent: 9d778a69370cc1b643b13648df971c83ff5654ef (serial: avoid waking up closed serial ports on resume)
Child:  6d4d67beb963de8865499781b8523e5b683819c3 (serial: speed setup failure reporting)
Branches: many (89)
Follows: v2.6.24
Precedes: v2.6.25-rc1

    serial: avoid stalling suspend if serial port won't drain


Author: Yinghai Lu <Yinghai.Lu@....COM>  2008-02-04 22:27:46
Committer: Linus Torvalds <torvalds@...dy.linux-foundation.org>  2008-02-05 09:44:09
Parent: 149b36eae2ab6aa6056664f4bc461f3d3affc9c1 (serial: stop passing NULL to functions that expect data)
Child:  9d778a69370cc1b643b13648df971c83ff5654ef (serial: avoid waking up closed serial ports on resume)
Branches: many (89)
Follows: v2.6.24
Precedes: v2.6.25-rc1

    serial: keep the DTR setting for serial console.
    

But I don't recall seeing any other reports of this and there's not
really anyone who is actively working on the serial drivers.

All of which builds up to the dreaded....  would you be able to perform
a bisection search to work out which commit caused this?
http://www.kernel.org/doc/local/git-quick.html has instructions.

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