All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Stephane Grosjean <s.grosjean@peak-system.com>,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH v4.1] can/sja1000: add support for PEAK-System PCMCIA card
Date: Fri, 17 Feb 2012 14:40:52 +0100	[thread overview]
Message-ID: <4F3E58E4.3030407@volkswagen.de> (raw)
In-Reply-To: <4F3E1F83.8020708@pengutronix.de>

On 17.02.2012 10:36, Marc Kleine-Budde wrote:
> On 02/17/2012 10:21 AM, Stephane Grosjean wrote:
>> Hi Oliver,
>>
>> I've got one (newbie) question: what is the next step? I mean, should I
>> post the same patch again but with this "Acked-by"? Or what? Should I
>> wait for any linux-can Acked-by ?
>
> No need to repost so soon. A Tested-by from Oliver under heavy load
> detaching together with the Fix unplug Patch would be fine.
>

I can confirm that with together with this patch
"[PATCH v2] can: sja1000 fix isr hang when hw is unplugged under load"

http://marc.info/?l=linux-can&m=132932474901518&w=2

there is no freeze on my Dell830 when unplugging the PEAK PCMCIA Card.

Tested-by: Oliver Hartkopp <socketcan@hartkopp.net>

Indeed i got some 'last famous CAN frames' on plug out like this:

can0  10 [8] 37 00 FF FF FF FF FF FF

while it should have been

can0  10 [8] 37 00 00 00 00 00 00 00

So the last message can contain rubbish but it doesn't freeze the machine
anymore. The behavior is now just like we discussed it :-)

I also did not get any freezes with the PEAK PCIeC anymore.

The only remaining issue with PEAK PCIeC is the locking warning about the
PCIeC LED timer lock (&card->led_timer) when i enable and start the interface
under CAN load. I do have a peak_pci v5 driver here - but in v6 only changed
the device_id table right?

To get this problem you need to connect the PCIeC to a CAN bus which is 
already having CAN traffic between at least two functional nodes.

Regards,
Oliver


  reply	other threads:[~2012-02-17 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 10:10 [PATCH v4.1] can/sja1000: add support for PEAK-System PCMCIA card Stephane Grosjean
2012-02-17  8:24 ` Dominik Brodowski
2012-02-17  9:21   ` Stephane Grosjean
2012-02-17  9:36     ` Marc Kleine-Budde
2012-02-17 13:40       ` Oliver Hartkopp [this message]
2012-02-17 14:19         ` Stephane Grosjean
2012-02-17 14:40           ` Oliver Hartkopp
2012-02-17 14:47             ` Stephane Grosjean
  -- strict thread matches above, loose matches on Subject: below --
2012-02-13 14:18 Stephane Grosjean

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=4F3E58E4.3030407@volkswagen.de \
    --to=oliver.hartkopp@volkswagen.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=s.grosjean@peak-system.com \
    --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 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.