Date: Mon, 3 Nov 2008 13:08:59 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Georgi Iovchev <geo@pulsar.bg> Cc: freebsd-acpi@freebsd.org, 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 Message-ID: <20081103040859.GD94302@cdnetworks.co.kr> In-Reply-To: <20081014064456.GE14769@cdnetworks.co.kr> References: <596673353.20081006181334@pulsar.bg> <20081010012058.GA99376@cdnetworks.co.kr> <1948191744.20081010114326@pulsar.bg> <20081014064456.GE14769@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 14, 2008 at 03:44:56PM +0900, To Georgi Iovchev wrote: > On Fri, Oct 10, 2008 at 11:43:26AM +0300, Georgi Iovchev wrote: > > > > > > -- > > Friday, October 10, 2008, 4:20:58 AM: > > > > > On Mon, Oct 06, 2008 at 06:13:34PM +0300, Georgi Iovchev wrote: > > >> Hello list > > >> > > >> 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. > > >> > > > > > Don't know WOL issue of em(4) but re(4) should respond to WOL. > > > 7.0-RELEASE had no support for WOL so RELENG_7 or 7.1-PRERELEASE > > > should be used to experiment WOL. > > Now I am using 7.1-prerelase > > > > >> 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 > > > > > Because you can wake up your sytem from Windows shutdown I think > > > your BIOS is already configured to allow wakeup from WOL. Would > > > you compare ethernet address of re(4) to Winwods? Have you tried to > > > send Magic packets to FreeBSD box? > > I have tried sending magic packets from another bsd machine. I am > > using net/wol. I also tried to send magic packets from windows machine > > using 3 different programs. > > > > > You may also try suspend your box with acpiconf and resume from WOL. > > I cant. > > > > [root@backup ~]# acpiconf -s 5 > > acpiconf: invalid sleep type (5) > > > > Actually I cant enter in any sleep state > > [root@backup ~]# acpiconf -s 4 > > acpiconf: request sleep type (4) failed: Operation not supported > > [root@backup ~]# acpiconf -s 3 > > acpiconf: request sleep type (3) failed: Operation not supported > > [root@backup ~]# acpiconf -s 2 > > acpiconf: request sleep type (2) failed: Operation not supported > > [root@backup ~]# acpiconf -s 1 > > acpiconf: request sleep type (1) failed: Operation not supported > > > > I am using generic kernel with little modifications, (generally i have > > commented many unused drivers - raid, if_....) Acpi is in generic > > kernel now. > > > > I even tried to wake the machine with magic packet after shutdown -h. > > But still no luck. > > > > > > >> indication on the switch port says that after shut down there is > > >> active link. > > >> > > > > > That indicates the controller is alive so it shall respond to WOL > > > if it was correctly configured to receive WOL packets. Have you > > > tried to send Magic packets to FreeBSD box? > > > > >> Here is some information after last update: > > >> > > >> [root@backup ~]# uname -a > > >> FreeBSD backup.pulsar.bg 7.1-PRERELEASE FreeBSD > > >> 7.1-PRERELEASE #1: Mon Oct 6 17:01:26 EEST 2008 > > >> root@backup.pulsar.bg:/usr/obj/usr/src/sys/MYCONF amd64 > > >> > > >> [root@backup ~]# pciconf -lv > > >> ... > > >> re0@pci0:3:0:0: class=0x020000 card=0xe0001458 > > >> chip=0x816810ec rev=0x01 hdr=0x00 > > >> vendor = 'Realtek Semiconductor' > > >> device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > >> class = network > > >> subclass = ethernet > > >> ... > > > > > Show me dmesg output pertinent to re(4). > > > > re0: <RealTek 8168/8168B/8168C/8168CP/8111B/8111C/8111CP PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf2000000-0xf2000fff irq 17 at device 0.0 on pci3 > > re0: turning off MSI enable bit. > > re0: Chip rev. 0x38000000 > > re0: MAC rev. 0x00000000 > > miibus0: <MII bus> on re0 > > rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0 > > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > re0: Ethernet address: 00:1f:d0:24:19:e9 > > re0: [FILTER] > > > > It looks like your chip is RTL8168B and I don't see any errors in > WOL related code of re(4). :-( > Can you check the resolved link speed/duplex of FreeBSD box after > shutdown?(You can enter to your switch menu and see the port > status.) > How about sending WOL packets over direct-connected UTP cable > without using switch? > Here is WOL patch which may fix the issye. Would you try the following patch and let me know whether WOL works or not? http://people.freebsd.org/~yongari/re/re.phy.patch.20081103 -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081103040859.GD94302>