From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Paul Lever <svjeorgia@gmail.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Subject: Re: candump error flags
Date: Sat, 08 Nov 2014 16:00:47 +0100 [thread overview]
Message-ID: <545E301F.7090708@hartkopp.net> (raw)
In-Reply-To: <CAHuoernFKhHJZKTYDc+qpbhwkrx6cWAr7vreH=Sa=FoinVG6dw@mail.gmail.com>
On 11/08/2014 03:47 PM, Paul Lever wrote:
>>> Make sure you're running a recent new kernel (v3.15 or better) as a lot
>>> of fixes went into the driver.
>>>
>>
>> E.g. the dropcount functionality emerged in Linux 2.6.33
>> So a Debian Squeeze with 2.6.32 won't make it here ...
> I am running the c_can driver with the updates to late June.
Of which kernel version?
A 2.6.32.x with security and stable patches is still no 2.6.33+
>> ps. additionally "candump -r 16000 -l can0 &" would be better :-)
> I need the timestamps.
The logfile format contains a unix timestamp (usec resolution) for every CAN
frame (and error message).
>
> With berr-reporting enabled I still don't see any messages generated
> by the -e and -d options to candump. Looking at my received data I can
> see that there are missing sequential packets.
I'll better wait for the kernel version until answering based on assumptions.
Regards,
Oliver
next prev parent reply other threads:[~2014-11-08 15:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 13:57 candump error flags Paul Lever
2014-11-07 14:13 ` Andri Yngvason
2014-11-07 14:30 ` Marc Kleine-Budde
2014-11-07 14:56 ` Oliver Hartkopp
2014-11-08 14:47 ` Paul Lever
2014-11-08 15:00 ` Oliver Hartkopp [this message]
2014-11-08 15:14 ` Paul Lever
2014-11-08 15:29 ` Oliver Hartkopp
2014-11-08 15:34 ` Paul Lever
2014-11-08 16:44 ` Oliver Hartkopp
2014-11-09 14:50 ` Paul Lever
2014-11-08 16:46 ` Marc Kleine-Budde
2014-11-09 14:52 ` Paul Lever
2014-11-09 15:01 ` Marc Kleine-Budde
2014-11-09 15:23 ` Paul Lever
2014-11-10 5:29 ` Pankajkumar Misra (RBEI/EEA2)
2014-11-13 10:20 ` mcp251x (was: Re: candump error flags) Marc Kleine-Budde
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=545E301F.7090708@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=svjeorgia@gmail.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 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.