From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw01.freescale.net (az33egw01.freescale.net [192.88.158.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw01.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id A7AE2DDECC for ; Tue, 12 Feb 2008 08:50:19 +1100 (EST) Message-ID: <47B0C30A.1030801@freescale.com> Date: Mon, 11 Feb 2008 15:50:02 -0600 From: Scott Wood MIME-Version: 1.0 To: Rune Torgersen Subject: Re: WARN_ON() hit in fsl bitbanged phy driver References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Rune Torgersen wrote: > I hit the following WARN_ON when using mii-tools agains a ethernet > interface using a bit-banged mii interface > It is only diplayed once, and does not seem to impact usage at all > > Does somebody know what is wrong, and how to fix it? It looks like the kernel thinks it's in an interrupt, even though it clearly isn't from the backtrace. Presumably, something slept from an interrupt handler; try turning on sleep-in-spinlock debugging. The root cause was probably something other than the phy code. -Scott