From: Stephane Grosjean <s.grosjean@peak-system.com>
To: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
Cc: linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: About can/usb v4 patches serie
Date: Tue, 07 Feb 2012 14:43:58 +0100 [thread overview]
Message-ID: <4F312A9E.60506@peak-system.com> (raw)
In-Reply-To: <4F31238A.9060305@volkswagen.de>
Le 07/02/2012 14:13, Oliver Hartkopp a écrit :
> On 07.02.2012 11:01, Stephane Grosjean wrote:
>
>
>> Meanwhile, I have a look to the deadlock issue in the pcmcia driver
>> timer
>> function first...
>
> Yes. Just to be sure this eject problem can generally be solved i
> replaced the PEAK PCMCIA card with the EMS PCMCIA card in my setup,
> where i only get two removal notifications when pulling the card under
> full rx load.
>
Sorry for the typo but the above issue I talked about concerns the
peak_pci driver and the PCIeC card, not the PCMCIA driver!
So please confirm:
- pciec iissue: deadlock occurs during 1xMbps traffic, afaik it occurs
with the led timer
- but what about this above "eject" issue, regarding the PCMCIA cards
and these removal notifications? Can you give me more explanations, please?
> Just one remark upon the USB driver:
>
> I did a
>
> cangen -g0 -i can5
>
> to flood the USB-Pro adapter with outgoing traffic.
>
> When doing an "ifconfig can5 down" i get:
>
>
> peak_usb 2-2:1.0: can5: Tx URB aborted (-2)
>
> ten times (what is probably the netdev queue length)
>
something like this, yes... I forgot that.
Regards,
Stéphane
--
PEAK-System Technik GmbH, Otto-Roehm-Strasse 69, D-64293 Darmstadt
Geschaeftsleitung: A.Gach/U.Wilhelm,St.Nr.:007/241/13586 FA Darmstadt
HRB-9183 Darmstadt, Ust.IdNr.:DE 202220078, WEE-Reg.-Nr.: DE39305391
Tel.+49 (0)6151-817320 / Fax:+49 (0)6151-817329, info@peak-system.com
next prev parent reply other threads:[~2012-02-07 13:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 15:12 [PATCH v2] can/sja1000: add support for PEAK-System PCMCIA card Stephane Grosjean
2012-02-03 16:44 ` Oliver Hartkopp
2012-02-06 16:03 ` Oliver Hartkopp
2012-02-06 17:05 ` Sven Geggus
2012-02-06 17:41 ` Oliver Hartkopp
[not found] ` <4F30F691.5070307@peak-system.com>
2012-02-07 13:13 ` About can/usb v4 patches serie Oliver Hartkopp
2012-02-07 13:43 ` Stephane Grosjean [this message]
2012-02-07 13:51 ` Oliver Hartkopp
2012-02-15 14:41 ` Stephane Grosjean
2012-02-15 20:05 ` Oliver Hartkopp
2012-02-10 11:00 ` can/sja1000: potential issue in sja1000.c? Stephane Grosjean
2012-02-10 11:16 ` Marc Kleine-Budde
2012-02-10 11:44 ` Wolfgang Grandegger
2012-02-10 15:32 ` Sebastian Haas
2012-02-10 15:37 ` Marc Kleine-Budde
2012-02-10 11:56 ` Wolfgang Grandegger
2012-02-10 15:39 ` Oliver Hartkopp
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=4F312A9E.60506@peak-system.com \
--to=s.grosjean@peak-system.com \
--cc=linux-can@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
/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.