[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53394296.5030906@linutronix.de>
Date: Mon, 31 Mar 2014 12:25:26 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Yijing Wang <wangyijing@...wei.com>
CC: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-rt-users@...r.kernel.org, Li Zefan <lizefan@...wei.com>,
Zhangwei <jovi.zhangwei@...wei.com>
Subject: Re: [BUGREPORT] Tasklet scheduled issue in Linux 3.4.x-rt
On 03/29/2014 07:35 AM, Yijing Wang wrote:
> Hi Sebastian,
Hi Yijing,
> Thanks for your reply and help to look at it, thanks!
>
> I also check the tasklet state machine changes, and didn't find
> clue for this issue. So I Temporarily reverted Ingo's patch, without
> this patch, my test is ok.
>
> Because this patch does not exist in the latest Linus kernel, so I
> have not reported this issue to kernel bugzilla.
This patch exists in all -RT releases up to 3.12. If there is an issue
with it, it should be solved.
If the sched bit set is and you can't get lock later then the tasklet
has be to active. Finally, not getting the lock in the tasklet code
itself means it is still occupied by the "add-to-the-list" part which
actually can't happen according to the code.
You said, that you have an eight-way. Is this also NUMA? If so, does
this problem happen if you disable NUMA (i.e. run only one NUMA node
and use only the memory that is directly attached to the node).
> Finally, I would like to thank you again.
>
> Thanks!
> Yijing.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists