Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759441AbZGHJOb (ORCPT ); Wed, 8 Jul 2009 05:14:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755823AbZGHJOU (ORCPT ); Wed, 8 Jul 2009 05:14:20 -0400 Received: from mail-bw0-f225.google.com ([209.85.218.225]:56762 "EHLO mail-bw0-f225.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752416AbZGHJOU (ORCPT ); Wed, 8 Jul 2009 05:14:20 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=pWYXNg4RnV7wUNZyXgFxZ7hQMcHTsVo3QCLyicX6AAJl51erOt3n2uUSfrnlulKH7l VAS5OcGObpL9PRU4jbde+7zcrtKAuta43MykRUCQ31YRNlw2ya4UPA0pYwc/0yQ9tLI6 xcMNhJWah2DPbVDisKPTMcqhPhSSoxGRTrGbo= Date: Wed, 8 Jul 2009 11:13:44 +0200 From: Jarek Poplawski To: Andres Freund Cc: Joao Correia , Arun R Bharadwaj , Thomas Gleixner , Stephen Hemminger , netdev@vger.kernel.org, LKML Subject: Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem) Message-ID: <20090708091344.GD3148@ami.dom.local> References: <200907031326.21822.andres@anarazel.de> <200907071811.27570.andres@anarazel.de> <20090708080852.GC3148@ami.dom.local> <200907081029.34527.andres@anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200907081029.34527.andres@anarazel.de> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1561 Lines: 45 On Wed, Jul 08, 2009 at 10:29:34AM +0200, Andres Freund wrote: > On Wednesday 08 July 2009 10:08:52 Jarek Poplawski wrote: > > On Tue, Jul 07, 2009 at 06:11:27PM +0200, Andres Freund wrote: > > > On Tuesday 07 July 2009 15:57:42 Jarek Poplawski wrote: > > > > On Tue, Jul 07, 2009 at 03:34:07PM +0200, Andres Freund wrote: > > > > ... > > > > > > > > > Testing wether its triggerable inside a vm might be interesting... > > > > > > > > Probably similarly to testing without this patch or even less. Maybe > > > > I should've warned you but this type of bugs in -rc with possible > > > > memory or stack overwrites might be fatal for your data (at least). > > > > > > Fortunately all the data on that machine should either be replaceable or > > > regularly backuped. > > > > > > Will test later today if that patch bugs. > > > > If you didn't start yet, it would be nice to use this, btw: > > > > CONFIG_HOTPLUG_CPU = N > > CONFIG_DEBUG_OBJECTS = Y > > CONFIG_DEBUG_OBJECTS_TIMERS = Y > So I should test with a single cpu? Or is there a config where HOTPLUG_CPU does > not imply !SMP? No, my single cpu should be enough ;-) There is something wrong I guess. I can see in my menuconfig: SMP [=y] ... HOTPLUG [=n] ... HOTPUG_CPU [=y] ... Depends on SMP && HOTPLUG So, let it be HOTPLUG_CPU = Y for now... Jarek P. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/