From owner-freebsd-current@FreeBSD.ORG Tue Apr 10 22:14:44 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A0BC16A404 for ; Tue, 10 Apr 2007 22:14:44 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id E8E0A13C46A for ; Tue, 10 Apr 2007 22:14:43 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l3AMEdB9075827; Tue, 10 Apr 2007 16:14:39 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <461C0C3A.7010304@samsco.org> Date: Tue, 10 Apr 2007 16:14:18 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: Julian Elischer References: <2a41acea0704101439l17ba9347o8b9844416dbb25a1@mail.gmail.com> <461C08DF.8010201@elischer.org> In-Reply-To: <461C08DF.8010201@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Tue, 10 Apr 2007 16:14:39 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-current , Jack Vogel Subject: Re: WOL question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2007 22:14:44 -0000 Julian Elischer wrote: > Jack Vogel wrote: >> I am hoping someone here who has more familiarity with the ACPI >> code can enlighten me.... >> >> I have an internal bug filed complaining that FreeBSD disables >> wake-on-lan on the hardware. This means that if you boot, say, >> Linux, even Knoppix as a quickie, and then shutdown, if the >> hardware supports it, it will be left in a state where a magic-packet >> wakeup will work. However, even if I boot up a FreeBSD kernel >> with NO em driver, and then shutdown, it undoes the WOL setup. >> >> Now, I would like to have explicit WOL support added into the >> em driver, but before I even worry about that I need to understand >> where the kernel turns this off without the driver even needed. >> >> I've looked around at the dev/acpi and arch/acpi code and at >> least so far I'm having a hard time getting an adequate picture >> to know how it happens. >> >> Jack >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" > > I think I heard once that some BIOSes turn it off during the boot cycle > somewhere and it is up to the OS to turn it back on. I do know that some > BIOSes > phuck with the NIC enough to stop IPMI from working during the boot. > That would make sense; you don't want the card to generate an NMI during boot from a spurius WOL package before the system is ready to handle it. Scott