Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031174AbWI1CEm (ORCPT ); Wed, 27 Sep 2006 22:04:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965198AbWI1CEm (ORCPT ); Wed, 27 Sep 2006 22:04:42 -0400 Received: from mail.gmx.de ([213.165.64.20]:20425 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S965197AbWI1CEk (ORCPT ); Wed, 27 Sep 2006 22:04:40 -0400 X-Authenticated: #5039886 Date: Thu, 28 Sep 2006 04:04:38 +0200 From: =?iso-8859-1?Q?Bj=F6rn?= Steinbrink To: Andrew Morton Cc: Martin Filip , linux-kernel@vger.kernel.org, Ayaz Abdulla Subject: Re: forcedeth - WOL [SOLVED] Message-ID: <20060928020438.GC3521@atjola.homenet> Mail-Followup-To: =?iso-8859-1?Q?Bj=F6rn?= Steinbrink , Andrew Morton , Martin Filip , linux-kernel@vger.kernel.org, Ayaz Abdulla References: <1159379441.9024.7.camel@archon.smoula-in.net> <20060927183857.GA2963@atjola.homenet> <1159389486.8902.4.camel@archon.smoula-in.net> <20060927165704.613bf0aa.akpm@osdl.org> <20060928000447.GB2963@atjola.homenet> <20060928004053.GA3521@atjola.homenet> <20060928010133.GB3521@atjola.homenet> <20060927183625.5231e969.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060927183625.5231e969.akpm@osdl.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1360 Lines: 31 On 2006.09.27 18:36:25 -0700, Andrew Morton wrote: > On Thu, 28 Sep 2006 03:01:33 +0200 > Bj?rn Steinbrink wrote: > > > > > > Do we know if this reversal *always* happens with this driver, or only > > > > > sometimes? > > > > I only tried 2.6.18 twice this time, but when I wrote my own tool to do > > it, I had probably 20-30 power on -> ethtool -> poweroff cycles before I > > decided to look into Bugzilla. As it looked like being fixed already and > > I did use the nForce NIC for testing only, I didn't spend any further > > time on it back then. > > What I'm angling towards is: "is this just a driver bug"? I just took a peek at the code. The version on bugzilla (last attachment, comment #22), which was reported to work correctly, has the MAC address reversal hardcoded. The driver in 2.6.18 has some logic to detect if it should reverse the MAC address. So it looks like a hardware oddity/bug that the driver wants to fix but fails. I'll see what happens if I force address reversal and if I can decipher anything, but probably someone else will have to cast the runes... Bj?rn - 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/