From owner-freebsd-scsi@freebsd.org Sun Nov 6 17:54:35 2016 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 83971C337B7 for ; Sun, 6 Nov 2016 17:54:35 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30106B66 for ; Sun, 6 Nov 2016 17:54:35 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.101] (p508F1FA4.dip0.t-ipconnect.de [80.143.31.164]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 3858B721E281A for ; Sun, 6 Nov 2016 18:54:22 +0100 (CET) From: Michael Tuexen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: mpt driver issue? Message-Id: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> References: To: freebsd-scsi@freebsd.org Date: Sun, 6 Nov 2016 18:54:09 +0100 X-Mailer: Apple Mail (2.3251) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de 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, 06 Nov 2016 17:54:35 -0000 Dear all, it was suggested on current@ to forward this to freebsd-scsi@ The problem shows up since r308268 and it looks like an issue in the mpt driver... Best regards Michael > Begin forwarded message: >=20 > From: Michael Tuexen > Subject: New warnings from WITNESS > Date: 6 November 2016 at 12:50:12 GMT+1 > To: FreeBSD Current >=20 > Dear all, >=20 > when booting a recent kernel >=20 > [freebsd12:~] tuexen% uname -a > FreeBSD freebsd12.testbed 12.0-CURRENT FreeBSD 12.0-CURRENT #702 = r308359M: Sun Nov 6 11:55:17 CET 2016 = tuexen@freebsd12.testbed:/usr/home/tuexen/head/sys/amd64/compile/SCTP = amd64 >=20 > on a VMWare Fusion VM, I get a lot of warnings like >=20 > bus_dmamap_create with the following non-sleepable locks held: > exclusive sleep mutex mpt (mpt) r =3D 0 (0xfffffe0000e2f008) locked @ = dev/mpt/mpt.c:2287 > stack backtrace: > #0 0xffffffff80ac0300 at witness_debugger+0x70 > #1 0xffffffff80ac15e7 at witness_warn+0x3d7 > #2 0xffffffff81055fef at bus_dmamap_create+0x2f > #3 0xffffffff80678a25 at mpt_configure_ioc+0x3a5 > #4 0xffffffff80677476 at mpt_attach+0x226 > #5 0xffffffff80683299 at mpt_pci_attach+0x9c9 > #6 0xffffffff80a9478d at device_attach+0x41d > #7 0xffffffff80a9595a at bus_generic_attach+0x4a > #8 0xffffffff806ebe75 at pci_attach+0xd5 > #9 0xffffffff80a9478d at device_attach+0x41d > #10 0xffffffff80a9595a at bus_generic_attach+0x4a > #11 0xffffffff803c11a2 at acpi_pcib_acpi_attach+0x402 > #12 0xffffffff80a9478d at device_attach+0x41d > #13 0xffffffff80a9595a at bus_generic_attach+0x4a > #14 0xffffffff803b4c8f at acpi_attach+0xdbf > #15 0xffffffff80a9478d at device_attach+0x41d > #16 0xffffffff80a9595a at bus_generic_attach+0x4a > #17 0xffffffff80ee03e3 at nexus_acpi_attach+0x73 > bus_dmamap_create with the following non-sleepable locks held: > exclusive sleep mutex mpt (mpt) r =3D 0 (0xfffffe0000e2f008) locked @ = dev/mpt/mpt.c:2287 > stack backtrace: > #0 0xffffffff80ac0300 at witness_debugger+0x70 > #1 0xffffffff80ac15e7 at witness_warn+0x3d7 > #2 0xffffffff81055fef at bus_dmamap_create+0x2f > #3 0xffffffff80678a25 at mpt_configure_ioc+0x3a5 > #4 0xffffffff80677476 at mpt_attach+0x226 > #5 0xffffffff80683299 at mpt_pci_attach+0x9c9 > #6 0xffffffff80a9478d at device_attach+0x41d > #7 0xffffffff80a9595a at bus_generic_attach+0x4a > #8 0xffffffff806ebe75 at pci_attach+0xd5 > #9 0xffffffff80a9478d at device_attach+0x41d > #10 0xffffffff80a9595a at bus_generic_attach+0x4a > #11 0xffffffff803c11a2 at acpi_pcib_acpi_attach+0x402 > #12 0xffffffff80a9478d at device_attach+0x41d > #13 0xffffffff80a9595a at bus_generic_attach+0x4a > #14 0xffffffff803b4c8f at acpi_attach+0xdbf > #15 0xffffffff80a9478d at device_attach+0x41d > #16 0xffffffff80a9595a at bus_generic_attach+0x4a > #17 0xffffffff80ee03e3 at nexus_acpi_attach+0x73 > bus_dmamap_create with the following non-sleepable locks held: > exclusive sleep mutex mpt (mpt) r =3D 0 (0xfffffe0000e2f008) locked @ = dev/mpt/mpt.c:2287 > stack backtrace: > #0 0xffffffff80ac0300 at witness_debugger+0x70 > #1 0xffffffff80ac15e7 at witness_warn+0x3d7 > #2 0xffffffff81055fef at bus_dmamap_create+0x2f > #3 0xffffffff80678a25 at mpt_configure_ioc+0x3a5 > #4 0xffffffff80677476 at mpt_attach+0x226 > #5 0xffffffff80683299 at mpt_pci_attach+0x9c9 > #6 0xffffffff80a9478d at device_attach+0x41d > #7 0xffffffff80a9595a at bus_generic_attach+0x4a > #8 0xffffffff806ebe75 at pci_attach+0xd5 > #9 0xffffffff80a9478d at device_attach+0x41d > #10 0xffffffff80a9595a at bus_generic_attach+0x4a > #11 0xffffffff803c11a2 at acpi_pcib_acpi_attach+0x402 > #12 0xffffffff80a9478d at device_attach+0x41d > #13 0xffffffff80a9595a at bus_generic_attach+0x4a > #14 0xffffffff803b4c8f at acpi_attach+0xdbf > #15 0xffffffff80a9478d at device_attach+0x41d > #16 0xffffffff80a9595a at bus_generic_attach+0x4a > #17 0xffffffff80ee03e3 at nexus_acpi_attach+0x73 > bus_dmamap_create with the following non-sleepable locks held: > exclusive sleep mutex mpt (mpt) r =3D 0 (0xfffffe0000e2f008) locked @ = dev/mpt/mpt.c:2287 > stack backtrace: > #0 0xffffffff80ac0300 at witness_debugger+0x70 > #1 0xffffffff80ac15e7 at witness_warn+0x3d7 > #2 0xffffffff81055fef at bus_dmamap_create+0x2f > #3 0xffffffff80678a25 at mpt_configure_ioc+0x3a5 > #4 0xffffffff80677476 at mpt_attach+0x226 > #5 0xffffffff80683299 at mpt_pci_attach+0x9c9 > #6 0xffffffff80a9478d at device_attach+0x41d > #7 0xffffffff80a9595a at bus_generic_attach+0x4a > #8 0xffffffff806ebe75 at pci_attach+0xd5 > #9 0xffffffff80a9478d at device_attach+0x41d > #10 0xffffffff80a9595a at bus_generic_attach+0x4a > #11 0xffffffff803c11a2 at acpi_pcib_acpi_attach+0x402 > #12 0xffffffff80a9478d at device_attach+0x41d > #13 0xffffffff80a9595a at bus_generic_attach+0x4a > #14 0xffffffff803b4c8f at acpi_attach+0xdbf > #15 0xffffffff80a9478d at device_attach+0x41d > #16 0xffffffff80a9595a at bus_generic_attach+0x4a > #17 0xffffffff80ee03e3 at nexus_acpi_attach+0x73 >=20 > ... and so on. Not sure which revision introduced it... >=20 > Best regards > Michael > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-scsi@freebsd.org Sun Nov 6 19:42:06 2016 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 447BFC329EB for ; Sun, 6 Nov 2016 19:42:06 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 259D7B03; Sun, 6 Nov 2016 19:42:05 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-232-116.albq.qwest.net [67.0.232.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 53B401928BA; Sun, 6 Nov 2016 19:41:58 +0000 (UTC) Subject: Re: mpt driver issue? To: Michael Tuexen , freebsd-scsi@freebsd.org References: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> Cc: scottl@freebsd.org From: Sean Bruno Message-ID: Date: Sun, 6 Nov 2016 12:41:54 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gmUQojcTriqElfHw5E40dTo5GAuJHxakc" 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, 06 Nov 2016 19:42:06 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gmUQojcTriqElfHw5E40dTo5GAuJHxakc Content-Type: multipart/mixed; boundary="rVBg9g1EiuJo5BOrG37RuxlH46a35N2eu"; protected-headers="v1" From: Sean Bruno To: Michael Tuexen , freebsd-scsi@freebsd.org Cc: scottl@freebsd.org Message-ID: Subject: Re: mpt driver issue? References: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> In-Reply-To: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> --rVBg9g1EiuJo5BOrG37RuxlH46a35N2eu Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 11/06/16 10:54, Michael Tuexen wrote: > Dear all, >=20 > it was suggested on current@ to forward this to freebsd-scsi@ >=20 > The problem shows up since r308268 and it looks like an issue > in the mpt driver... >=20 > Best regards > Michael I don't see any *obvious* reason that we should hold the mpt lock here. It looks ok to just drop it. sean Index: sys/dev/mpt/mpt.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/dev/mpt/mpt.c (revision 308345) +++ sys/dev/mpt/mpt.c (working copy) @@ -2284,9 +2284,7 @@ mpt_lprt(mpt, MPT_PRT_DEBUG, "doorbell req =3D %s\n", mpt_ioc_diag(mpt_read(mpt, MPT_OFFSET_DOORBELL))); - MPT_LOCK(mpt); error =3D mpt_configure_ioc(mpt, 0, 0); - MPT_UNLOCK(mpt); return (error); } --rVBg9g1EiuJo5BOrG37RuxlH46a35N2eu-- --gmUQojcTriqElfHw5E40dTo5GAuJHxakc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQF8BAEBCgBmBQJYH4eCXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kBl8H+wXvTw6UNz60CCSQKDBXyutj ZfdbbSwf1clyM3dfUTPlVY87cSS5gnaNE2D4pFgnb0uum+5pH4YC+M9or/eSHIHp yw/FLvwNZS3uWk4meAq1s+9hEXnUHvsFiry9cssklrLtKS2bn8BhDCzJdPnq58U5 oOn74eNUMep5EeFLtFjkX3jEAuZBghQzcnymCHftcaNGM4PXIi5PVKOMnLiiyWkS UaS4SYIrH9TNNnjYCFQ56ScE3zz5Gnl8Q+hDk20r37Uk1QQAkR+bzkeaPrVD+Qu6 IFjF5U0mp7AQ+md2DbcfBJN3gDTHc94gHMBbgFjXbkfgDcrQGAoagh9HNWG/Vpw= =qWMX -----END PGP SIGNATURE----- --gmUQojcTriqElfHw5E40dTo5GAuJHxakc-- From owner-freebsd-scsi@freebsd.org Sun Nov 6 20:57:08 2016 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 198DCC33E8B for ; Sun, 6 Nov 2016 20:57:08 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D5027EE6; Sun, 6 Nov 2016 20:57:07 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.101] (p508F13AC.dip0.t-ipconnect.de [80.143.19.172]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 45885721E281A; Sun, 6 Nov 2016 21:57:04 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: mpt driver issue? From: Michael Tuexen In-Reply-To: Date: Sun, 6 Nov 2016 21:57:02 +0100 Cc: freebsd-scsi@freebsd.org, scottl@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> To: Sean Bruno X-Mailer: Apple Mail (2.3251) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de 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, 06 Nov 2016 20:57:08 -0000 > On 6 Nov 2016, at 20:41, Sean Bruno wrote: > > > > On 11/06/16 10:54, Michael Tuexen wrote: >> Dear all, >> >> it was suggested on current@ to forward this to freebsd-scsi@ >> >> The problem shows up since r308268 and it looks like an issue >> in the mpt driver... >> >> Best regards >> Michael > > I don't see any *obvious* reason that we should hold the mpt lock here. > It looks ok to just drop it. I tried that and the system (with WITNESS) panic'ed... Can't write a core (not a surprise). Best regards Michael > > sean > > Index: sys/dev/mpt/mpt.c > =================================================================== > --- sys/dev/mpt/mpt.c (revision 308345) > +++ sys/dev/mpt/mpt.c (working copy) > @@ -2284,9 +2284,7 @@ > mpt_lprt(mpt, MPT_PRT_DEBUG, "doorbell req = %s\n", > mpt_ioc_diag(mpt_read(mpt, MPT_OFFSET_DOORBELL))); > > - MPT_LOCK(mpt); > error = mpt_configure_ioc(mpt, 0, 0); > - MPT_UNLOCK(mpt); > > return (error); > } > > > > > From owner-freebsd-scsi@freebsd.org Sun Nov 6 22:46:07 2016 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 CD70EC3482C for ; Sun, 6 Nov 2016 22:46:07 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from mail.samsco.org (suzi.samsco.org [96.84.242.101]) (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 B2495EA; Sun, 6 Nov 2016 22:46:06 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from localhost (localhost [192.168.254.3]) by mail.samsco.org (Postfix) with ESMTP id 2851915C1867E; Sun, 6 Nov 2016 22:46:04 +0000 (UTC) Received: from mail.samsco.org ([192.168.254.3]) by localhost (mail.samsco.org [192.168.254.3]) (maiad, port 10024) with ESMTP id 27855-10; Sun, 6 Nov 2016 22:46:04 +0000 (UTC) Received: from [192.168.254.199] (unknown [192.168.254.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: scottl@samsco.org) by mail.samsco.org (Postfix) with ESMTPSA id 0530415C1867C; Sun, 6 Nov 2016 22:46:04 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: mpt driver issue? From: Scott Long In-Reply-To: Date: Sun, 6 Nov 2016 15:46:03 -0700 Cc: Sean Bruno , freebsd-scsi Content-Transfer-Encoding: 7bit Message-Id: References: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> To: Michael Tuexen X-Mailer: Apple Mail (2.3251) 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, 06 Nov 2016 22:46:07 -0000 > On Nov 6, 2016, at 1:57 PM, Michael Tuexen wrote: > >> On 6 Nov 2016, at 20:41, Sean Bruno wrote: >> >> >> >> On 11/06/16 10:54, Michael Tuexen wrote: >>> Dear all, >>> >>> it was suggested on current@ to forward this to freebsd-scsi@ >>> >>> The problem shows up since r308268 and it looks like an issue >>> in the mpt driver... >>> >>> Best regards >>> Michael >> >> I don't see any *obvious* reason that we should hold the mpt lock here. >> It looks ok to just drop it. > I tried that and the system (with WITNESS) panic'ed... > Can't write a core (not a surprise). Any info on where the panic was? Scott From owner-freebsd-scsi@freebsd.org Mon Nov 7 08:21:57 2016 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 BEB6EC33FDE for ; Mon, 7 Nov 2016 08:21:57 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 73DB81871; Mon, 7 Nov 2016 08:21:57 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [192.168.1.101] (p508F13AC.dip0.t-ipconnect.de [80.143.19.172]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 293A1721E281A; Mon, 7 Nov 2016 09:21:52 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: mpt driver issue? From: Michael Tuexen In-Reply-To: Date: Mon, 7 Nov 2016 09:21:50 +0100 Cc: Sean Bruno , freebsd-scsi Content-Transfer-Encoding: quoted-printable Message-Id: <1909C322-A218-4463-9A86-8E859B4715E6@freebsd.org> References: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> To: Scott Long X-Mailer: Apple Mail (2.3251) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de 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: Mon, 07 Nov 2016 08:21:57 -0000 > On 6 Nov 2016, at 23:46, Scott Long wrote: >=20 >=20 >> On Nov 6, 2016, at 1:57 PM, Michael Tuexen = wrote: >>=20 >>> On 6 Nov 2016, at 20:41, Sean Bruno wrote: >>>=20 >>>=20 >>>=20 >>> On 11/06/16 10:54, Michael Tuexen wrote: >>>> Dear all, >>>>=20 >>>> it was suggested on current@ to forward this to freebsd-scsi@ >>>>=20 >>>> The problem shows up since r308268 and it looks like an issue >>>> in the mpt driver... >>>>=20 >>>> Best regards >>>> Michael >>>=20 >>> I don't see any *obvious* reason that we should hold the mpt lock = here. >>> It looks ok to just drop it. >> I tried that and the system (with WITNESS) panic'ed... >> Can't write a core (not a surprise). >=20 > Any info on where the panic was? After learning how to add a serial console to a VM und Fusion: Booting... GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #705 r308359M: Sun Nov 6 21:54:54 CET 2016 = tuexen@freebsd12.testbed:/usr/home/tuexen/head/sys/amd64/compile/SCTP = amd64 FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on = LLVM 3.8.0) WARNING: WITNESS option enabled, expect reduced performance. VT(vga): text 80x25 CPU: Intel(R) Core(TM) i7-2677M CPU @ 1.80GHz (1799.38-MHz K8-class CPU) Origin=3D"GenuineIntel" Id=3D0x206a7 Family=3D0x6 Model=3D0x2a = Stepping=3D7 = Features=3D0xfa3fbff = Features2=3D0x9fba2203 AMD Features=3D0x28100800 AMD Features2=3D0x1 Structured Extended Features=3D0x2 TSC: P-state invariant Hypervisor: Origin =3D "VMwareVMware" real memory =3D 536870912 (512 MB) avail memory =3D 472502272 (450 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) random: unblocking device. MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff80f7f3c0, 0) error 19 nexus0 vtvga0: on motherboard cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 cpu0: numa-domain 0 on acpi0 cpu1: numa-domain 0 on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port = 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1060-0x106f at device 7.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 pci0: at device 7.3 (no driver attached) vgapci0: port 0x1070-0x107f mem = 0xe8000000-0xefffffff,0xfe000000-0xfe7fffff irq 16 at device 15.0 on = pci0 vgapci0: Boot video device mpt0: port 0x1400-0x14ff mem = 0xfeba0000-0xfebbffff,0xfebc0000-0xfebdffff irq 17 at device 16.0 on = pci0 mpt0: MPI Version=3D1.2.0.0 panic: mutex mpt not owned at ../../../dev/mpt/mpt.c:1212 cpuid =3D 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame = 0xffffffff8222b3d0 vpanic() at vpanic+0x182/frame 0xffffffff8222b450 panic() at panic+0x43/frame 0xffffffff8222b4b0 __mtx_assert() at __mtx_assert+0xc1/frame 0xffffffff8222b4c0 mpt_free_request() at mpt_free_request+0x81/frame 0xffffffff8222b500 mpt_configure_ioc() at mpt_configure_ioc+0x3fa/frame 0xffffffff8222b5e0 mpt_attach() at mpt_attach+0x20c/frame 0xffffffff8222b640 mpt_pci_attach() at mpt_pci_attach+0x9c9/frame 0xffffffff8222b6e0 device_attach() at device_attach+0x41d/frame 0xffffffff8222b740 bus_generic_attach() at bus_generic_attach+0x4a/frame 0xffffffff8222b760 pci_attach() at pci_attach+0xd5/frame 0xffffffff8222b7a0 device_attach() at device_attach+0x41d/frame 0xffffffff8222b800 bus_generic_attach() at bus_generic_attach+0x4a/frame 0xffffffff8222b820 acpi_pcib_acpi_attach() at acpi_pcib_acpi_attach+0x402/frame = 0xffffffff8222b890 device_attach() at device_attach+0x41d/frame 0xffffffff8222b8f0 bus_generic_attach() at bus_generic_attach+0x4a/frame 0xffffffff8222b910 acpi_attach() at acpi_attach+0xdbf/frame 0xffffffff8222b9d0 device_attach() at device_attach+0x41d/frame 0xffffffff8222ba30 bus_generic_attach() at bus_generic_attach+0x4a/frame 0xffffffff8222ba50 nexus_acpi_attach() at nexus_acpi_attach+0x73/frame 0xffffffff8222ba80 device_attach() at device_attach+0x41d/frame 0xffffffff8222bae0 bus_generic_new_pass() at bus_generic_new_pass+0x116/frame = 0xffffffff8222bb10 bus_set_pass() at bus_set_pass+0x8c/frame 0xffffffff8222bb40 configure() at configure+0x9/frame 0xffffffff8222bb50 mi_startup() at mi_startup+0x118/frame 0xffffffff8222bb70 btext() at btext+0x2c KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> Best regards Michael PS: I haven't seen your initial response on = https://lists.freebsd.org/pipermail/freebsd-scsi/2016-November/date.html Just tested Sean's proposed patch. >=20 > Scott >=20 From owner-freebsd-scsi@freebsd.org Mon Nov 7 08:25:31 2016 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 94D82C342E2 for ; Mon, 7 Nov 2016 08:25:31 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from mail.samsco.org (suzi.samsco.org [96.84.242.101]) (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 78BF51E12; Mon, 7 Nov 2016 08:25:30 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from localhost (localhost [192.168.254.3]) by mail.samsco.org (Postfix) with ESMTP id D4C7015C18682; Mon, 7 Nov 2016 08:25:29 +0000 (UTC) Received: from mail.samsco.org ([192.168.254.3]) by localhost (mail.samsco.org [192.168.254.3]) (maiad, port 10024) with ESMTP id 68184-03; Mon, 7 Nov 2016 08:25:29 +0000 (UTC) Received: from [192.168.254.199] (unknown [192.168.254.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: scottl@samsco.org) by mail.samsco.org (Postfix) with ESMTPSA id B022015C18680; Mon, 7 Nov 2016 08:25:29 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: mpt driver issue? From: Scott Long In-Reply-To: <1909C322-A218-4463-9A86-8E859B4715E6@freebsd.org> Date: Mon, 7 Nov 2016 01:25:29 -0700 Cc: Sean Bruno , freebsd-scsi Content-Transfer-Encoding: quoted-printable Message-Id: <1E584A39-B268-4253-A588-7A5CA5D46C97@samsco.org> References: <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> <1909C322-A218-4463-9A86-8E859B4715E6@freebsd.org> To: Michael Tuexen X-Mailer: Apple Mail (2.3251) 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: Mon, 07 Nov 2016 08:25:31 -0000 > On Nov 7, 2016, at 1:21 AM, Michael Tuexen wrote: >=20 >> On 6 Nov 2016, at 23:46, Scott Long wrote: >>=20 >>=20 >>> On Nov 6, 2016, at 1:57 PM, Michael Tuexen = wrote: >>>=20 >>>> On 6 Nov 2016, at 20:41, Sean Bruno wrote: >>>>=20 >>>>=20 >>>>=20 >>>> On 11/06/16 10:54, Michael Tuexen wrote: >>>>> Dear all, >>>>>=20 >>>>> it was suggested on current@ to forward this to freebsd-scsi@ >>>>>=20 >>>>> The problem shows up since r308268 and it looks like an issue >>>>> in the mpt driver... >>>>>=20 >>>>> Best regards >>>>> Michael >>>>=20 >>>> I don't see any *obvious* reason that we should hold the mpt lock = here. >>>> It looks ok to just drop it. >>> I tried that and the system (with WITNESS) panic'ed... >>> Can't write a core (not a surprise). >>=20 >> Any info on where the panic was? > After learning how to add a serial console to a VM und Fusion: >=20 >>=20 Thanks. I have a fix, but I seem to not be able to access the svn = server over ssh right now so I can=E2=80=99t commit it. Here=E2=80=99s = the patch: --- mpt.c (revision 308358) +++ mpt.c (working copy) @@ -2695,7 +2695,11 @@ */ mpt->max_cam_seg_cnt =3D min(mpt->max_seg_cnt, (MAXPHYS / = PAGE_SIZE) + 1); =20 + /* XXX Lame Locking! */ + MPT_UNLOCK(mpt); error =3D mpt_dma_buf_alloc(mpt); + MPT_LOCK(mpt); + if (error !=3D 0) { mpt_prt(mpt, "mpt_dma_buf_alloc() failed!\n"); return (EIO); @@ -2745,6 +2749,7 @@ * retrieved, we are responsible for re-downloading * the firmware after any hard-reset. */ + MPT_UNLOCK(mpt); mpt->fw_image_size =3D mpt->ioc_facts.FWImageSize; error =3D mpt_dma_tag_create(mpt, mpt->parent_dmat, 1, = 0, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, = NULL, @@ -2752,6 +2757,7 @@ &mpt->fw_dmat); if (error !=3D 0) { mpt_prt(mpt, "cannot create firmware dma = tag\n"); + MPT_LOCK(mpt); return (ENOMEM); } error =3D bus_dmamem_alloc(mpt->fw_dmat, @@ -2760,6 +2766,7 @@ if (error !=3D 0) { mpt_prt(mpt, "cannot allocate firmware = memory\n"); bus_dma_tag_destroy(mpt->fw_dmat); + MPT_LOCK(mpt); return (ENOMEM); } mi.mpt =3D mpt; @@ -2768,6 +2775,7 @@ mpt->fw_image, mpt->fw_image_size, mpt_map_rquest, = &mi, 0); mpt->fw_phys =3D mi.phys; =20 + MPT_LOCK(mpt); error =3D mpt_upload_fw(mpt); if (error !=3D 0) { mpt_prt(mpt, "firmware upload failed.\n"); From owner-freebsd-scsi@freebsd.org Thu Nov 10 09:57:56 2016 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 882FEC39E9E for ; Thu, 10 Nov 2016 09:57:56 +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 77934AB9 for ; Thu, 10 Nov 2016 09:57:56 +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 uAA9vt20050262 for ; Thu, 10 Nov 2016 09:57:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 09:57:56 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 09:57:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #18 from Julien Cigar --- Problem appeared again today, after ~15 days of uptime, always on FreeBSD filer1.prod.lan 10.3-RELEASE-p11 FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:49:24 UTC 2016=20=20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da3:iscsi1:0:0:0): READ(10). CDB: 28 00 01 ef ec 90 00 00 01 00=20 (da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 01 ef ec 8e 00 00 01 00=20 (da3:(da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host iscsi1:0:(da2:0:iscsi2:0:0): 0:Retrying command 0): Retrying command da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: s/n MYSERIAL 0 detached da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: s/n MYSERIAL 1 detached (da2:iscsi2:0:0:0): Periph destroyed (da3:iscsi1:0:0:0): Periph destroyed da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 1 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 1c 14 10 0f 00 00 01 00=20 (da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): Retrying command da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: s/n MYSERIAL 1 detached (da2:iscsi2:0:0:0): Periph destroyed da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 1 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): login timed out after 6 seconds; reconnecting da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 0 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 1c 14 10 0f 00 00 01 00=20 (da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): Retrying command da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: s/n MYSERIAL 1 detached WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da2:iscsi2:0:0:0): Periph destroyed da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 1 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): handoff on already connected session WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): connection error; reconnecting da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: s/n MYSERIAL 0 detached (da3:iscsi1:0:0:0): Periph destroyed da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 0 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) After a zpool online, and with vfs.zfs.scrub_delay =3D 0 and vfs.zfs.resilver_delay =3D 0 I issued a zpool scrub and again I had a timeo= ut: WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 5 seconds; reconnecting WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target1): no ping reply (NOP-In) after 5 seconds; reconnecting (da3:iscsi1:0:0:0): READ(10). CDB: 28 00 00 b9 9a 67 00 00 01 00=20 (da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 00 b9 98 3c 00 00 01 00=20 (da3:(da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host iscsi1:0:(da2:0:iscsi2:0:0): 0:Retrying command 0): Retrying command (da3:iscsi1:0:0:0): READ(10). CDB: 28 00 00 b9 9f e4 00 00 01 00=20 (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 00 b9 a8 cc 00 00 01 00=20 (da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:(da2:iscsi1:0:iscsi2:0:0:0:0): 0): Retrying command Retrying command (da3:iscsi1:0:0:0): READ(10). CDB: 28 00 00 b9 a2 42 00 00 01 00=20 (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 00 b9 95 6e 00 00 20 00=20 (da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:(da2:iscsi1:0:iscsi2:0:0:0:0): 0): Retrying command Retrying command (da3:iscsi1:0:0:0): READ(10). CDB: 28 00 00 b9 96 4e 00 00 20 00=20 (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 00 b9 95 8e 00 00 20 00=20 (da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:(da2:iscsi1:0:iscsi2:0:0:0:0): 0): Retrying command Retrying command (da3:iscsi1:0:0:0): READ(10). CDB: 28 00 00 b9 96 6e 00 00 20 00=20 (da2:iscsi2:0:0:0): READ(10). CDB: 28 00 00 b9 a9 b2 00 00 01 00=20 (da3:iscsi1:0:0:0): CAM status: CCB request aborted by the host (da2:iscsi2:0:0:0): CAM status: CCB request aborted by the host (da3:(da2:iscsi1:0:iscsi2:0:0:0:0): 0): Retrying command Retrying command da3 at iscsi1 bus 0 scbus4 target 0 lun 0 da3: s/n MYSERIAL 0 detached da2 at iscsi2 bus 0 scbus3 target 0 lun 0 da2: s/n MYSERIAL 1 detached (da3:iscsi1:0:0:0): Periph destroyed (da2:iscsi2:0:0:0): Periph destroyed da2 at iscsi1 bus 0 scbus4 target 0 lun 0 da2: Fixed Direct Access SPC-4 SCSI device da2: Serial Number MYSERIAL 0 da2: 150.000MB/s transfers da2: Command Queueing enabled da2: 1840144MB (471076881 4096 byte sectors) da3 at iscsi2 bus 0 scbus3 target 0 lun 0 da3: Fixed Direct Access SPC-4 SCSI device da3: Serial Number MYSERIAL 1 da3: 150.000MB/s transfers da3: Command Queueing enabled da3: 1840144MB (471076881 4096 byte sectors) I've raised those timeouts a little bit: kern.iscsi.login_timeout: 30 kern.iscsi.iscsid_timeout: 30 kern.iscsi.ping_timeout: 30 and see if it makes any difference --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 10:05:52 2016 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 069A4C3940A for ; Thu, 10 Nov 2016 10:05:52 +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 EA5DDF3C for ; Thu, 10 Nov 2016 10:05:51 +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 uAAA5ptU007436 for ; Thu, 10 Nov 2016 10:05:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 10:05:51 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 10:05:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #19 from Julien Cigar --- this is what I have on the target: root@filer2:/home/jcigar # sysctl -a|grep -i 'iscsi' kern.iscsi.fail_on_shutdown: 1 kern.iscsi.fail_on_disconnection: 1 kern.iscsi.maxtags: 255 kern.iscsi.login_timeout: 30 kern.iscsi.iscsid_timeout: 30 kern.iscsi.ping_timeout: 30 kern.iscsi.debug: 1 kern.cam.ctl.iscsi.maxcmdsn_delta: 256 kern.cam.ctl.iscsi.login_timeout: 60 kern.cam.ctl.iscsi.ping_timeout: 5 kern.cam.ctl.iscsi.debug: 1 and the following in the error logs: WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): connection error; dropping connection WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): connection error; dropping connection WARNING: 10.20.30.31 (iqn.1994-09.org.freebsd:filer1.prod.lan): connection error; dropping connection --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 11:18:24 2016 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 2B7C2C3A259 for ; Thu, 10 Nov 2016 11:18:24 +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 1B2EC11CC for ; Thu, 10 Nov 2016 11:18:24 +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 uAABIN3i004386 for ; Thu, 10 Nov 2016 11:18:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 11:18:24 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 11:18:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #20 from Julien Cigar --- Also I noticed some Idrop packets on the iscsi interface of the initiator s= ide: root@filer1:/home/jcigar # netstat -I bge1 Name Mtu Network Address Ipkts Ierrs Idrop Opkts O= errs Coll bge1 9000 d0:bf:9c:3a:c6:e1 77396222 0 107 45800806 = 0 0 bge1 - 10.20.30.0 10.20.30.31 77394879 - - 73726273 = - - and: root@filer1:/home/jcigar # vmstat -z | grep -i 'mbuf_jumbo_9k:' mbuf_jumbo_9k: 9216, 74075, 256, 161,51922039, 214, 0 could it be related to jumbo frames? (on the target side counters are 0) --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 11:27:48 2016 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 46230C3A6EB for ; Thu, 10 Nov 2016 11:27:48 +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 35D0C190B for ; Thu, 10 Nov 2016 11:27:48 +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 uAABRlio025466 for ; Thu, 10 Nov 2016 11:27:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 11:27:48 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ben.rubson@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 11:27:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #21 from Ben RUBSON --- I was also using jumbo frames with 10.3, but unfortunately I did not look at dropped packets when I had the issues. Note that with 11, I still use jumbo frames and never encounter this issue again. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 11:47:21 2016 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 D2CE8C3AC5A for ; Thu, 10 Nov 2016 11:47:21 +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 C27DB692 for ; Thu, 10 Nov 2016 11:47:21 +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 uAABlLTl068644 for ; Thu, 10 Nov 2016 11:47:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 11:47:22 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 11:47:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #22 from Julien Cigar --- Yep it's strange, I will definitively upgrade to 11 when possible .. Other infos: root@filer1:/home/jcigar # netstat -m 1285/6575/7860 mbufs in use (current/cache/total) 1024/3526/4550/500010 mbuf clusters in use (current/cache/total/max) 1024/3178 mbuf+clusters out of packet secondary zone in use (current/cache) 0/267/267/250005 4k (page size) jumbo clusters in use (current/cache/total/= max) 256/181/437/74075 9k jumbo clusters in use (current/cache/total/max) 0/0/0/41667 16k jumbo clusters in use (current/cache/total/max) 4673K/11392K/16066K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) 0/214/0 requests for jumbo clusters denied (4k/9k/16k) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile root@filer1:/home/jcigar # sysctl kern.ipc | fgrep nmb kern.ipc.nmbufs: 3200070 kern.ipc.nmbjumbo16: 166668 kern.ipc.nmbjumbo9: 222225 kern.ipc.nmbjumbop: 250005 kern.ipc.nmbclusters: 500010 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 22:25:34 2016 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 3D6E4C3B898 for ; Thu, 10 Nov 2016 22:25:34 +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 2D160DBF for ; Thu, 10 Nov 2016 22:25:34 +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 uAAMPXMo011319 for ; Thu, 10 Nov 2016 22:25:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 22:25:33 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 22:25:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #23 from Julien Cigar --- Ok.. I definitively think it's an issue with jumbo frames, I got another disconnection and again the "requests for jumbo clusters denied" (9k) count= er increased: 0/304/0 requests for jumbo clusters denied (4k/9k/16k) any idea? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 22:47:23 2016 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 A1658C3A70F for ; Thu, 10 Nov 2016 22:47:23 +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 91263188 for ; Thu, 10 Nov 2016 22:47:23 +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 uAAMlN5H058783 for ; Thu, 10 Nov 2016 22:47:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 22:47:23 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: Thu, 10 Nov 2016 22:47:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 Steven Hartland changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smh@FreeBSD.org --- Comment #24 from Steven Hartland --- Any mention of nmbjumbo9 in /var/log/messages? Specifically do you see: kern.ipc.nmbjumbo9 limit reached If so have you tried bumping kern.ipc.nmbjumbo9? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 23:12:13 2016 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 8EE5BC3AEBC for ; Thu, 10 Nov 2016 23:12:13 +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 64AB4F88 for ; Thu, 10 Nov 2016 23:12:13 +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 uAANCD6t057943 for ; Thu, 10 Nov 2016 23:12:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:12:13 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 23:12:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #25 from Julien Cigar --- (In reply to Steven Hartland from comment #24) I don't have any mention of nmbjumbo9 in /var/log/messages, I haven't raised kern.ipc.nmbjumbo9 yet, currently it's: root@filer1:/var/log # sysctl kern.ipc.nmbjumbo9 kern.ipc.nmbjumbo9: 222225 but it does not seem necessary to raise it if I can trust netstat -m: root@filer1:/var/log # netstat -m 1282/6533/7815 mbufs in use (current/cache/total) 1024/3564/4588/500010 mbuf clusters in use (current/cache/total/max) 1024/3431 mbuf+clusters out of packet secondary zone in use (current/cache) 0/161/161/250005 4k (page size) jumbo clusters in use (current/cache/total/= max) 256/120/376/74075 9k jumbo clusters in use (current/cache/total/max) 0/0/0/41667 16k jumbo clusters in use (current/cache/total/max) 4672K/10485K/15157K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) 0/304/0 requests for jumbo clusters denied (4k/9k/16k) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile (the box isn't heavily loaded) what I don't understand if why there are requests for 4k jumbo clusters den= ied as there are plenty free .. ? could it be related to this change: https://svnweb.freebsd.org/base/head/sys/dev/bge/if_bge.c?r1=3D276299&r2=3D= 276750 ? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 23:15:40 2016 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 BCDA8C3AFAB for ; Thu, 10 Nov 2016 23:15:40 +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 94216114 for ; Thu, 10 Nov 2016 23:15:40 +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 uAANFetJ063318 for ; Thu, 10 Nov 2016 23:15:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:15:40 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 23:15:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #26 from Julien Cigar --- I don't know if it's related but I also noticed some incorrect cksum: 00:14:03.380734 IP (tos 0x0, ttl 64, id 19369, offset 0, flags [DF], proto = TCP (6), length 100, bad cksum 0 (->9e84)!) 10.20.30.31.24995 > 10.20.30.32.iscsi-target: Flags [P.], cksum 0x50bd (incorrect -> 0xfff9), seq 1205926059:1205926107, ack 1518444144, win 16384, options [nop,nop,TS val 1388742470 ecr 2474468733], length 48 00:14:03.380742 IP (tos 0x0, ttl 64, id 19370, offset 0, flags [DF], proto = TCP (6), length 100, bad cksum 0 (->9e83)!) 10.20.30.31.55645 > 10.20.30.32.iscsi-target: Flags [P.], cksum 0x50bd (incorrect -> 0x3912), seq 3104128225:3104128273, ack 1948017382, win 16384, options [nop,nop,TS val 1388742470 ecr 4001288677], length 48 00:14:03.381060 IP (tos 0x0, ttl 64, id 54596, offset 0, flags [DF], proto = TCP (6), length 100) 10.20.30.32.iscsi-target > 10.20.30.31.55645: Flags [P.], cksum 0x4c6a (correct), seq 1:49, ack 48, win 16384, options [nop,nop,TS val 4001289988 = ecr 1388742470], length 48 00:14:03.381070 IP (tos 0x0, ttl 64, id 54597, offset 0, flags [DF], proto = TCP (6), length 100) 10.20.30.32.iscsi-target > 10.20.30.31.24995: Flags [P.], cksum 0x0d62 (correct), seq 1:49, ack 48, win 16384, options [nop,nop,TS val 2474470019 = ecr 1388742470], length 48 ... but I guess it's because TSO is enabled on the interfaces ? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 23:17:51 2016 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 34F8AC3B068 for ; Thu, 10 Nov 2016 23:17:51 +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 24D2C1E6 for ; Thu, 10 Nov 2016 23:17:51 +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 uAANHoWL065902 for ; Thu, 10 Nov 2016 23:17:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:17:50 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 23:17:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #27 from Steven Hartland --- checksums a likely just due to hw checksum offloading. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 23:19:43 2016 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 948D3C3B119 for ; Thu, 10 Nov 2016 23:19:43 +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 8407B2E3 for ; Thu, 10 Nov 2016 23:19:43 +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 uAANJh6p068216 for ; Thu, 10 Nov 2016 23:19:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:19:43 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 23:19:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #28 from Steven Hartland --- checksums a likely just due to hw checksum offloading. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 23:30:48 2016 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 50A24C3B476 for ; Thu, 10 Nov 2016 23:30:48 +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 409E7B7F for ; Thu, 10 Nov 2016 23:30:48 +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 uAANUlKP090854 for ; Thu, 10 Nov 2016 23:30:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:30:47 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 23:30:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #29 from Steven Hartland --- I'm assuming vmstat agrees with netstat -m e.g. vmstat -z | head -n 1; vmstat -z | grep mbuf It could be that the disconnect is the cause of mbuf issue and not the other way round. You'd have to catch it when the issue is occurring to confirm. If you have plenty of ram you could just trying doubling kern.ipc.nmbjumbo9= to see if the problem goes away? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 23:42:21 2016 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 D1BADC3B889 for ; Thu, 10 Nov 2016 23:42:21 +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 C1ABD1558 for ; Thu, 10 Nov 2016 23:42:21 +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 uAANgLK8019077 for ; Thu, 10 Nov 2016 23:42:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:42:21 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 23:42:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #30 from Steven Hartland --- If its dropping in the driver due to failure go get a jumbo mbuf you should= see this in the output netstat -i. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 23:47:16 2016 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 7D1D2C3B9A7 for ; Thu, 10 Nov 2016 23:47: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 6CF6216D4 for ; Thu, 10 Nov 2016 23:47:16 +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 uAANlG22025087 for ; Thu, 10 Nov 2016 23:47:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:47:16 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 23:47:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #31 from Julien Cigar --- Y(In reply to Steven Hartland from comment #29) Yes it seems so: root@filer1:/var/log # vmstat -z | head -n 1; vmstat -z | grep mbuf ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP mbuf_packet: 256, 3200070, 1024, 3431,94881716, 0, 0 mbuf: 256, 3200070, 257, 3103,566359041, 0, 0 mbuf_cluster: 2048, 500010, 4455, 133,15367798, 0, 0 mbuf_jumbo_page: 4096, 250005, 0, 161,102798544, 0, 0 mbuf_jumbo_9k: 9216, 74075, 256, 120,52036055, 304, 0 mbuf_jumbo_16k: 16384, 41667, 0, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 0, 0, 0, 0 > You'd have to catch it when the issue is occurring to confirm not so easy :) but every time I have a WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 30 seconds; reconnecting I have a small increase in the "requests for 9k jumbo clusters denied" coun= ter > If you have plenty of ram you could just trying doubling kern.ipc.nmbjumb= o9 to see if the problem goes away? The machine has only 8GB of RAM (and ZFS), I think I'll first test with a 1= 500 MTU and -tso --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Nov 10 23:49:55 2016 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 E9F94C3BA59 for ; Thu, 10 Nov 2016 23:49: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 D9CE217A6 for ; Thu, 10 Nov 2016 23:49:55 +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 uAANntHo028187 for ; Thu, 10 Nov 2016 23:49:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:49:55 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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: Thu, 10 Nov 2016 23:49:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #32 from Julien Cigar --- (In reply to Steven Hartland from comment #30) Yes I already checked the error counters, but it's 0: root@filer1:/var/log # netstat -I bge1 Name Mtu Network Address Ipkts Ierrs Idrop Opkts O= errs Coll bge1 9000 d0:bf:9c:3a:c6:e1 77755195 0 152 46072898 = 0 0 bge1 - 10.20.30.0 10.20.30.31 77753810 - - 74150354 = - - ... so I guess it's not a driver issue --=20 You are receiving this mail because: You are on the CC list for the bug.=