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 13:36:03 +0200 [thread overview]
Message-ID: <20120717113603.9830@gmx.net> (raw)
In-Reply-To: <20120717122140.075aa7ae@pyramind.ukuu.org.uk>
This is a single core arm processor (Cirrus EP9315), could this race condition happen in this case?
But i have CONFIG PRREMPT set. Shall i take a stab on it by switching it to off?
Tobias
-------- Original-Nachricht --------
> Datum: Tue, 17 Jul 2012 12:21:40 +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
> On Tue, 17 Jul 2012 12:05:21 +0200
> "Tobias Arp" <tobiasarp@gmx.de> wrote:
>
> > I run kernel 3.2. Upgrading to a newer kernel would be not se easy at
> the moment.
>
> 3.2 is certainly new enough that it should have all the major fixes in.
>
> > I am not sure how to check if this change is really lost.
>
> With a debugger dump the state of the port structures one the hung port
> once it has hung. Something like Red Hat's systemtap might also be very
> helpful in doing this kind of monitoring.
>
> My first guess would be that you hit a race between the port stopping on
> one processor and the flow control event on another. We have one known
> case there still being debugged but I thought it could only be hit if you
> were using ttys in low latency mode.
>
> Alan
next prev parent reply other threads:[~2012-07-17 11:36 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
2012-07-17 11:21 ` Alan Cox
2012-07-17 11:36 ` Tobias Arp [this message]
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=20120717113603.9830@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).