From owner-freebsd-current@FreeBSD.ORG Tue Apr 10 22:53:07 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 5AC7816A403 for ; Tue, 10 Apr 2007 22:53:07 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outW.internet-mail-service.net (outW.internet-mail-service.net [216.240.47.246]) by mx1.freebsd.org (Postfix) with ESMTP id 47B6613C468 for ; Tue, 10 Apr 2007 22:53:07 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Tue, 10 Apr 2007 15:22:23 -0700 Received: from [10.251.22.38] (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 5C55F125B24; Tue, 10 Apr 2007 15:53:06 -0700 (PDT) Message-ID: <461C1554.7030407@elischer.org> Date: Tue, 10 Apr 2007 15:53:08 -0700 From: Julian Elischer User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0704101439l17ba9347o8b9844416dbb25a1@mail.gmail.com> <461C08DF.8010201@elischer.org> <461C0C3A.7010304@samsco.org> <2a41acea0704101538l6ae90e8ckf30b10fca4b571eb@mail.gmail.com> In-Reply-To: <2a41acea0704101538l6ae90e8ckf30b10fca4b571eb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current 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:53:07 -0000 Jack Vogel wrote: > On 4/10/07, Scott Long wrote: >> 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. > > Hmm, so I have two competing views about things, one is that the kernel > is actively doing something to disable WOL on shutdown, and now the > theory that its just not rearming the system. > > I really need to know which it is, because I'm putting code in the > driver that > I think should rearm it, and it doesnt work, and I've been left > wondering if > my code is wrong, or if something deeper in the kernel is clobbering the > things I am trying to set up :) > > Jack set up the kernel debugger to stop the boot at the first possible instance (boot -d from the loader) and see what state it is then.. at that point it has only touched a very few things.. mostly just RAM and the console device.