From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Austin Schuh <austin@peloton-tech.com>,
Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org
Subject: Re: Stuck vcan
Date: Tue, 11 Mar 2014 21:56:57 +0100 [thread overview]
Message-ID: <531F7899.3010205@pengutronix.de> (raw)
In-Reply-To: <CANGgnMbtfaowdGjVRbQ9L8TJBKmbAaNxjApPsc=JDM7e28U8LA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]
On 03/11/2014 09:37 PM, Austin Schuh wrote:
> I'm not trying to cause problems ;)
:D
> Neither of those helped.
>
> # ifconfig vcan0
> vcan0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> UP RUNNING NOARP MTU:16 Metric:1
> RX packets:428406 errors:0 dropped:0 overruns:0 frame:0
> TX packets:428406 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:3427248 (3.2 MiB) TX bytes:3427248 (3.2 MiB)
>
> # ip link show vcan0
> 17: vcan0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc noqueue state UNKNOWN
> mode DEFAULT
> link/can
>
> # ifconfig vcan0
> vcan0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> UP RUNNING NOARP MTU:16 Metric:1
> RX packets:1400094 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1400094 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:10
> RX bytes:11200752 (10.6 MiB) TX bytes:11200752 (10.6 MiB)
>
> # ip link show vcan0
> 17: vcan0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc noqueue state UNKNOWN
> mode DEFAULT qlen 10
> link/can
>
> Both times, I get the following.
>
> Mar 11 13:28:58 aschuh-peloton kernel: [96229.460901] Dead loop on
> virtual device vcan0, fix it urgently!
> Mar 11 13:28:59 aschuh-peloton kernel: [96230.313875] Dead loop on
> virtual device vcan0, fix it urgently!
> Mar 11 13:28:59 aschuh-peloton kernel: [96230.319494] Dead loop on
> virtual device vcan0, fix it urgently!
> Mar 11 13:29:00 aschuh-peloton kernel: [96231.072617] Dead loop on
> virtual device vcan0, fix it urgently!
>
> Luckily, it is easy to reproduce. I have some trivial code which
> sends out 10,000 msgs/sec on the vcan. I run 3+ copies of the code on
> a dual core machine with hyperthreads enabled. More parallel sends
> should cause it to occur more frequently.
Can you share the code?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]
next prev parent reply other threads:[~2014-03-11 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 0:22 Stuck vcan Austin Schuh
2014-03-11 7:05 ` Oliver Hartkopp
2014-03-11 20:37 ` Austin Schuh
2014-03-11 20:56 ` Marc Kleine-Budde [this message]
2014-03-11 21:54 ` Austin Schuh
2014-03-11 21:29 ` Oliver Hartkopp
2014-03-11 21:55 ` Austin Schuh
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=531F7899.3010205@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=austin@peloton-tech.com \
--cc=linux-can@vger.kernel.org \
--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.