linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobias Arp" <tobiasarp@gmx.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-serial@vger.kernel.org
Subject: Re: ST16C654 stoppes transmitting after a while
Date: Tue, 17 Jul 2012 12:05:21 +0200	[thread overview]
Message-ID: <20120717100521.219440@gmx.net> (raw)
In-Reply-To: <20120717105229.17b578a5@pyramind.ukuu.org.uk>

I run kernel 3.2. Upgrading to a newer kernel would be not se easy at the moment.

I am not sure how to check if this change is really lost.

-------- Original-Nachricht --------
> Datum: Tue, 17 Jul 2012 10:52:29 +0100
> Von: Alan Cox <alan@lxorguk.ukuu.org.uk>
> An: "Tobias Arp" <tobiasarp@gmx.de>
> CC: linux-serial@vger.kernel.org
> Betreff: Re: ST16C654 stoppes transmitting after a while

> > I found out that the hw_stopped flag is set to 1 but not set to 0 again
> although CTS is set (measuring with the oscilloscope and reading out the
> modem status register are confirming this / i modified the
> serial8250_get_mctrl function to print out these values).
> > 
> > It seems to me that an CTS change (UART_MSR_DCTS) is lost.
> > Could this cause this behaviour?
> 
> Possibly you'd need to instrument your kernel as well to prove it. It
> could also be a race in the kernel drivers somewhere. We certainly had
> those in old kernels here and there.
>  
> > Any suggestions for a workaround are appreciated.
> 
> What kernel are you running ?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-serial" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-07-17 10:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  7:43 ST16C654 stoppes transmitting after a while Tobias Arp
2012-07-17  9:52 ` Alan Cox
2012-07-17 10:05   ` Tobias Arp [this message]
2012-07-17 11:21     ` Alan Cox
2012-07-17 11:36       ` Tobias Arp
2012-07-17 16:38         ` Alan Cox
2012-07-18  6:37           ` Tobias Arp
2012-07-18  7:45             ` Tobias Arp
2012-07-18 11:08               ` Alan Cox
2012-07-18 11:16                 ` Tobias Arp
2012-07-20  4:25             ` Tobias Arp
2012-07-20 10:10             ` Tobias Arp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120717100521.219440@gmx.net \
    --to=tobiasarp@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-serial@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).