[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141217201630.GA27208@redhat.com>
Date: Wed, 17 Dec 2014 15:16:30 -0500
From: Dave Jones <davej@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Chris Mason <clm@...com>,
Mike Galbraith <umgwanakikbuti@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Dâniel Fraga <fragabr@...il.com>,
Sasha Levin <sasha.levin@...cle.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Suresh Siddha <sbsiddha@...il.com>,
Oleg Nesterov <oleg@...hat.com>,
Peter Anvin <hpa@...ux.intel.com>
Subject: Re: frequent lockups in 3.18rc4
On Wed, Dec 17, 2014 at 11:51:45AM -0800, Linus Torvalds wrote:
> On Wed, Dec 17, 2014 at 10:57 AM, Dave Jones <davej@...hat.com> wrote:
> > On Wed, Dec 17, 2014 at 01:22:41PM -0500, Dave Jones wrote:
> >
> > > I'm going to try your two patches on top of .18, with the same kernel
> > > config, and see where that takes us.
> > > Hopefully to happier places.
> >
> > Not so much. Died very quickly.
>
> Damn, damn, damn. That's because of a stupid typo on the patches. We
> have these very similar variables ("flags" and "fault") that have very
> similar fault information, but they are completely different.
>
> The "fault & FAULT_FLAG_USER" test is wrong, it should test "flags &
> FAULT_FLAG_USER". Patch attached.
Yup, that seems to be the only obvious bug in those commits.
It's survived for long with that change on top.
> The half-way good news is that this certainly confirms that trinity is
> triggering the "page fault with fatal signal pending" special case.
Now let's see how long it runs for..
Dave
--
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