...@xenomai.org]
Enviado el: 13 July 2012 18:48
Para: Jorge Ramirez Ortiz, HCL Europe
CC: Jan Kiszka; xenomai@xenomai.org
Asunto: Re: [Xenomai] BUG: Unhandled exception over domain Xenomai - switching
to ROOT
On 07/13/2012 06:27 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Please can we go b
On 07/13/2012 06:27 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Please can we go back and reframe the discussion?
>
> But first I'll reiterate: do ignore the marginal issue I had with the
> framework (I ported and went over 44,785 lines of ANSI-C(kernel/user)
> and 1995 lines of C++ code in just
On 07/13/2012 01:24 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Yes it does: the caller ignores upfront whether the call will be
> handled in realtime or non-realtime context by the driver. The client
> (of course!) can/should (it doesn't really matter for the sake of the
> argument) take the adeq
...@siemens.com]
Enviado el: 13 July 2012 12:59
Para: Jorge Ramirez Ortiz, HCL Europe
CC: Philippe Gerum; xenomai@xenomai.org
Asunto: Re: [Xenomai] BUG: Unhandled exception over domain Xenomai - switching
to ROOT
[please don't top-post]
On 2012-07-13 13:24, Jorge Ramirez Ortiz, HCL Europe
On 07/13/2012 01:24 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Yes it does: the caller ignores upfront whether the call will be
> handled in realtime or non-realtime context by the driver. The client
> (of course!) can/should (it doesn't really matter for the sake of the
> argument) take the adeq
[please don't top-post]
On 2012-07-13 13:24, Jorge Ramirez Ortiz, HCL Europe wrote:
> Yes it does: the caller ignores upfront whether the call will be handled in
> realtime or non-realtime context by the driver.
> The client (of course!) can/should (it doesn't really matter for the sake of
> the
t_queue_t *curr, *next;
>
> +ipipe_check_context(ipipe_root_domain);
>
> +
>
> list_for_each_entry_safe(curr, next, &q->task_list, task_list) {
>
> unsigned flags = curr->flags;
>
> At any rate, you should not expect the system to help you getting away
>
> with viol
etails and the patch.
-Mensaje original-
De: Philippe Gerum [mailto:r...@xenomai.org]
Enviado el: 13 July 2012 10:34
Para: Jorge Ramirez Ortiz, HCL Europe
CC: Gilles Chanteperdrix; xenomai@xenomai.org
Asunto: Re: [Xenomai] BUG: Unhandled exception over domain Xenomai -
switching to ROOT
On 07/12/
13 July 2012 10:34
Para: Jorge Ramirez Ortiz, HCL Europe
CC: Gilles Chanteperdrix; xenomai@xenomai.org
Asunto: Re: [Xenomai] BUG: Unhandled exception over domain Xenomai - switching
to ROOT
On 07/12/2012 11:29 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Hi Gilles
>
> Information an
edded developer needs. And RTDM has been a great addition.
thanks
Jorge
From: Gilles Chanteperdrix [gilles.chanteperd...@xenomai.org]
Sent: 12 July 2012 09:31
To: Jorge Ramirez Ortiz, HCL Europe
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] BUG: Unhandled
On 07/12/2012 11:29 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
[ 242.962195] BUG: Unhandled exception over domain Xenomai at 0x892160 -
switching to ROOT
Weird message, I can not seem to find it in xenomai sources. Anyway the
messa
From: Gilles Chanteperdrix [gilles.chanteperd...@xenomai.org]
Sent: 12 July 2012 09:31
To: Jorge Ramirez Ortiz, HCL Europe
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] BUG: Unhandled exception over domain Xenomai - switching
to ROOT
On 07/12/2012 10:16 AM, Jorge Ra
On 07/12/2012 10:16 AM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Thanks Gilles. Yes unfortunately I cant recompile this kernel so I
> was wondering about the system context of this fault within Xenomai.
> BTW how come the stack frame is not printed by default.
Because it may not be safe to use sh
]
Sent: 12 July 2012 01:21
To: Jorge Ramirez Ortiz, HCL Europe
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] BUG: Unhandled exception over domain Xenomai - switching
to ROOT
On 07/11/2012 08:10 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Please could I get some background with respect of
On 07/11/2012 08:10 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Please could I get some background with respect of the possible causes of
> this message? I have read it might be related to __copy_to/from user but I
> have already validated that path in the driver. Must be something else.
> Also,
Please could I get some background with respect of the possible causes of this
message? I have read it might be related to __copy_to/from user but I have
already validated that path in the driver. Must be something else.
Also, I am OK to assume that the system is not reliable after this event.
th
16 matches
Mail list logo
