From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail6.bemta8.messagelabs.com (mail6.bemta8.messagelabs.com [216.82.243.55]) by kanga.kvack.org (Postfix) with ESMTP id A54656B00C9 for ; Tue, 22 Nov 2011 21:10:51 -0500 (EST) Message-ID: <1322012633.14573.22.camel@pasglop> Subject: Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413 From: Benjamin Herrenschmidt Date: Wed, 23 Nov 2011 12:43:53 +1100 In-Reply-To: References: <20111121131531.GA1679@x4.trippels.de> <1321884966.10470.2.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20111121153621.GA1678@x4.trippels.de> <1321890510.10470.11.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20111121161036.GA1679@x4.trippels.de> <1321894353.10470.19.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <1321895706.10470.21.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20111121173556.GA1673@x4.trippels.de> <1321900743.10470.31.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20111121185215.GA1673@x4.trippels.de> <20111121195113.GA1678@x4.trippels.de> <1321907275.13860.12.camel@pasglop> <1321948113.27077.24.camel@edumazet-laptop> <1321999085.14573.2.camel@pasglop> <1322007501.14573.15.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: owner-linux-mm@kvack.org List-ID: To: Christian Kujau Cc: Eric Dumazet , Christoph Lameter , Markus Trippelsdorf , "Alex,Shi" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , Pekka Enberg , Matt Mackall , "netdev@vger.kernel.org" , Tejun Heo > > I just want to see whether your network + heavy IO load problem goes > > away with that one patch. > > Sorry, I should have been clearer in that mail: the high "load" value > isn't a problem - the intermittent panics are. What I meant to say was: > the panics usually occur when lots of disk & cpu IO is in progress (rsync > to an external but local disk over firewire). While doing this the load is > usally at 3-5, but that's "normal" and expected for a machine of that age. No, I understand your problem. What I meant above is to see whether you reproduce the crash caused by network + heavy IO :-) > But then the machine crashes with recent kernels. After setting the > cpu_partial files to 0 I tried to reproduce the same I/O pattern, *plus* a > bit more, to really stress the machine, so load went up to 6-7 and the > machine did not crash. So the load of 6-7 was expected and I'm glad that > the machine did not crash with that workaround. I don't know of the > implications of setting cpu_partial to 0 though. Right. Now we want to check if that patch from Christoph fixes cpu partial. > As soon as the build with Christoph's one-liner is done I'll test w/o > setting cpu_partial to 0 and see what it gives. Thanks ! Cheers, Ben. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org