Jan Kiszka wrote:
Jan Kiszka wrote:
...
[Update] While writing this mail and letting your test run for a while,
I *did* get a hard lock-up. Hold on, digging deeper...
And here are its last words, spoken via serial console:
c31dfab0 0086 c30d1a90 c02a2500 c482a360 0001 0001
Hm.
When I remove the output() from both tasks, all seems fine.
Jeroen.
___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core
Hold on. Just crashed without the file access: please disregard last post.
Jeroen.
___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core
Gilles,
I cannot reproduce those messages after turning nucleus debugging on. Instead, I now either get relatively more failing mutexes oreven hard lockups with the test program I sent to you. If thecomputer didn't crash, dmesg contains 3 Xenomai messages relating to a task being movend to
Jeroen Van den Keybus wrote:
Gilles,
I cannot reproduce those messages after turning nucleus debugging on.
Instead, I now either get relatively more failing mutexes or even hard
lockups with the test program I sent to you. If the computer didn't crash,
dmesg contains 3 Xenomai
Hello,
Apparently, the code I shared with Gilles never made it to this forum. Anyway, the issue I'm having here is really a problem and it might be useful if some of you could try it out or comment on it. I might be making a silly programming error here, but the result is invariably erroneous
Jan Kiszka wrote:
...
[Update] While writing this mail and letting your test run for a while,
I *did* get a hard lock-up. Hold on, digging deeper...
And here are its last words, spoken via serial console:
c31dfab0 0086 c30d1a90 c02a2500 c482a360 0001 0001 0020
Jan Kiszka wrote:
Jan Kiszka wrote:
...
[Update] While writing this mail and letting your test run for a while,
I *did* get a hard lock-up. Hold on, digging deeper...
And here are its last words, spoken via serial console:
c31dfab0 0086 c30d1a90 c02a2500 c482a360 0001 0001
Jeroen Van den Keybus wrote:
Interesting, when writing to 2 different files, I get the same crashes.
Will test with only one task/fd.
File ops doesn't matter for me. I took them out of task0/1, and I still
got the crashes. (BTW, this may explain the difference in your backtrace
you reported
Jan Kiszka wrote:
[...]
Do you (or anybody else) have a running 2.0.x installation? If so,
please test that setup as well.
Sure :-)
# uname -r
2.6.13.4-adeos-xenomai
# cat /proc/xenomai/version
2.0
# ./mutex
Running for 2.15 seconds.
ALERT: No lock! (lockcnt=0) Offending task: task0
ALERT: No
Hm.
When I remove the output() from both tasks, all seems fine.
Jeroen.
11 matches
Mail list logo
