From nobody Tue Nov 26 05:14:46 2024 X-Original-To: net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xy9jz2qcFz5ds7W for ; Tue, 26 Nov 2024 05:14:47 +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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xy9jy6rLZz4JP1 for ; Tue, 26 Nov 2024 05:14:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1732598087; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6N1cUys3qennDZcCg+qe0ewNRgWQsL84DgI6yA5poJU=; b=GBxHcwEMQbGCqJLW+ICysnXoPeCVCtKOnMNTPVCzcpqmZWDBvxiW7Cbz+Iv7HvuPTVP5/k BQ+lyvQHbuHOoS5VFko0ULq/ok4bKhg/CwhqZZjC6p3VEYRwJOpd/LvQwz4jUJkHh1OO3O RL5gvSljMToA8jRUJJFtseLS3XLnorCsYMO5b8VlUulcqXtEbxq1wY2LRvVcXxv/ar+8tp 6i9l80HlwVKqesK0g0OfYkg1vnrha+dmGod/ccsC7csbiLLDRiz0JVt5QkBoC63a5t2j8L AfKQXRW0brTWWJotwgtjI1qDlOPK65U+1wJHxZJtbOkxpsScUgknShJwv+CDzQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1732598087; a=rsa-sha256; cv=none; b=C93V/SvrkvrRwd5PrxOEiiSnZF/Ug3U5fRLjbZWVClabnp4WkaGkwsdX2ReApclpzhRG1Z NbD9qWJ5HRgQAJY0McRjQr/JR2XDvH3RCDD5tzJz6NtY0DGrJ43lq3N/YUx4r071V2Hfwz xO/v+Lx1VaKq5fF1tqj8uiGvZ2eT04QBC9V2kif8s86Ya0nVqGVaTvXK22YH6OeYSRNaLx N6ZUEB2uP3Tb9e1tAdKQvf4Mh3Oy8kyFianIKDK6mccR5MNgd6udoSeoU3EcbkXY2AYmMx 0ci1jnE4Tr6DycihSKqL8VI6psRSrEqmLABTg+VFnF9MgZrLhMnTxihOWjzWwg== 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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Xy9jy6L9Pz1B6k for ; Tue, 26 Nov 2024 05:14:46 +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 4AQ5EkPF072477 for ; Tue, 26 Nov 2024 05:14:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4AQ5EkC3072476 for net@FreeBSD.org; Tue, 26 Nov 2024 05:14:46 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 265714] igc(4) drops link under high traffic Date: Tue, 26 Nov 2024 05:14:46 +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: 13.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: kbowling@freebsd.org 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 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265714 --- Comment #12 from Kevin Bowling --- (In reply to mike from comment #11) To confirm you are setting that on both sides on boot? I am not sure what to make of the instability so far, it is sounding like t= he PHY FW you have is buggy which seemed to be a common problem with these chipsets early on. There is a report of one version struggling with and th= en without EEE in a slightly newer version which both are eventually fixed in = the later PHY FW. The system I have access to as well as what I've heard from Netgate seem to be very stable but are running up to date NVMs which doesn't seem to be ubiquitous on consumer and builder parts. It may be a hard batt= le to get ahold of the right person, but check with the manufacturer to see if they can provide an update. --=20 You are receiving this mail because: You are the assignee for the bug.=