From: Wolfgang Grandegger <wg@grandegger.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "Michael Jäntsch" <michael.jaentsch@in.tum.de>,
linux-can@vger.kernel.org
Subject: Re: [Socketcan-users] Message stalls in SocketCan Layer?
Date: Fri, 03 Feb 2012 20:41:56 +0100 [thread overview]
Message-ID: <4F2C3884.2000808@grandegger.com> (raw)
In-Reply-To: <4F2C11DF.7010707@hartkopp.net>
On 02/03/2012 05:57 PM, Oliver Hartkopp wrote:
> Hi Michael,
>
> On 03.02.2012 17:08, Michael Jäntsch wrote:
>
>
>> yes, it all started when I switched to kernel 3.0.0-15-generic. However,
>> weirdly enough there is one computer with this kernel where the problem
>> doesn't appear and two where it does. I think I will confirm this by
>> going back to an older kernel and seeing if the problem disappears.
>
>
> please consider that if it works on other machines with the same kernel that
> there could be some changes within the USB subsystem or some interrupt or
> ACPI/powersaving issues too.
>
> Going back to an older Kernel is a good check - don't know, if you also can go
> further (3.1, 3.2) with Ubuntu 11.10 too ?!?
>
> Maybe there's some USB debugging available to check whether the URB has been
> sent properly to the USB wire and if the interrupt of the USB controller
> reached the system after sending.
IIUC, he said that the time stamps indicated that the USB transfers have
happened in time. The delays occured later. That's wired, indeed.
Wolfgang.
next prev parent reply other threads:[~2012-02-03 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F29091F.4010908@in.tum.de>
[not found] ` <4F2AA5DF.9080304@grandegger.com>
2012-02-03 16:08 ` [Socketcan-users] Message stalls in SocketCan Layer? Michael Jäntsch
2012-02-03 16:57 ` Oliver Hartkopp
2012-02-03 19:41 ` Wolfgang Grandegger [this message]
2012-02-13 10:00 ` Michael Jäntsch
2012-02-13 10:45 ` Wolfgang Grandegger
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=4F2C3884.2000808@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-can@vger.kernel.org \
--cc=michael.jaentsch@in.tum.de \
--cc=socketcan@hartkopp.net \
/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).