[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFzJ2uOxHC8y25oTzkURPcXo9r=5cvcCzSxgOSKnET5voQ@mail.gmail.com>
Date: Thu, 4 Dec 2014 08:18:10 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dâniel Fraga <fragabr@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Dave Jones <davej@...hat.com>
Cc: Chris Rorvick <chris@...vick.com>, Tejun Heo <tj@...nel.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: frequent lockups in 3.18rc4
On Thu, Dec 4, 2014 at 12:43 AM, Dâniel Fraga <fragabr@...il.com> wrote:
>
> Linus, today it's your lucky day, because I think I found the
> real bad commit (if it isn't, then it's some very close to it). I
> managed to narrow the bisect and here's the result:
Ok, that actually looks very reasonable, I had actually looked at it
because of the whole "changes IPI" thing.
One more thing to try: does a revert fix it on current git?
It doesn't revert entirely cleanly, but close enough - attached a
quick rough patch that may or may not work, but looks like a good
revert.
Dave - this might be worth testing for you too, exactly because of
that whole "it changes how we do IPI's". It was your bug report with
TLB IPI's that made me look at that commit originally.
Linus
---
> fd2ac4f4a65a7f34b0bc6433fcca1192d7ba8b8e is the first bad commit
> commit fd2ac4f4a65a7f34b0bc6433fcca1192d7ba8b8e
> Author: Frederic Weisbecker <fweisbec@...il.com>
> Date: Tue Mar 18 21:12:53 2014 +0100
>
> nohz: Use nohz own full kick on 2nd task enqueue
View attachment "patch.diff" of type "text/plain" (1140 bytes)
Powered by blists - more mailing lists