From: "Tobias Arp" <tobiasarp@gmx.de>
To: Tobias Arp <tobiasarp@gmx.de>, alan@lxorguk.ukuu.org.uk
Cc: linux-serial@vger.kernel.org
Subject: Re: ST16C654 stoppes transmitting after a while
Date: Fri, 20 Jul 2012 06:25:29 +0200 [thread overview]
Message-ID: <20120720042529.19870@gmx.net> (raw)
In-Reply-To: <20120718063704.130240@gmx.net>
BTW:
all interfaces work fine with our old kernel version 2.6.15.
Tobias
-------- Original-Nachricht --------
> Datum: Wed, 18 Jul 2012 08:37:04 +0200
> Von: "Tobias Arp" <tobiasarp@gmx.de>
> An: Alan Cox <alan@lxorguk.ukuu.org.uk>
> CC: linux-serial@vger.kernel.org
> Betreff: Re: ST16C654 stoppes transmitting after a while
> The serial links are all set up to 115200 baud.
>
> Dumping out the tty-struct when it hangs shows me this:
>
> magic: 0x5401
> name: ttyS0
> flags: 0x00000A00
> count: 1
> stopped: 0
> hw_stopped: 1
> flow_stopped: 0
> packet: 0
> low_latency: 0
> warned: 0
> ctrl_status: 0x00
> receive_room: 4095
> ...
>
> It is a little bit strange that always the null modem connection shows
> this behaviour. May be it's because it has the highest data transfer rate (all
> other connections are made by isdn modems / 1-channel isdn)?
>
>
>
>
> -------- Original-Nachricht --------
> > Datum: Tue, 17 Jul 2012 17:38:47 +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 13:36:03 +0200
> > "Tobias Arp" <tobiasarp@gmx.de> wrote:
> >
> > > This is a single core arm processor (Cirrus EP9315), could this race
> > condition happen in this case?
> >
> > In theory, otoh it ought to be quite easy to test for.
> >
> > How fast are your links - would it be fair to characterise your
> > environment as a fairly slow CPU handling a lot of fast serial links
> >
> > (just trying to understand what the likely places to look might be)
> >
> > --
> > 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
> --
> 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
next prev parent reply other threads:[~2012-07-20 4:25 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
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 [this message]
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=20120720042529.19870@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.