Date: Thu, 22 Apr 2010 21:25:10 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Andriy Gapon <avg@icyb.net.ua> Cc: freebsd-stable@freebsd.org, jfvogel@gmail.com Subject: Re: RELENG_8 -- shutdown -p no longer powers off boxes Message-ID: <20100423042510.GA21479@icarus.home.lan> In-Reply-To: <4BD0C9BA.2000405@icyb.net.ua> References: <20100422143542.GA2208@icarus.home.lan> <4BD0C9BA.2000405@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 23, 2010 at 01:12:10AM +0300, Andriy Gapon wrote: > on 22/04/2010 17:35 Jeremy Chadwick said the following: > > I went digging through HEAD commits between the above dates and wasn't > > able to find much other than this, which appears to be the HEAD commit > > that was MFC'd to RELENG_8: > > > > http://freshbsd.org/2010/04/02/23/04/31 > > I don't think this has been MFC-ed to 8. > Most likely a red herring. > AFAIK, there were no ACPI-related changes in 8 for the last couple of months, so > the issue must be elsewhere. You're right -- sorry about that. I was looking at cvsweb initially, and missed the fact that CVS tags was HEAD (I thought it was RELENG_8). Removing jkim@ from CC list. I'm not sure how I'm going to figure out what the cause of this is, due to how the problem manifests itself. The only other idea I have pertains to WOL (Wake-on-LAN), as both machines use em(4), and I see ifconfig reports the following on their NICs: options=399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC> WOL_UCAST, WOL_MCAST, and WOL_MAGIC are new -- presumably respecting a WOL packet sent via unicast and multicast, but what's WOL_MAGIC? The "magic packet" part of WOL is mandatory, AFAIK (has to contain 6 0xFFs followed by 16 repetitions of the MAC address, and the packet can be of any type. Why I care: When I visually inspected the machine during "shutdown -p", I noticed it had shut off (fans powered down), but the instant the LAN LED blinked the machine powered back on. This could indicate that the new e1000 code isn't doing the Right Thing(tm) when it comes to WOL, and is instead interpreting *any* packet coming in to the NIC as WOL, thus powering up. I have no idea how I'd go about debugging this either. Jack, any ideas? The NICs which have link/exist on the same LAN together: Supermicro X7SBA: em0: <Intel(R) PRO/1000 Network Connection 7.0.5> port 0x2000-0x201f mem 0xdc200000-0xdc21ffff irq 16 at device 0.0 on pci13 em0@pci0:13:0:0: class=0x020000 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (82573E)' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) Supermicro X7SBL-LN2: em0: <Intel(R) PRO/1000 Network Connection 7.0.5> port 0x2000-0x201f mem 0xdc100000-0xdc11ffff irq 16 at device 0.0 on pci13 em0@pci0:13:0:0: class=0x020000 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (82573E)' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100423042510.GA21479>