From: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
To: kime-Z4QKGCRq86k@public.gmane.org
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CAN State Information
Date: Fri, 09 Dec 2011 09:19:06 +0100 [thread overview]
Message-ID: <4EE1C47A.7080507@grandegger.com> (raw)
In-Reply-To: <4EE1C3BF.70104-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
On 12/09/2011 09:15 AM, Wolfgang Grandegger wrote:
> On 12/09/2011 09:03 AM, kime-Z4QKGCRq86k@public.gmane.org wrote:
>> I plan to spend some time today tracking down the problem. I am most curious to discover if there is a problem in the msg returned from send_dump_request().
>>
>> $ sudo ./canconfig can0 state
>> can0 state: STOPPED
>> $ sudo ./canconfig can1 state
>> can1 state: STOPPED
>> $ "
>> can2: failed to get state
>> $ sudo ./canconfig can3 state
>> can3: failed to get state
>
> OK, what does strace tell you. Is there a system call failing with "-1"?
> Also ftrace could give some hint (assuming that ftrace and function
> tracing is enabled in you kernel):
>
> # mount -tdebugfs none /sys/kernel/debug/
> # cd /sys/kernel/debug/tracing/
> # echo function > current_tracer
> # echo "can_*" > set_ftrace_filter
> # cat set_ftrace_filter
> # echo 0 > trace
# echo 1 > tracing_on
might also be necessary (usually it on by default).
Wolfgang.
next prev parent reply other threads:[~2011-12-09 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166589D0B9DD2547A1319599B9BADA1FC1960C@vsv-exchange.ixxat.intranet.priv>
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1960C-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-06 15:26 ` CAN State Information Wolfgang Grandegger
[not found] ` <4EDE342E.8030102-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-06 18:54 ` Wolfram Sang
2011-12-08 8:43 ` kime-Z4QKGCRq86k
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1981F-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-08 19:15 ` Wolfgang Grandegger
2011-12-09 8:03 ` kime
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC19968-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-09 8:15 ` Wolfgang Grandegger
[not found] ` <4EE1C3BF.70104-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-09 8:19 ` Wolfgang Grandegger [this message]
[not found] ` <4EE1C47A.7080507-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-09 8:45 ` kime-Z4QKGCRq86k
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1998A-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-09 9:00 ` Wolfgang Grandegger
2011-12-09 13:41 ` kime
2011-12-09 14:49 ` Wolfgang Grandegger
[not found] ` <4EE2200E.4060403-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-12 10:21 ` kime-Z4QKGCRq86k
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=4EE1C47A.7080507@grandegger.com \
--to=wg-5yr1bzd7o62+xt7jha+gda@public.gmane.org \
--cc=kime-Z4QKGCRq86k@public.gmane.org \
--cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).