From owner-freebsd-net@FreeBSD.ORG Tue Nov 9 21:01:34 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 746A7106566C for ; Tue, 9 Nov 2010 21:01:34 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail.yamagi.overkill.yamagi.org (unknown [IPv6:2a01:4f8:121:2102:1::7]) by mx1.freebsd.org (Postfix) with ESMTP id 076358FC1E for ; Tue, 9 Nov 2010 21:01:34 +0000 (UTC) Received: from [2001:6f8:108a:1:226:c6ff:fec4:399e] (unknown [IPv6:2001:6f8:108a:1:226:c6ff:fec4:399e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yamagi.overkill.yamagi.org (Postfix) with ESMTPSA id D569416663D1; Tue, 9 Nov 2010 22:01:32 +0100 (CET) Date: Tue, 9 Nov 2010 22:01:36 +0100 (CET) From: Yamagi Burmeister X-X-Sender: yamagi@maka.home.yamagi.org To: Pyun YongHyeon In-Reply-To: <20101109190713.GA7766@michelle.cdnetworks.com> Message-ID: References: <20101109011410.GB1275@michelle.cdnetworks.com> <20101109190713.GA7766@michelle.cdnetworks.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, Yamagi Burmeister Subject: Re: [patch] WOL support for nfe(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 21:01:34 -0000 On Tue, 9 Nov 2010, Pyun YongHyeon wrote: >> No, the link stays at 1000Mbps so the driver must manually switch back >> to 10/100Mbps. >> > > Hmm, this is real problem for WOL. Establishing 1000Mbps link to > accept WOL frames is really bad idea since it can draw more power > than 375mA. Consuming more power than 375mA is violation of > PCI specification and some system may completely shutdown the power > to protect hardware against over-current damage which in turn means > WOL wouldn't work anymore. Even if WOL work with 1000Mbps link for > all nfe(4) controllers, it would dissipate much more power. > > Because nfe(4) controllers are notorious for using various PHYs, > it's hard to write a code to reliably establish 10/100Mbps link in > driver. In addition, nfe(4) is known to be buggy in link state > handling such that forced media selection didn't work well. I'll > see what could be done in this week if I find spare time. Hmm... Maybe just add a hint to the manpage that WOL is possible broken? Nevertheless thanks for your work it's much appreciated :) >>> o When you put your box into suspend mode, can you wake up your box >>> with WOL magic packet? >> >> I'm sorry but I can't test that since none of those boxes supports >> suspend: >> >> % sysctl hw.acpi.suspend_state >> hw.acpi.suspend_state: NONE >> > > You can switch to suspend mode with "acpiconf -s1". If all goes > well, driver would put the controller into suspend mode after > reprogramming controller to accept WOL frames. After that, you can > wakeup the box by sending a WOL magic packet. Okay, It thought that S3 is required. Put the box into S1, waited some minutes and send the magic packet. The video didn't resume but I was able to login via SSH. So waking up by sending the WOL magic packet works. -- Homepage: www.yamagi.org Jabber: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB