From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 18:35:57 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D83A8106567E for ; Mon, 3 Nov 2008 18:35:57 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (mailrelay.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id 606928FC1C for ; Mon, 3 Nov 2008 18:35:57 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id CDFFDA06B7; Mon, 3 Nov 2008 19:35:54 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id C15DBA06B3; Mon, 3 Nov 2008 19:35:54 +0100 (CET) Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id A368EA0690; Mon, 3 Nov 2008 19:35:54 +0100 (CET) Received: from localhost.my.domain ([132.187.37.59]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.2) with ESMTP id 2008110319355330-11240 ; Mon, 3 Nov 2008 19:35:53 +0100 Received: by localhost.my.domain (sSMTP sendmail emulation); Mon, 3 Nov 2008 19:35:56 +0100 Date: Mon, 3 Nov 2008 19:35:56 +0100 From: Alexey Shuvaev To: Pyun YongHyeon Message-ID: <20081103183556.GA2009@localhost.my.domain> References: <20081015003745.GG14769@cdnetworks.co.kr> MIME-Version: 1.0 In-Reply-To: <20081015003745.GG14769@cdnetworks.co.kr> Organization: Universitaet Wuerzburg User-Agent: Mutt/1.5.18 (2008-05-17) X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.2|August 07, 2008) at 11/03/2008 07:35:53 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.2|August 07, 2008) at 11/03/2008 07:35:54 PM, Serialize complete at 11/03/2008 07:35:54 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Cc: freebsd-current@freebsd.org Subject: Re: Call for testers: fxp(4) WOL 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: Mon, 03 Nov 2008 18:35:58 -0000 On Wed, Oct 15, 2008 at 09:37:45AM +0900, Pyun YongHyeon wrote: > I've implemented WOL for fxp(4) and it works ok to me. Because > there too many variants of fxp(4) hardwares I'd like to hear > success/failure report before committing attached patch to tree. > It seems that the following Intel 8255x supports WOL. Apparently > 82557 lacks WOL capabillity. > > 82558 > 82559 > 82550 > 82551 > How can one figure out which chip he has? I have relative old Toshiba notebook with integrated intel network card. The system is: FreeBSD localhost.my.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Oct 27 01:25:54 CET 2008 root@localhost.my.domain:/usr/obj/usr/src/sys/GENERIC i386 Here are relevant messages from the verbose boot: fxp0: port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfceff000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1031 1179 0001 0042 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 fxp0: XXX: driver didn't set ifq_maxlen ^^^ Is this something to fix? fxp0: bpf attached fxp0: Ethernet address: xx:xx:xx:xx:xx:xx fxp0: [MPSAFE] fxp0: [ITHREAD] and this is the output from pciconv -lvc: fxp0@pci0:2:8:0: class=0x020000 card=0x00011179 chip=0x10318086 rev=0x42 hdr=0x00 vendor = 'Intel Corporation' device = '82801CAM (ICH3) PRO/100 VE (LOM) Network Connection' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D1 D2 D3 current D0 It seems that driver changes something, after boot or 'ifconfig fxp0 wol': fxp0: flags=8843 metric 0 mtu 1500 options=2008 and after 'ifconfig fxp0 -wol': fxp0: flags=8843 metric 0 mtu 1500 options=8 However the system seems to honors only the BIOS settings, if I enable WOL in the BIOS the system wakes up from power-down or suspend (to ram) states regardless of fxp settings and with disabled WOL in BIOS it never wakes up. The worse thing I have noticed is if I send WOL packet while the system is running it reliably hangs. It does not panic and switching virtual consoles works (and typing/deleting something in the shell prompt too), but the cooler runs at full power and you can't do anything else. This is both with patched fxp and that from -CURRENT. > If your suspend/resume works on your system you can also wake up > your system in suspend by WOL. > Actually, the system does not wake up from suspended mode properly, either by power button or by WOL packet, but it tries. > Thanks. Thank you, if you need something more (debugging output, testing new patches, digging deeper...) just let me know. Alexey.