From owner-freebsd-scsi@freebsd.org  Tue Oct 31 20:03:29 2017
Return-Path: <owner-freebsd-scsi@freebsd.org>
Delivered-To: freebsd-scsi@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 E5A42E62727
 for <freebsd-scsi@mailman.ysv.freebsd.org>;
 Tue, 31 Oct 2017 20:03:29 +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 D3C06367D
 for <freebsd-scsi@FreeBSD.org>; Tue, 31 Oct 2017 20:03:29 +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 v9VK3TiR008440
 for <freebsd-scsi@FreeBSD.org>; Tue, 31 Oct 2017 20:03:29 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-scsi@FreeBSD.org
Subject: [Bug 223238] Persistent iscsi underflow mismatch errors followed by
 apparent kernel panic
Date: Tue, 31 Oct 2017 20:03:29 +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: 11.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: trasz@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-223238-5312-Syo4eoL5N8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223238-5312@https.bugs.freebsd.org/bugzilla/>
References: <bug-223238-5312@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-scsi@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi/>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 20:03:30 -0000

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

--- Comment #14 from Edward Tomasz Napierala <trasz@FreeBSD.org> ---
The iSCSI messages are obviously related to the iscsi(4) driver, sure, but =
they
are not fatal - in fact they should be completely harmless.  The panic in t=
he
screenshot doesn't seem to be related to iscsi at all - it's panicing in the
mpt(4) driver.  Thus my suggestion to switch the emulated hardware to somet=
hing
else, to see if the workaround helps.  If it does, the logical next step wo=
uld
be to file a bug for mpr(4).

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