Re: hith latency when cpu is fully loaded

2019-11-18 Thread chensong via Xenomai
On 2019年11月19日 14:49, Jan Kiszka wrote: On 19.11.19 02:01, chensong via Xenomai wrote: Dear experts, i'm new in xenomai, i got an issue, here is the detail: Main processor architect: ARM64 phytium ft2000ahk Kernel release number: 4.14.4 cmdline:BOOT_IMAGE=/Image-tmp

Re: Deadlock during debugging

2019-11-18 Thread Jan Kiszka via Xenomai
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. On

Re: hith latency when cpu is fully loaded

2019-11-18 Thread Jan Kiszka via Xenomai
On 19.11.19 02:01, chensong via Xenomai wrote: Dear experts, i'm new in xenomai, i got an issue, here is the detail: Main processor architect: ARM64 phytium ft2000ahk Kernel release number: 4.14.4 cmdline:BOOT_IMAGE=/Image-tmp root=UUID=9fea0634-a9c9-4e9f-906c-9c36b7249822

hith latency when cpu is fully loaded

2019-11-18 Thread chensong via Xenomai
Dear experts, i'm new in xenomai, i got an issue, here is the detail: Main processor architect: ARM64 phytium ft2000ahk Kernel release number: 4.14.4 cmdline:BOOT_IMAGE=/Image-tmp root=UUID=9fea0634-a9c9-4e9f-906c-9c36b7249822 console=ttyS1,115200 earlyprintk=uart8250-32bit,0x28001000 rw

RE: Deadlock during debugging

2019-11-18 Thread Lange Norbert via Xenomai
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

RE: Deadlock during debugging

2019-11-18 Thread Lange Norbert via Xenomai
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

Deadlock during debugging

2019-11-18 Thread Lange Norbert via Xenomai
Hello, Here's one of my deadlocks, the output seems interleaved from 2 concurrent dumps, I ran the crashlog through decode_stacktrace.sh. I got to this, after enabling a breakpoint in gdb (execution did stop there), setting another breakpoint and hitting continue. [ 135.414273] CPU: 1 PID:

Re: [PATCH 3/3] boilerplate/avl: fix NULL link representation in pshared mode - take #2

2019-11-18 Thread Jan Kiszka via Xenomai
On 18.11.19 09:20, Philippe Gerum wrote: On 11/18/19 9:12 AM, Jan Kiszka wrote: On 17.11.19 12:41, Philippe Gerum via Xenomai wrote: Since zero is the offset pointing at the AVL tree anchor, it cannot be used for representing a NULL link. Use (ptrdiff_t)-1 instead. Signed-off-by: Philippe

Re: [PATCH 3/3] boilerplate/avl: fix NULL link representation in pshared mode - take #2

2019-11-18 Thread Philippe Gerum via Xenomai
On 11/18/19 9:12 AM, Jan Kiszka wrote: > On 17.11.19 12:41, Philippe Gerum via Xenomai wrote: >> Since zero is the offset pointing at the AVL tree anchor, it cannot be >> used for representing a NULL link. Use (ptrdiff_t)-1 instead. >> >> Signed-off-by: Philippe Gerum >> --- >>  

Re: [PATCH 3/3] boilerplate/avl: fix NULL link representation in pshared mode - take #2

2019-11-18 Thread Jan Kiszka via Xenomai
On 17.11.19 12:41, Philippe Gerum via Xenomai wrote: Since zero is the offset pointing at the AVL tree anchor, it cannot be used for representing a NULL link. Use (ptrdiff_t)-1 instead. Signed-off-by: Philippe Gerum --- include/boilerplate/avl-inner.h | 8 1 file changed, 4