On 10/03/2014 11:58 AM, Dave Jones wrote: > On Fri, Oct 03, 2014 at 08:43:57AM -0700, Linus Torvalds wrote: > > On Thu, Oct 2, 2014 at 10:00 PM, Sasha Levin <sasha.le...@oracle.com> > wrote: > > > > > > For the record, I tweaked the environment to put some more pressure on > the > > > scheduler and found out what broke (which is not related to this thread > at > > > all). > > > > Ok. It's probably still worth testing Mel's patches, since that's what > > goes into 3.17. But it would be interesting to eventually go back to > > stability-testing the protnone set, since it *looked* like it was > > working well aside from this issue. I might decide to just do it > > during the 3.18 merge window..
Linus, I'm running with Mel's patches since yesterday, nothing interesting to report. > FYI, I've been trying to reproduce that initial bug all week, and > haven't seen a single reoccurance of it, just other bugs. > Kind of a pain in the ass for confirming this numa stuff was indeed > the cause, but that's been true of so many of the more obscure bugs > trinity has shaken out. +1, it seems to have "disappeared", quite annoying :/ Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
