On 11/21/19 4:52 PM, Jan Kiszka wrote:
> On 21.11.19 16:31, Philippe Gerum wrote:
>> On 11/19/19 6:39 PM, Philippe Gerum wrote:
>>> On 11/19/19 5:46 PM, Philippe Gerum via Xenomai wrote:
On 11/18/19 4:13 PM, Lange Norbert via Xenomai wrote:
> Hello,
>
> Here's one of my deadlocks,
On 21.11.19 16:31, Philippe Gerum wrote:
On 11/19/19 6:39 PM, Philippe Gerum wrote:
On 11/19/19 5:46 PM, Philippe Gerum via Xenomai wrote:
On 11/18/19 4:13 PM, Lange Norbert via Xenomai wrote:
Hello,
Here's one of my deadlocks, the output seems interleaved from 2 concurrent
dumps,
I ran the
On 11/19/19 6:39 PM, Philippe Gerum wrote:
> On 11/19/19 5:46 PM, Philippe Gerum via Xenomai wrote:
>> On 11/18/19 4:13 PM, Lange Norbert via Xenomai wrote:
>>> Hello,
>>>
>>> Here's one of my deadlocks, the output seems interleaved from 2 concurrent
>>> dumps,
>>> I ran the crashlog through
On 11/19/19 5:46 PM, Philippe Gerum via Xenomai wrote:
> On 11/18/19 4:13 PM, Lange Norbert via Xenomai wrote:
>> Hello,
>>
>> Here's one of my deadlocks, the output seems interleaved from 2 concurrent
>> dumps,
>> I ran the crashlog through decode_stacktrace.sh.
>>
>
> Ok, I can reproduce this
On 11/18/19 4:13 PM, Lange Norbert via Xenomai wrote:
> Hello,
>
> Here's one of my deadlocks, the output seems interleaved from 2 concurrent
> dumps,
> I ran the crashlog through decode_stacktrace.sh.
>
Ok, I can reproduce this one, including in a vm. The symptom can be either a
lockup, or
> -Original Message-
> From: Jan Kiszka
> Sent: Dienstag, 19. November 2019 07:51
> To: Lange Norbert ; Xenomai
> (xenomai@xenomai.org)
> Subject: Re: Deadlock during debugging
>
> NON-ANDRITZ SOURCE: BE CAUTIOUS WITH CONTENT, LINKS OR
> ATTACHMENTS.
>
On 18.11.19 18:31, Lange Norbert wrote:
-Original Message-
From: Jan Kiszka
Sent: Montag, 18. November 2019 18:22
To: Lange Norbert ; Xenomai
(xenomai@xenomai.org)
Subject: Re: Deadlock during debugging
NON-ANDRITZ SOURCE: BE CAUTIOUS WITH CONTENT, LINKS OR
ATTACHMENTS
One more,
Note that there seem to be quite different reports, from a recursive fault to
some threads getting marked as "runaway".
I can reproduce the issue now easily, but its proprietary software I cant reach
around.
Norbert
[ 226.354729] I-pipe: Detected stalled head domain, probably
New crash, same thing with ipipe panic trace (the decoded log does not add
information to the relevant parts).
Is the dump_stack function itself trashing the stack?
[ 168.411205] [Xenomai] watchdog triggered on CPU #1 -- runaway thread 'main'
signaled
[ 209.176742] [ cut here
