From owner-freebsd-bugs@freebsd.org  Wed Nov 11 02:21:55 2015
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 1AA83A2B0DB
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 11 Nov 2015 02:21:55 +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 EC588192B
 for <freebsd-bugs@FreeBSD.org>; Wed, 11 Nov 2015 02:21:54 +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 tAB2Ls5g078778
 for <freebsd-bugs@FreeBSD.org>; Wed, 11 Nov 2015 02:21:54 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 204453] panic: vnic0: Received packet fragment with NULL mbuf
 from ThunderX VNIC driver
Date: Wed, 11 Nov 2015 02:21:55 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: emaste@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-204453-8@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-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: Wed, 11 Nov 2015 02:21:55 -0000

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

            Bug ID: 204453
           Summary: panic: vnic0: Received packet fragment with NULL mbuf
                    from ThunderX VNIC driver
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: arm64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: emaste@freebsd.org

I don't know how to reproduce, but this happened while I was installing
packages from a fast local repository:

panic: vnic0: Received packet fragment with NULL mbuf

cpuid = 0
KDB: stack backtrace:
db_trace_self() at db_trace_self_wrapper+0x28
         pc = 0xffffff80005aa694  lr = 0xffffff8000071048
         sp = 0xffffff875119d540  fp = 0xffffff875119d660

db_trace_self_wrapper() at vpanic+0x170
         pc = 0xffffff8000071048  lr = 0xffffff80002b5db8
         sp = 0xffffff875119d670  fp = 0xffffff875119d6f0

vpanic() at panic+0x4c
         pc = 0xffffff80002b5db8  lr = 0xffffff80002b5c44
         sp = 0xffffff875119d700  fp = 0xffffff875119d780

panic() at nicvf_rb_ptr_to_mbuf+0x80
         pc = 0xffffff80002b5c44  lr = 0xffffff80005cc54c
         sp = 0xffffff875119d790  fp = 0xffffff875119d7b0

nicvf_rb_ptr_to_mbuf() at nicvf_cq_intr_handler+0x410
         pc = 0xffffff80005cc54c  lr = 0xffffff80005cc1c4
         sp = 0xffffff875119d7c0  fp = 0xffffff875119d870

nicvf_cq_intr_handler() at nicvf_cmp_task+0x20
         pc = 0xffffff80005cc1c4  lr = 0xffffff80005cbd1c
         sp = 0xffffff875119d880  fp = 0xffffff875119d8a0

nicvf_cmp_task() at taskqueue_run_locked+0x14c
         pc = 0xffffff80005cbd1c  lr = 0xffffff800030c8f8
         sp = 0xffffff875119d8b0  fp = 0xffffff875119d920

taskqueue_run_locked() at taskqueue_thread_loop+0x12c
         pc = 0xffffff800030c8f8  lr = 0xffffff800030da5c
         sp = 0xffffff875119d930  fp = 0xffffff875119d950

taskqueue_thread_loop() at fork_exit+0xb4
         pc = 0xffffff800030da5c  lr = 0xffffff800026f6b8
         sp = 0xffffff875119d960  fp = 0xffffff875119d990

fork_exit() at fork_trampoline+0x10
         pc = 0xffffff800026f6b8  lr = 0xffffff80005bc90c
         sp = 0xffffff875119d9a0  fp = 0x0000000000000000

KDB: enter: panic
[ thread pid 0 tid 100389 ]
Stopped at      kdb_enter+0x40:
db>

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