From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "Paul Thomas" <pthomas8589@gmail.com>,
linux-can@vger.kernel.org,
"Stéphane Grosjean" <s.grosjean@peak-system.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
support@peak-system.com
Subject: Re: peak_usb: urb aborted
Date: Fri, 8 Apr 2022 20:45:02 +0200 [thread overview]
Message-ID: <c2e2c7b0-cdfb-8eb0-9550-0fb59b5cd10c@hartkopp.net> (raw)
In-Reply-To: <CAD56B7dMg073f56vfaxp38=dZiAFU0iCn6kmDGiNcNtCijyFoA@mail.gmail.com>
On 08.04.22 18:35, Paul Thomas wrote:
> Folks,
>
> I'm using a PCAN-USB adapter, and it seems to have a lot of trouble
> under medium load. I'm getting these urb aborted messages.
> [125054.082248] peak_usb 3-2.4.4:1.0 can0: Rx urb aborted (-71)
> [125077.886850] peak_usb 3-2.4.4:1.0 can0: Rx urb aborted (-32)
As I run the same hardware here it is very likely that you have a faulty
CAN bus setup with
- wrong bitrate setting / sample points / etc
- wrong or no termination
- missing or wrong configured (other) CAN nodes
I added the maintainer of the PEAK USB adapter (Stephane) to the
recipient list.
Having the linux-can mailing list and Stephane in the recipient list is
sufficient to answer the above details.
Regards,
Oliver
>
> Is there anything that can be done about this? This is very
> frustrating because it makes the USB adapter very difficult to use as
> a reliable partner of an embedded CAN device.
>
> I'm using Ubuntu with 5.4.0-107-generic. Any help would be appreciated.
>
> -Paul
next prev parent reply other threads:[~2022-04-08 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 16:35 Paul Thomas
2022-04-08 18:45 ` Oliver Hartkopp [this message]
2022-04-11 13:07 ` Stéphane Grosjean
2022-04-14 18:21 ` Paul Thomas
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=c2e2c7b0-cdfb-8eb0-9550-0fb59b5cd10c@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pthomas8589@gmail.com \
--cc=s.grosjean@peak-system.com \
--cc=support@peak-system.com \
--cc=wg@grandegger.com \
/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®