From owner-freebsd-net@freebsd.org  Wed Feb 15 09:56:08 2017
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 7FB33CDF97D
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed, 15 Feb 2017 09:56:08 +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 6E5E6197C
 for <freebsd-net@FreeBSD.org>; Wed, 15 Feb 2017 09:56:08 +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 v1F9u32v081953
 for <freebsd-net@FreeBSD.org>; Wed, 15 Feb 2017 09:56:08 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _
 and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)
Date: Wed, 15 Feb 2017 09:56:03 +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.1-STABLE
X-Bugzilla-Keywords: crash, needs-qa, patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: rwatson@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-148807-2472-2m3hI8Zso3@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-148807-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-148807-2472@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-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 09:56:08 -0000

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

--- Comment #39 from Robert Watson <rwatson@FreeBSD.org> ---
FYI, I feel that this bug report ought to be closed, and a new and more
specific report opened on the IGB issue. The "sbdrop" panic is a generic
debugging invariant that catches a range of different bugs, and this report=
 has
likely therefore encapsulated quite a few different bugs over the years, ra=
ther
than reflecting a single bug.

Can I recommend the creation of a new ticket tacking the presumed IGB
multi-queue issue specifically?

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