From owner-freebsd-net@freebsd.org Fri Mar 20 15:37:20 2020 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1D3A426A64C for ; Fri, 20 Mar 2020 15:37:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48kSZS02BQz3yrZ for ; Fri, 20 Mar 2020 15:37:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id F121D26A64A; Fri, 20 Mar 2020 15:37:19 +0000 (UTC) Delivered-To: net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EF9E526A649 for ; Fri, 20 Mar 2020 15:37:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48kSZR5D20z3yrT for ; Fri, 20 Mar 2020 15:37:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A911925BFF for ; Fri, 20 Mar 2020 15:37:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 02KFbJ7a024287 for ; Fri, 20 Mar 2020 15:37:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 02KFbJvh024286 for net@FreeBSD.org; Fri, 20 Mar 2020 15:37:19 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 206567] [msk] msk0: watchdog timeout - 88E8053 on i386 Date: Fri, 20 Mar 2020 15:37:19 +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: 9.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: portmaster@bsdforge.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@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-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2020 15:37:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206567 --- Comment #12 from Chris Hutchinson --- (In reply to Tom Lane from comment #11) OK. I only see one MSI-X message in dmesg(8) It's related to your (msk) card -- Found 1 of 1 interrupts. I ran into the same error you're reporting. But it was on a dual port re (realtek) card. The most proposed solution was to disable MSI-X on the card. Blamed on a poor implementation. I wasn't satisfied with that, as doing so would reduce performance, and I work that card pretty hard. So I performed some additional investigation into exactly *why* this problem occurs, and ultimately decided to investigate the kernel tunable kern.ipc.nmbjumbop and kern.ipc.nmbclusters After tweaking them for awhile. I found thresholds that eliminated the error, and have been running the card blissfully for about 9 months now. If I were you, I might be inclined to increase those numbers until the errors cease. There is no magic number I can provide. As it differs from card to card, and load to load. But it's enough to say that the *default* number is inadequate (too small). HTH --Chris --=20 You are receiving this mail because: You are the assignee for the bug.=