On Tue, Jul 03, 2012 at 04:10:46PM -0400, Dong Liu wrote:
> Hi,
>
> After reading the RCU cpu stall doc. I thought that CONFIG_NO_HZ
> might have something to do with this problem. And I think the NO_HZ
> config is not good for RT performance, so I made a new kernel
> without NO_HZ. It lasted longer but eventually cpu stalls happened
> again.
>
> I then disable the cpu stall checking by set
>
> /sys/module/rcutree/parameters/rcu_cpu_stall_suppress
>
> to "1", but it did not solve the problem. Instead of cpu stall I had
>
> BUG: soft lockup - CPU#0 stuck for 279s! [swapper/0:0]
>
> And even I disabled Hyper-Threading, I also got cpu stall now.
>
> CPU stalls also occurred in KVM guest OS as well.
>
> But I never get cpu stall when I'm running the normal kernel without
> -rt patch.
>
> Is the cpu stall a known issue with the rt patch?
>
> Thanks,
>
> Dong
>
> On 6/27/12 11:22 PM, Dong Liu wrote:
> >Hi,
> >
> >I'm running 3.4.3-rt11 and 3.2.18-rt29 on a system with Intel I7 860, I
> >noticed that with hyperthread enabled, I'm getting kernel error
> >
> >rcu_preempt detected stalls on CPUs/tasks: { 3} (detected by 5, t=60002
> >jiffies)
Did you get stack traces with this error? And did you get repeated
stall messages if you waited a few minutes after the first one?
If so, the stack traces can help track down the problem.
Thanx, Paul
> >But with hyperthread disabled, no such error.
> >
> >Is preempt_rt not supposed to be used with hyperthread?
> >
> >Thanks,
> >
> >Dong
> >
> >P.S.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
