From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarek Poplawski Subject: Re: BUG: soft lockup detected on CPU#0! (2.6.18.2 plus hacks) Date: Thu, 4 Jan 2007 12:04:35 +0100 Message-ID: <20070104110435.GA3175@ff.dom.local> References: <20070104080351.GA1740@ff.dom.local> <20070104082930.GB7006@gondor.apana.org.au> <20070104085014.GA2500@ff.dom.local> <20070104102707.GA7662@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Stevens , greearb@candelatech.com, netdev@vger.kernel.org Return-path: Received: from mx10.go2.pl ([193.17.41.74]:46642 "EHLO poczta.o2.pl" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932368AbXADLCz (ORCPT ); Thu, 4 Jan 2007 06:02:55 -0500 To: Herbert Xu Content-Disposition: inline In-Reply-To: <20070104102707.GA7662@gondor.apana.org.au> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Jan 04, 2007 at 09:27:07PM +1100, Herbert Xu wrote: > On Thu, Jan 04, 2007 at 09:50:14AM +0100, Jarek Poplawski wrote: > > > > Could you explain? I can see some inet_rtm_newaddr > > interrupted. For me it could be e.g.: > > > > after > > vconfig add eth0 9 > > > > ip addr add dev eth0.9 ... > > Whether eth0.9 is up or not does not affect this at all. The spin > locks are initialised (and used) when the first IPv4 address is added, > not when the device comes up. I understand this. I consider IFF_UP as a sign all initialisations (open functions including) are completed and there is permission for working (so logically, if I would do eth0.9 down all traffic should be stopped, what probably isn't true now). Jarek P.