From: Roland Tollenaar <rwatollenaar@domain.hid>
To: Sebastian Smolorz <ssm@domain.hid>, Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] CAN errors and real-time behaviour (IRQ raise forever and may lock system)
Date: Mon, 05 Mar 2007 13:16:25 +0100 [thread overview]
Message-ID: <45EC0A19.2060708@domain.hid> (raw)
In-Reply-To: <E1HOBsC-0004y8-Rb@domain.hid>
Hi,
Sebastian Smolorz wrote:
> Roland Tollenaar wrote:
>> IMHO it would be nice if the warning did get into the message buffer
>> (assuming that they cannot -easily- be expelled elsewhere) but that the
>> overflowing does not result in triggering non-application
>
> You mean the log printing? Simply don't set CONFIG_XENO_DRIVERS_CAN_DEBUG.
Aha! This sounds like something that may sort out my little problem.
Where do I set this parameter? I certainly did not turn it on so it must
be in some default configuration. Is it on compiling the kernel? Where?
how do I unset it?
Thanks.
Roland
>
>> warning or
>> error handeling mechanisms.
>
> Error handling is the duty of your application. The CAN stack doesn't do this
> for you.
>
> --
> Sebastian
>
next prev parent reply other threads:[~2007-03-05 12:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 14:09 [Xenomai-help] CAN errors and real-time behaviour roland Tollenaar
2007-03-05 8:49 ` Stéphane ANCELOT
2007-03-05 9:26 ` Roland Tollenaar
2007-03-05 10:39 ` [Xenomai-help] CAN errors and real-time behaviour (IRQ raise forever and may lock system) Stéphane ANCELOT
2007-03-05 11:26 ` Sebastian Smolorz
2007-03-05 11:42 ` Roland Tollenaar
2007-03-05 12:01 ` Sebastian Smolorz
2007-03-05 12:16 ` Roland Tollenaar [this message]
2007-03-05 12:48 ` Sebastian Smolorz
2007-03-05 13:13 ` Roland Tollenaar
2007-03-05 14:57 ` Stéphane ANCELOT
2007-03-05 14:42 ` Sebastian Smolorz
2007-03-05 17:02 ` Stéphane ANCELOT
2007-03-06 9:36 ` Sebastian Smolorz
2007-03-10 20:53 ` Wolfgang Grandegger
2007-03-14 11:38 ` [Xenomai-help] RT-Socket-CAN bus error handling (was CAN errors and real-time behaviour (IRQ raise forever and may lock system)) Wolfgang Grandegger
2007-03-14 12:51 ` Sebastian Smolorz
2007-03-14 13:18 ` Wolfgang Grandegger
2007-03-14 13:24 ` Sebastian Smolorz
2007-03-17 11:56 ` Wolfgang Grandegger
2007-03-18 10:22 ` Jan Kiszka
2007-03-18 11:33 ` Wolfgang Grandegger
2007-03-18 20:59 ` Jan Kiszka
2007-03-19 8:21 ` Sebastian Smolorz
2007-03-19 8:50 ` Sebastian Smolorz
2007-03-19 11:35 ` Wolfgang Grandegger
2007-03-19 11:46 ` Sebastian Smolorz
2007-03-19 13:05 ` Jan Kiszka
2007-03-19 20:44 ` Wolfgang Grandegger
2007-03-19 21:19 ` Wolfgang Grandegger
2007-03-19 22:25 ` Jan Kiszka
2007-03-20 6:53 ` Wolfgang Grandegger
2007-03-19 8:54 ` Wolfgang Grandegger
2007-03-19 16:48 ` Stéphane ANCELOT
2007-03-19 16:56 ` Sebastian Smolorz
2007-03-19 17:33 ` Jan Kiszka
2007-03-19 8:49 ` Stéphane ANCELOT
2007-03-19 8:30 ` Wolfgang Grandegger
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=45EC0A19.2060708@domain.hid \
--to=rwatollenaar@domain.hid \
--cc=Xenomai-help@domain.hid \
--cc=rolandtollenaar@domain.hid \
--cc=ssm@domain.hid \
/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.