From owner-freebsd-wireless@freebsd.org  Thu Jan 19 16:27:58 2017
Return-Path: <owner-freebsd-wireless@freebsd.org>
Delivered-To: freebsd-wireless@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 E9FA3CB8F04
 for <freebsd-wireless@mailman.ysv.freebsd.org>;
 Thu, 19 Jan 2017 16:27:58 +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 D909D16E5
 for <freebsd-wireless@FreeBSD.org>; Thu, 19 Jan 2017 16:27:58 +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 v0JGRvOc008487
 for <freebsd-wireless@FreeBSD.org>; Thu, 19 Jan 2017 16:27:58 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-wireless@FreeBSD.org
Subject: [Bug 211689] panic with lagg failover wireless ath and iwm
Date: Thu, 19 Jan 2017 16:27:57 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: wireless
X-Bugzilla-Version: 11.0-RC1
X-Bugzilla-Keywords: crash, needs-qa, patch, regression
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: asomers@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org
X-Bugzilla-Flags: mfc-stable10? mfc-stable11?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-211689-21060-R0DuIxcsaH@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211689-21060@https.bugs.freebsd.org/bugzilla/>
References: <bug-211689-21060@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2017 16:27:59 -0000

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

--- Comment #16 from Alan Somers <asomers@FreeBSD.org> ---
Randy, you are correct that "service netif restart lagg0" will destroy the
cloned interface.  I just didn't realize that suspending restarted network
interfaces.  In any case, you're panic isn't directly in the lagg or inet6
code.  That's why I want to see the exact panic string.  I may need access =
to
the core file too, if you're willing and able to provide it.

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