freebsd stable - Oct 2008 - can not wake on lan after halt -p (or shutdown -p now) on releng_7 and releng_7_0

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.

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.

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
...
em0@pci0:1:0:0: class=0x020000 card=0x10838086 chip=0x10b98086 rev=0x06 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82572EI PRO/1000 PT Desktop Adapter (Copper)'
    class      = network
    subclass   = ethernet
...

[root@backup ~]# ifconfig re0 wol
[root@backup ~]# ifconfig em0 wol
[root@backup ~]# ifconfig
em0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
        ether 00:1b:21:22:52:cd
        media: Ethernet autoselect
        status: no carrier
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
        ether 00:1f:d0:24:19:e9
        inet 78.142.42.158 netmask 0xfffffff0 broadcast 78.142.42.159
        inet 192.168.0.6 netmask 0xffffff00 broadcast 192.168.0.255
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        inet 127.0.0.1 netmask 0xff000000
        


I suppose that I should post more info but I dont know what exactly is
needed.
        
Need help!
10x in advance

Georgi Iovchev

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.

 > 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?
You may also try suspend your box with acpiconf and resume from WOL.

 > 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).

-- 
Regards,
Pyun YongHyeon

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.

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.
>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.

(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