From owner-freebsd-scsi@freebsd.org Sun Oct 29 13:17:22 2017 Return-Path: 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 D82D6E6325E for ; Sun, 29 Oct 2017 13:17:22 +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 C552B7D789 for ; Sun, 29 Oct 2017 13:17:22 +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 v9TDHM50036137 for ; Sun, 29 Oct 2017 13:17:22 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: Sun, 29 Oct 2017 13:17:22 +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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2017 13:17:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223238 --- Comment #6 from Edward Tomasz Napierala --- The warnings on the initiator (FreeBSD) side mean that the NAS doesn't correctly mark underflows. It's a common bug and not something to worry ab= out (though still a protocol error). The "Unsupported SCSI Opcode 0xb7" messages on the target (Synology) side m= ean it doesn't support READ DEFECT DATA command. That's ok too, and shouldn't break anything. I'm not sure what makes FreeBSD send the READ DEFECT DATA command to the target. Do you have some disk monitoring software enabled on the initiator side? As for the panic message - looking at the traceback it looks like panic in mpt(4) driver, unrelated to iscsi(4). It might be triggered by the same software that triggers the READ DEFECT DATA on iSCSI. Can you check which process triggered the panic? Basically, when you see the backtrace and pan= ic messages, press Scroll Lock and use cursor keys to scroll up; there should = be some more information there. --=20 You are receiving this mail because: You are the assignee for the bug.=