From owner-freebsd-stable@FreeBSD.ORG Fri Oct 10 06:02:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD85E1065687 for ; Fri, 10 Oct 2008 06:02:20 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id 769658FC14 for ; Fri, 10 Oct 2008 06:02:20 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so340146rvf.43 for ; Thu, 09 Oct 2008 23:02:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=X2Ul87+brrhUHSQzkb68nqNRIu8b0dhQWyyZywRkaRg=; b=BTKCG+6PbGrllqtIpgh6yEQaOiiUB1sD9s0j707iooGtOjQI9gipP53yqp/jWVYLe8 HrPDQb48VaETGNolijqrSoeJlN3H9Pj5dGekcJ0UchmWWqk8CbE7HKj9rvW5Xyt5eU6x sV5DSww4FUTytHTlf2hAyUS4TONL2gxCB0eeo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=wVPzK3MQyZnVdEdcNjqqIyHzj/URjnlHF0oSY1nrE+FzWXJ0LxrMuo6lTWwhwyxECu 2jHMvqihGv487lk45m8hUj0cXNEvbvY7/Avc/Bc743y1TK7XR1szKNZEJHsZgRtg28lM u7iWDfTLfA0UnRfkE7Ns4vt0o/KtGycRnINtE= Received: by 10.141.52.5 with SMTP id e5mr808953rvk.10.1223618539826; Thu, 09 Oct 2008 23:02:19 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b8sm3290710rvf.4.2008.10.09.23.02.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 09 Oct 2008 23:02:18 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m9A60HQb000523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Oct 2008 15:00:17 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m9A60D1E000522; Fri, 10 Oct 2008 15:00:13 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 10 Oct 2008 15:00:13 +0900 From: Pyun YongHyeon To: David Adam Message-ID: <20081010060013.GB99376@cdnetworks.co.kr> References: <596673353.20081006181334@pulsar.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: Georgi Iovchev , freebsd-stable@freebsd.org Subject: Re: can not wake on lan after halt -p (or shutdown -p now) on releng_7 and releng_7_0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2008 06:02:20 -0000 On Fri, Oct 10, 2008 at 11:41:59AM +0800, David Adam wrote: > On Mon, 6 Oct 2008, Georgi Iovchev wrote: > > I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R > > motherboard. Integrated network card is Realtek 8111B. > > I can not wake the computer after I shutdown it from FreeBSD. > > It is a dualboot system - windows xp and freebsd. If I shutdown the > > computer from windows - later I can wake it up with magic packet. Even > > if i shutdown the machine on the boot menu with the power button - than > > later I can wake on lan. The only situation where I CANNOT wake it is > > when I shutdown the machine from freebsd (halt -p). > > > > First I tested with 7.0-RELEASE-p5 amd64 (RELENG_7_0) and than I > > upgraded to 7.1 PRERELASE amd64 (RELENG_7). I also tested with two > > network cards - the integrated one Realtek 8111B and another one Intel > > PRO1000PT PCI-E with WOL enabled. > > > > With both nics and both freebsd versions the situation is the same - > > after shutdown from bsd the computer is not able to wake on lan. The > > indication on the switch port says that after shut down there is > > active link. > > I have a similar problem with an Intel SR1200 Pentium 3-class system, > using fxp(4) cards, although I haven't yet tried the `halt -p` command. > fxp(4) should be taught to support WOL. Also note, not all fxp(4) hardwares support WOL. > I was discussing WoL with a colleague recently and he suggested that on > some Linux systems he needed to use `ethtool -s eth0 wol g` on every boot > to maintain the WoL status. > In FreeBSD this is controlled by ifconfig(8) and WOL implementation is up to driver writer. Some controllers require special configuration to make WOL work but I think re(4) should have no such issue as one of hardest part of WOL is handled by firmware on RealTek controllers(You don't need to reestablish a 10/100Mbps link). > >From the ethtool(1) manpage: > > wol p|u|m|b|a|g|s|d... > Set Wake-on-LAN options. Not all devices support this. > g Wake on MagicPacket(tm) > > >From my reading, this might be necessary if the driver clears the flag > during initialisation of the card. > > kern/83807 was filed to fix this issue for sis(4), but was never > committed. However, work is apparently being done in 8-CURRENT to support > exposing the WoL settings to ifconfig: see > http://wiki.freebsd.org/WakeOnLan . Until that work lands in a release, I > think we're out of luck. > If I had sis(4) hardware I would have written WOL support code. The patch in the PR needs minor modifications but it requires real hardware to test the WOL functionality. Maybe PR submitter can do that. > (Another administrator has also suggested that, on Linux at least, using > the 'ifdown' command will destroy WoL status, but I don't think that's an > issue here.) > > Hope that helps. I'm sure any contributions to the effort to add driver > support will be appreciated. > > David Adam > zanchey@ucc.gu.uwa.edu.au -- Regards, Pyun YongHyeon