From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joao Correia Subject: Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem) Date: Mon, 6 Jul 2009 18:23:18 +0100 Message-ID: References: <200907031326.21822.andres@anarazel.de> <20090706141916.GA3477@ami.dom.local> <200907061813.29379.andres@anarazel.de> <20090706163106.GA4559@ami.dom.local> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Arun R Bharadwaj , Thomas Gleixner , Stephen Hemminger , netdev@vger.kernel.org, LKML , Andres Freund To: Jarek Poplawski Return-path: Received: from mail-fx0-f218.google.com ([209.85.220.218]:44564 "EHLO mail-fx0-f218.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752504AbZGFRXg convert rfc822-to-8bit (ORCPT ); Mon, 6 Jul 2009 13:23:36 -0400 In-Reply-To: <20090706163106.GA4559@ami.dom.local> Sender: netdev-owner@vger.kernel.org List-ID: Hello Since i already had the kernel compiled and ready to boot when i read this, i gave it a go anyway :-). I can reproduce the freeze with those 4 patches applied, so i can confirm that its, at least, related to, or exposed by, those patches. There must be something else too, or its just too much fuzziness, but the freeze takes a bit more time (approximately five minutes, give or take) compared to the instant freeze before, but its there with the patches, and without them, no freeze. I assume there isnt a "safe" way to get them out of current .31-rc's, r= ight? Thank you very much for your time, Joao Correia On Mon, Jul 6, 2009 at 5:31 PM, Jarek Poplawski wrot= e: > On Mon, Jul 06, 2009 at 06:13:29PM +0200, Andres Freund wrote: > ... >> > > Btw, I ran netem with delay for more than 48h on around 80mbit..= =2E That >> > > does =A0not exclude such a rarely triggered race, but makes it a= bit more >> > > unlikely. (With migration thats around 3sec or so) > ... >> Sorry once more. > > Andres, the bisection + the above - you did 'the whole lotta work' an= d > you shouldn't be sorry at all! ;-) > > Thanks again, > Jarek P. >