Re: 2.6.25.3: serial problem (minicom)

On Thu, 15 May 2008 20:06:23 +0100 (BST) Chris Rankin <rankincj@xxxxxxxxx> 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@xxxxxxxxxxxxxxxx> 2008-02-04 22:27:52
Committer: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxx> 2008-02-04 22:27:46
Committer: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Serial console access: need help
    ... > I have configured my RHEL-AS3 box to support serial console. ... > configured GRUB to send kernel messages to serial console as well added ... > minicom and have them work. ... rip minicom the hell out and use Kermit instead. ...
    (comp.os.linux.setup)
  • Re: Ultra 30 serially linked with a PC - Shutdown problem
    ... >> I had been using minicom under Linux as the serial console. ... That was the best of my recollection from over a year ago when my Sun ... now I recall that I only used the minicom break *before* Solaris had ...
    (comp.sys.sun.hardware)
  • serial8250: too much work for irq4
    ... These came while I was using minicom on serial port at 9600 bps to work ... The serial console worked fine. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Serial (RS232) communication - failing to detect stop bit
    ... Minicom is, unfortunately, also crap... ... configuration is intended for an actual modem and 'a lot of tedious ... strings and saving the modifed configuration afterwards. ... I happen to use it regularly to connect to the serial console of the ...
    (comp.os.linux.development.apps)
  • Re: [PATCH] Stop pmac_zilog from abusing 8250s device numbers.
    ... The moment you do serial console, ... Each hardware driver should just register with the ... Non-8250 serial ports, such as the multiport PCI cards from ... 'ttyS0' and to have used the ttyS0 device numbers in the first place. ...
    (Linux-Kernel)