From: "Nameer Yarkon" <nameer.yarkon@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serial problem and request for guidance..
Date: Wed, 18 Jun 2008 00:33:21 +0300 [thread overview]
Message-ID: <bec9a5870806171433gf74e251m6742e066960d6ab4@mail.gmail.com> (raw)
In-Reply-To: <20080616130353.1b80fdd0@lxorguk.ukuu.org.uk>
On Mon, Jun 16, 2008 at 3:03 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> Some of my serial rx data gets lost.
>
> Which hardware ?
It's a range of platforms/kernel versions and scenarios.
Currently it happens with a bluetooth device connected to standard UART
on ARM (OMAP) with an old 2.6.14 kernel, but only when I enable the
debug macros of the line discipline code (hci_h4, hci_ldisc,..).
When a big chunk of data arrives, more than
half of it is lost. even on 115200. But when I turn of the debug macros (BT_DBG
macros which are simply a bunch of prinks) the problem disappears. So I suspect
there are some nasty timing issues which lead to data loss.
I encountered similar problems last year even on a PC, with pre 2.6.21 kernels
(around 2.6.19 or even earlier IIRC) but it was all gone with 2.6.21 and 2.6.22.
Currently I have totally different machines, and these devices tend now to come
with USB-to-serial connectors so I'm not quite sure about up-to-date
kernels yet.
All I can say is that it is nasty and very hard to debug, and I'm not quite sure
how can I debug it as I find the serial/tty subsystems a bit perplexing.
I know this is not necessarily relevant to the tip of the kernel, and it still
lacks many details, but any guidance towards how can I debug it will
be much appreciated. If I will successfully reproduce it with a current
kernel I promise a full and detailed bug report.
Thank you for your time and patience !
Nameer.
next prev parent reply other threads:[~2008-06-17 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 12:14 Nameer Yarkon
2008-06-16 12:03 ` Alan Cox
2008-06-17 21:33 ` Nameer Yarkon [this message]
2008-06-17 21:38 ` Alan Cox
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=bec9a5870806171433gf74e251m6742e066960d6ab4@mail.gmail.com \
--to=nameer.yarkon@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®