Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755270AbXEASI7 (ORCPT ); Tue, 1 May 2007 14:08:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755269AbXEASI6 (ORCPT ); Tue, 1 May 2007 14:08:58 -0400 Received: from cassiel.sirena.org.uk ([80.68.93.111]:4021 "EHLO cassiel.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755258AbXEASI5 (ORCPT ); Tue, 1 May 2007 14:08:57 -0400 Date: Tue, 1 May 2007 19:08:31 +0100 From: Mark Brown To: =?utf-8?B?UmFmYcWC?= Bilski Cc: Andrew Morton , linux-kernel@vger.kernel.org, netdev@vger.kernel.org Message-ID: <20070501180830.GA31630@sirena.org.uk> Mail-Followup-To: =?utf-8?B?UmFmYcWC?= Bilski , Andrew Morton , linux-kernel@vger.kernel.org, netdev@vger.kernel.org References: <46365887.3010705@interia.pl> <20070430205522.abad2481.akpm@linux-foundation.org> <20070501084639.GA528@sirena.org.uk> <46371590.4090004@interia.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <46371590.4090004@interia.pl> X-Cookie: Are you sure the back door is locked? User-Agent: Mutt/1.5.13 (2006-08-11) X-SA-Exim-Connect-IP: 82.32.140.119 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: Natsemi DP83815 driver spaming X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on cassiel.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1753 Lines: 51 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 01, 2007 at 12:25:20PM +0200, Rafa=C5=82 Bilski wrote: > eth0: Media selection timer tick. > eth0: possible phy reset: re-initializing This is why the reset is being triggered - it's a workaround for a hardware bug which checks to make sure the hardware is in the state that the kernel thinks it is is going off. The code has this explanatory comment: * 2) check for sudden death of the NIC: * It seems that a reference set for this chip went out with incorrect i= nfo, * and there exist boards that aren't quite right. An unexpected voltage * drop can cause the PHY to get itself in a weird state (basically rese= t). * NOTE: this only seems to affect revC chips. I'd suggest checking your power supply as a first step. [BTW, as Andrew said please don't drop people from the CC.] --=20 "You grabbed my hand and we fell into it, like a daydream - or a fever." --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQCVAwUBRjeCGw2erOLNe+68AQLrcAP/Xc9DKNgyVpeFcH1Llb7KSzqcY+2pWftK LVcJrHiVt9cmJaR3v+CxQ+ISvmUHv8ampBPULEKjixT/w5TRonkpBP2I7ye81ei8 U7C2Wslx58oVtjI43nkTnAFyjq6iLCdt7OyY9jIx2JGDVwdzzDa70J2JpsceQ3BW XmRZmVnrX5Y= =qyTT -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- - 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/