From owner-freebsd-current@freebsd.org Sat May 1 19:22:15 2021 Return-Path: Delivered-To: freebsd-current@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 F3AD663539B for ; Sat, 1 May 2021 19:22:15 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FXfJ75ZsFz4prY; Sat, 1 May 2021 19:22:15 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Received: from freebsd2.freebsd.lan (mail.northatlanticmusicsupplies.com [212.237.182.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: jsm) by smtp.freebsd.org (Postfix) with ESMTPSA id 5F214415F; Sat, 1 May 2021 19:22:15 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Subject: Re: Problems with realtek NIC To: Nilton Jose Rizzo , freebsd-current@freebsd.org References: <202105011909.141J9kQ4068083@server.i805.com.br> From: Jesper Schmitz Mouridsen Message-ID: Date: Sat, 1 May 2021 21:22:12 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.9.1 MIME-Version: 1.0 In-Reply-To: <202105011909.141J9kQ4068083@server.i805.com.br> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 May 2021 19:22:16 -0000 On 01.05.2021 21.09, Nilton Jose Rizzo wrote: > Hi all > > I using a FreeBSD 14-Current and get random error with my NIC. The watchdog timer send a timeout message and I loose connection temporaly. In logs show only this message: > > May 1 14:24:18 valfenda kernel: re0: watchdog timeout > May 1 14:24:18 valfenda kernel: re0: link state changed to DOWN > May 1 14:24:22 valfenda kernel: re0: link state changed to UP > May 1 14:46:12 valfenda kernel: re0: watchdog timeout > May 1 14:46:12 valfenda kernel: re0: link state changed to DOWN > May 1 14:46:16 valfenda kernel: re0: link state changed to UP > May 1 14:58:58 valfenda kernel: re0: watchdog timeout > May 1 14:58:58 valfenda kernel: re0: link state changed to DOWN > May 1 14:59:02 valfenda kernel: re0: link state changed to UP > May 1 15:06:20 valfenda kernel: re0: watchdog timeout > May 1 15:06:20 valfenda kernel: re0: link state changed to DOWN > May 1 15:06:25 valfenda kernel: re0: link state changed to UP > May 1 15:25:32 valfenda kernel: re0: watchdog timeout > May 1 15:25:32 valfenda kernel: re0: link state changed to DOWN > May 1 15:25:36 valfenda kernel: re0: link state changed to UP > May 1 15:28:24 valfenda kernel: re0: watchdog timeout > May 1 15:28:24 valfenda kernel: re0: link state changed to DOWN > May 1 15:28:28 valfenda kernel: re0: link state changed to UP > > This occur frequently when i use a Mozilla Firefox in meet session, but not only in this case. > > My box: > > % uname -a > FreeBSD valfenda 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-7ea3223c7: Thu Apr 22 13:24:05 -03 2021 rizzo@valfenda:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > % pkg info -a | grep firefox > firefox-88.0,2 Web browser based on the browser portion of Mozilla > % kldstat > Id Refs Address Size Name > 1 85 0xffffffff80200000 2131010 kernel > 2 1 0xffffffff82333000 91d0 cryptodev.ko > 3 1 0xffffffff8233d000 7cae50 zfs.ko > 4 1 0xffffffff83010000 d940 geom_eli.ko > 5 1 0xffffffff8301e000 3530 fdescfs.ko > 6 1 0xffffffff83022000 3378 acpi_wmi.ko > 7 1 0xffffffff83026000 3218 intpm.ko > 8 1 0xffffffff8302a000 2180 smbus.ko > 9 1 0xffffffff8302d000 10b310 nvidia-modeset.ko > 10 1 0xffffffff83200000 1e834a8 nvidia.ko > 11 2 0xffffffff83139000 378f8 linux.ko > 12 3 0xffffffff83171000 db70 linux_common.ko > 13 1 0xffffffff8317f000 3238 filemon.ko > 14 1 0xffffffff83183000 5730 cuse.ko > 15 1 0xffffffff83189000 3160 amdtemp.ko > 16 1 0xffffffff8318d000 2138 amdsmn.ko > 17 1 0xffffffff83190000 e538 snd_uaudio.ko > 18 1 0xffffffff8319f000 2340 uhid.ko > 19 1 0xffffffff831a2000 2380 usbhid.ko > 20 1 0xffffffff831a5000 31f8 hidbus.ko > 21 1 0xffffffff831a9000 3320 wmt.ko > 22 1 0xffffffff831ad000 4350 ums.ko > 23 1 0xffffffff831b2000 27040 ipfw.ko > 24 1 0xffffffff831da000 1ae88 ext2fs.ko > 25 1 0xffffffff85084000 11f10 fusefs.ko > 26 1 0xffffffff831f5000 5354 geom_linux_lvm.ko > 27 1 0xffffffff85096000 56ec0 vboxdrv.ko > % > > TIA, > Rizzo > _______________________________________________ > 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" Back on 12 net/realtek-re-kmod solved it for me. With the following in /boot/loader.conf if_re_load="YES" if_re_name="/boot/modules/if_re.ko"