From owner-freebsd-bugs@freebsd.org  Sat Jun  3 14:10:20 2017
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 F1214BF2267
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat,  3 Jun 2017 14:10:20 +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 DE18470AB6
 for <freebsd-bugs@FreeBSD.org>; Sat,  3 Jun 2017 14:10:20 +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 v53EAKRf057255
 for <freebsd-bugs@FreeBSD.org>; Sat, 3 Jun 2017 14:10:20 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 217299] Periodic Kernel Panic with FreeBSD 10.3-RELEASE and
 Myricom cards.
Date: Sat, 03 Jun 2017 14:10:20 +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.3-RELEASE
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: mshirk@daemon-security.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217299-8-XIZMAsLL8B@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217299-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-217299-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.23
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: Sat, 03 Jun 2017 14:10:21 -0000

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

--- Comment #3 from Shirkdog <mshirk@daemon-security.com> ---
Keith, I was not sure if you had a change to test with FreeBSD 11 yet, but
update the bug if you still are having the same issue.

The issue that needs to be ironed out is whether this is an issue with the
operating system or the proprietary driver provided by Myricom for their
Sniffer Pro License.

Myricom has pointed to this as a FreeBSD issue, as of course it is the
operating systems fault trying to open fake devices :)

However, they have not provided Keith with any specific reason why from Myr=
icom
support, he only has these logs and crashes that occur periodically.

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