From owner-freebsd-bugs@freebsd.org  Thu Feb 18 13:37:16 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 008FFAAC5ED
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 18 Feb 2016 13:37:16 +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 E524312E8
 for <freebsd-bugs@FreeBSD.org>; Thu, 18 Feb 2016 13:37:15 +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 u1IDbFCM084700
 for <freebsd-bugs@FreeBSD.org>; Thu, 18 Feb 2016 13:37:15 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 168411] [vm] [panic] uma_find_refcnt(): zone possibly not
 UMA_ZONE_REFCNT
Date: Thu, 18 Feb 2016 13:37:15 +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: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ae@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-168411-8-U0KWYxbTFZ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-168411-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-168411-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 13:37:16 -0000

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

--- Comment #2 from Andrey V. Elsukov <ae@FreeBSD.org> ---
I found the cause of our panics. ixgbe(4) needs to have configured the size=
 of
buffer to receive packets via SRRCTL registers.
In our case it used 4k buffers and for jumbo frames the size of the first
buffer always was 4k. So, even if we correctly set m_len/m_pkthdr.len it al=
ways
writes 4k into m_data. This leads to memory corruption due that the size of
available space in the mbuf is less than 4k (128 bytes reserved). After we
correctly configure SRRCTL registers the panics disappeared.

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