From owner-freebsd-net@freebsd.org Tue Sep 4 16:57:04 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8D45FF5225 for ; Tue, 4 Sep 2018 16:57:03 +0000 (UTC) (envelope-from ryan@ixsystems.com) Received: from mail-pl1-x642.google.com (mail-pl1-x642.google.com [IPv6:2607:f8b0:4864:20::642]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 377DE77518 for ; Tue, 4 Sep 2018 16:57:03 +0000 (UTC) (envelope-from ryan@ixsystems.com) Received: by mail-pl1-x642.google.com with SMTP id f6-v6so1919725plo.1 for ; Tue, 04 Sep 2018 09:57:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=feaZceK6syH0AD3wLB+VtwpEO5ziI6s1WtwYxzKdcTo=; b=m1+btNYdfMGwWEzjh9t+xo6Xxkwl/xh2evN7o7abch/NXWqVT+XiHSwqVWI9k4ht+4 GJNpFdSDPjaWsZ0m8As6HXORz3xaM9IOCHpOOv1MwpkV3nsvh9CBrEbApIAj52RyHrGX uUlvnwGr5qWlKFOWyHDuT4Z7Sl1Y5DYJemToCAHNKitKN82949D3h0puCmbmCEumIpiH 0GAT4T2MA5qOtRrvluaiRWy0Pi7MxMBsk/Fz729YLJ5f7Qyrguo63gxrMrCS+MfKIqxM 02ijVpBUxS2LPRBGdwmsBgYwE0rFKQ0+t+gsxZ8g1i/DVVkKici4yq6DwyAg38kXWHRg uXQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=feaZceK6syH0AD3wLB+VtwpEO5ziI6s1WtwYxzKdcTo=; b=CuP7jB+1F7HvHOKRakYbiU8x0XjIQnGlt6AtdO/Gv3w4Fliz7z5JvjTvLaPfeghsT8 MBwezVjOlXvjYqbzS2pCjHvHY1wa9yQOTXsNWMMDu7oG8M4BV84evXQy/d9QEKCVjj0o eu9GHHgjLuC/D8HE4VG+EVN8sknxplBMyQ3Xqp4JxDraNje+rzpfIoSs/SsgxD6LNkQe LpNywPY+xhu/nQtfRWWBamByXiWupYt1ZSA8u3HboYK3Zqwwx/jKYbMA/3Lk1oGxwmud tCbrg8d56QxJa0t415A+mvbuxq8oZ8aTvpuZ5g2mS8v8ItJIw76zAwgX62AxHOv3R21H YvGQ== X-Gm-Message-State: APzg51A+KD1mQJaf+vUs35L1C/G/8RZlaSYWG6QScPH6/kJA3eNGaemx AIvSbls8cIn+wBjNQ4/FthgmV+DhA3HedzMAqT6O0Kq6yFewGV6qHv65Dfv8aHwcylx26GHcsMM gkH4AUVJEDYKdlsD2AvdHsGQEE7h+S3a/yRmpUA3ztTWOsFkcAmI69meJPN7D5IJCzw== X-Google-Smtp-Source: ANB0VdY1PiqM45EZ226evdPB9fRRAY4S7A1pz5rAsVlNmpD6JTM7+Tup5QvGbBAtSWItHWRIjUb6EA== X-Received: by 2002:a17:902:24d:: with SMTP id 71-v6mr26355413plc.91.1536080222176; Tue, 04 Sep 2018 09:57:02 -0700 (PDT) Received: from [10.0.0.116] (c-67-160-253-209.hsd1.ca.comcast.net. [67.160.253.209]) by smtp.gmail.com with ESMTPSA id s16-v6sm28564053pfm.114.2018.09.04.09.57.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Sep 2018 09:57:01 -0700 (PDT) From: Ryan Moeller Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: iSCSI issues after upgrading to 11.2 x64 RELEASE Date: Tue, 4 Sep 2018 09:57:00 -0700 References: <541494c3-d275-dee2-ff5e-8b276ef8d9d6@gmail.com> To: freebsd-net@freebsd.org In-Reply-To: <541494c3-d275-dee2-ff5e-8b276ef8d9d6@gmail.com> Message-Id: <0C437CBE-E525-4277-9315-6205206CDBB7@ixsystems.com> X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Sep 2018 16:57:04 -0000 > The NIC's are Intel based using igb kernel driver: >=20 > igb0: flags=3D8843 metric 0 = mtu 9000 > = options=3D6403bb I see your MTU is 9000, and as described by the other thread you linked = to, there are issues with 9k jumbo cluster allocation. Some detailed notes are here, but the quick summary is: set MTU < 4096 https://gist.github.com/freqlabs/eba9b755f17a223260246becfbb150a1 > Can anyone suggest anything to stop my system from completely locking = up and becoming unresponsive? > At the moment I'm not sure if switching to 'Stable' or 'Current' = branches is a good solution? The problem has been mitigated for a while on 12-CURRENT, so that might = be worth trying. Otherwise I=E2=80=99ve been hoping a committer will put = this fix in 11-STABLE, but in the meantime you could manually apply the = patch: https://reviews.freebsd.org/D16534 - Ryan=