From owner-freebsd-net@freebsd.org  Mon Aug  3 17:47:57 2015
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3EEB39B2EA7
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon,  3 Aug 2015 17:47:57 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2B99B9F7
 for <freebsd-net@FreeBSD.org>; Mon,  3 Aug 2015 17:47:57 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t73Hlu8k022706
 for <freebsd-net@FreeBSD.org>; Mon, 3 Aug 2015 17:47:56 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 194344] [regression] Wake on LAN no longer works on em(4)
Date: Mon, 03 Aug 2015 17:47:57 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: IntelNetworking
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: sbruno@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-194344-2472-UKhdRc67du@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-194344-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-194344-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Aug 2015 17:47:57 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194344

Sean Bruno <sbruno@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |In Progress

--- Comment #4 from Sean Bruno <sbruno@FreeBSD.org> ---
(In reply to Warren Block from comment #0)
Is this the only lem(legacy em device) in the box?  

I see no difference in sys/dev/e1000/if_em.c and sys/dev/e1000/if_lem.c code
that would cause this.

In your copious spare time, :-), can you try to figure out a repro scenario?  I
can't seem to get it to NOT work on my em(4) and lem(4) adapters.

-- 
You are receiving this mail because:
You are the assignee for the bug.