AW: Question concerning RCU

Hi Paul, > Two things to try: > > 1. alt-sysreq-t to get all tasks' stacks, or I am not able to do that since I am working on an embedded system which has no real tty, just a serial connected terminal. > 2. disable RCU CPU stall warnings and see if the hangs go away. > As I see

AW: Question concerning RCU

Hi Paul, Two things to try: 1. alt-sysreq-t to get all tasks' stacks, or I am not able to do that since I am working on an embedded system which has no real tty, just a serial connected terminal. 2. disable RCU CPU stall warnings and see if the hangs go away. As I see there

AW: Question concerning RCU

Hi Paul, > You got stack traces with the stall warnings, correct? If so, please look > at them and at Documentation/RCU/stallwarn.txt and see if the kernel is > looping somewhere inappropriate. Yes and no. I have a stack trace, but it is not generated by a stall warning. More precise: I can

AW: Question concerning RCU

Hi Paul, You got stack traces with the stall warnings, correct? If so, please look at them and at Documentation/RCU/stallwarn.txt and see if the kernel is looping somewhere inappropriate. Yes and no. I have a stack trace, but it is not generated by a stall warning. More precise: I can never

AW: Question concerning RCU

Hi Paul, many thanks for your fast answer! Now I have changed my application in that way, that it does not require Xenomai/I-Pipe anymore. That means my kernel is build now from mainline source, with preempt_rt only and no Xenomai or I-Pipe. However the problem is exact the same. After some

AW: Question concerning RCU

Hi Paul, many thanks for your fast answer! Now I have changed my application in that way, that it does not require Xenomai/I-Pipe anymore. That means my kernel is build now from mainline source, with preempt_rt only and no Xenomai or I-Pipe. However the problem is exact the same. After some