[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5480991f.c42ee00a.3e08.ffff8ddd@mx.google.com>
Date: Thu, 4 Dec 2014 15:25:46 -0200
From: Dâniel Fraga <fragabr@...il.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Dave Jones <davej@...hat.com>,
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, 4 Dec 2014 17:52:08 +0100
Frederic Weisbecker <fweisbec@...il.com> wrote:
> And this bug has been fixed upstream with:
>
> _ nohz: nohz full depends on irq work self IPI support
> _ x86: Tell irq work about self IPI support
> _ irq_work: Force raised irq work to run on irq work interrupt
> _ nohz: Move nohz full init call to tick init
>
> These patches have been backported to stable as well.
>
> I suspect Daniel rewinded far enough to fall on that old bug.
>
> Daniel, did you see the above very stacktrace in latest upstream too? Or was it
> a different one?
You're completely right Frederic. I was so obsessed with v3.17
that I forgot to check the fixes made after v3.17 (shame on me!).
The revert patch Linus provided fixes the issue with v3.17, but
since Frederic just confirmed it was fixed after v3.17, then it doesn't
matter anymore.
Sorry about that Linus. Well, so I'm using 3.18.0-rc7 and
everything is working perfect here. :)
Thank you.
--
Linux 3.18.0-rc7: Diseased Newt
http://www.youtube.com/DanielFragaBR
http://exchangewar.info
Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL
--
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