From nobody Mon Mar 4 07:25:22 2024 X-Original-To: freebsd-current@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 4Tp9G504Y3z5C3nn for ; Mon, 4 Mar 2024 07:25:33 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4Tp9G33J6Hz4SxJ for ; Mon, 4 Mar 2024 07:25:31 +0000 (UTC) (envelope-from jakob@alvermark.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=alvermark.net header.s=x header.b=hS2NQJMW; dmarc=none; spf=pass (mx1.freebsd.org: domain of jakob@alvermark.net designates 185.34.136.138 as permitted sender) smtp.mailfrom=jakob@alvermark.net Received: from c-bc4d235c.06-431-73746f70.bbcust.telenor.se ([92.35.77.188] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96 (FreeBSD)) (envelope-from ) id 1rh2fQ-0007d5-01; Mon, 04 Mar 2024 08:23:20 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alvermark.net; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: From:References:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=o9vaALYRi/9B4z49BSQWNPKwpq9lEV2hEneqjW98faE=; b=hS2NQJMWNgwsygJr0atbVModHH 54atuusCjo698m5ELevDxA2SS03IHqCDl6rmb0nCO+x4kyRancxkSU6MhiuMMVW/uky393mjYtMfS wlXd8vcKZpSFogmQ9/zX/OBGlmIf77I+05g+vdqeWkRWrINA5UYMoH53k47V377L2HHzXaFZoG4IZ 3HzwJJ7HpC0faRA+4zVfyXPCpvekSsS5IN5OfL57RygQTZPunULxbmPTk4HCj0qMJQA9Ld1Hn83wB 6eCV302ASQnlo01/ArYfbH4sIj6sT8llIJO4FlQw865FIZ3X2Oec/RwNMY4KgyNt2oCjrNsOTY8UC sdNw6ubQ==; Received: from office.as33885.net ([84.55.65.101] helo=[192.168.10.2]) by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1rh2hO-000IUC-UH; Mon, 04 Mar 2024 08:25:22 +0100 Message-ID: Date: Mon, 4 Mar 2024 08:25:22 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: main [so: 15] context, 7950X3D and RTL8251/8153 based Ethernet dongle: loss of state, example log information To: Mark Millard , Current FreeBSD References: <41913B2D-381A-4EEC-9B37-531445645F71.ref@yahoo.com> <41913B2D-381A-4EEC-9B37-531445645F71@yahoo.com> Content-Language: en-US From: Jakob Alvermark In-Reply-To: <41913B2D-381A-4EEC-9B37-531445645F71@yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/24, country:IT]; FREEMAIL_TO(0.00)[yahoo.com,freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[alvermark.net:+] X-Rspamd-Queue-Id: 4Tp9G33J6Hz4SxJ On 12/4/23 09:16, Mark Millard wrote: > The following sort of thing is happening a lot: > > Ryzen 9 7950X3D using a USB Ethernet dongle that I've historically > used on occasion, sometimes for long periods . . . > > Example contexts for the issue have been: > > FreeBSD 15.0-CURRENT #126 main-n266130-d521abdff236-dirty: Tue Oct 24 18:17:40 PDT 2023 > and: > FreeBSD 15.0-CURRENT #131 main-n266749-ed31b3f4a146-dirty: Wed Nov 29 16:53:33 PST 2023 > > Both UFS and ZFS boot media, here part of a ed31b3f4a146 UFS example is shown > > Nov 29 18:26:27 7950X3D-UFS kernel: miibus0: on ure0 > Nov 29 18:26:27 7950X3D-UFS kernel: rgephy0: PHY 0 on miibus0 > Nov 29 18:26:27 7950X3D-UFS kernel: rgephy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto > Nov 29 18:26:27 7950X3D-UFS kernel: ue0: on ure0 > Nov 29 18:26:27 7950X3D-UFS kernel: ue0: Ethernet address: REDACTED > Nov 29 18:26:27 7950X3D-UFS kernel: ue0: link state changed to DOWN > . . . > Nov 29 18:26:27 7950X3D-UFS kernel: ue0: link state changed to UP > . . . (no ue0: messages, then) . . . > Nov 30 03:23:18 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:18 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:18 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:18 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:18 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:18 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:19 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:19 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:19 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:19 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:19 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:19 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:19 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:19 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:20 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:20 7950X3D-UFS kernel: ue0: 2 link states coalesced > Nov 30 03:23:20 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:20 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:20 7950X3D-UFS dhclient[53725]: New IP Address (ue0): 192.168.1.157 > Nov 30 03:23:20 7950X3D-UFS dhclient[53730]: New Subnet Mask (ue0): 255.255.255.0 > Nov 30 03:23:20 7950X3D-UFS dhclient[53734]: New Broadcast Address (ue0): 192.168.1.255 > Nov 30 03:23:20 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:20 7950X3D-UFS kernel: ue0: 3 link states coalesced > Nov 30 03:23:20 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:20 7950X3D-UFS dhclient[53771]: New Routers (ue0): 192.168.1.1 > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: link state changed to DOWN > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: 3 link states coalesced > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: link state changed to UP > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: 2 link states coalesced > Nov 30 03:23:21 7950X3D-UFS kernel: ue0: link state changed to UP > . . . (lots more) . . . > > Other FreeBSD system on the Ethernet are not getting such but none > of them are currently using such a dongle. > > Note: The ASUS X670-P WiFi board's built in Ethernet is not > supported. > > === > Mark Millard > marklmi at yahoo.com > I see the same with my Lenovo dongle: ugen1.12: at usbus1 ure0 on uhub6 ure0: on usbus1 miibus1: on ure0 rgephy1: PHY 0 on miibus1 rgephy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto ue0: on ure0 Jakob