Date: Wed, 7 Dec 2022 16:58:00 -0800 From: Pete Wright <pete@nomadlogic.org> To: questions@freebsd.org Subject: Re: FreeBSD keep loosing ethernet connection Message-ID: <b0dbf444-6589-6265-6db1-6c6bd458fba8@nomadlogic.org> In-Reply-To: <NIj5vig--3-9@tutanota.com> References: <NIj5vig--3-9@tutanota.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------RgYjHEpEMEjKhYOmeHLjPfPu
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
On 12/7/22 16:21, iio7@tutanota.com wrote:
> I have recently changed one of my long running boxes from Arch Linux
> to FreeBSD 13.1, after which I see this in the log during file transfers:
>
> <snip>
> Dec 8 01:01:41 foo kernel: re0: watchdog timeout
> Dec 8 01:01:41 foo kernel: re0: link state changed to DOWN
> Dec 8 01:01:45 foo kernel: re0: link state changed to UP
> Dec 8 01:01:51 foo kernel: re0: watchdog timeout
> Dec 8 01:01:51 foo kernel: re0: link state changed to DOWN
> Dec 8 01:01:55 foo kernel: re0: link state changed to UP
> Dec 8 01:02:02 foo kernel: re0: watchdog timeout
> Dec 8 01:02:02 foo kernel: re0: link state changed to DOWN
> Dec 8 01:02:06 foo kernel: re0: link state changed to UP
> Dec 8 01:02:18 foo kernel: re0: watchdog timeout
> Dec 8 01:02:18 foo kernel: re0: link state changed to DOWN
> Dec 8 01:02:22 foo kernel: re0: link state changed to UP
> Dec 8 01:02:30 foo kernel: re0: watchdog timeout
> Dec 8 01:02:30 foo kernel: re0: link state changed to DOWN
> Dec 8 01:02:34 foo kernel: re0: link state changed to UP
> Dec 8 01:02:45 foo kernel: re0: watchdog timeout
> Dec 8 01:02:45 foo kernel: re0: link state changed to DOWN
> Dec 8 01:02:49 foo kernel: re0: link state changed to UP
> Dec 8 01:03:01 foo kernel: re0: watchdog timeout
> Dec 8 01:03:01 foo kernel: re0: link state changed to DOWN
> Dec 8 01:03:05 foo kernel: re0: link state changed to UP
> Dec 8 01:03:14 foo kernel: re0: watchdog timeout
> Dec 8 01:03:14 foo kernel: re0: link state changed to DOWN
> Dec 8 01:03:18 foo kernel: re0: link state changed to UP
> Dec 8 01:03:26 foo kernel: re0: watchdog timeout
> Dec 8 01:03:26 foo kernel: re0: link state changed to DOWN
> Dec 8 01:03:30 foo kernel: re0: link state changed to UP
> Dec 8 01:03:47 foo kernel: re0: watchdog timeout
> Dec 8 01:03:47 foo kernel: re0: link state changed to DOWN
> Dec 8 01:03:51 foo kernel: re0: link state changed to UP
> Dec 8 01:03:57 foo kernel: re0: watchdog timeout
> Dec 8 01:03:57 foo kernel: re0: link state changed to DOWN
> Dec 8 01:04:01 foo kernel: re0: link state changed to UP
> Dec 8 01:04:31 foo kernel: re0: watchdog timeout
> Dec 8 01:04:31 foo kernel: re0: link state changed to DOWN
> Dec 8 01:04:35 foo kernel: re0: link state changed to UP
> Dec 8 01:05:09 foo kernel: re0: watchdog timeout
> Dec 8 01:05:09 foo kernel: re0: link state changed to DOWN
> Dec 8 01:05:13 foo kernel: re0: link state changed to UP
> Dec 8 01:13:39 foo kernel: re0: watchdog timeout
> Dec 8 01:13:39 foo kernel: re0: link state changed to DOWN
> Dec 8 01:13:41 foo kernel: .
> Dec 8 01:13:42 foo kernel: , 52791.
> Dec 8 01:13:43 foo kernel:
> Dec 8 01:13:43 foo kernel: re0: link state changed to UP
> Dec 8 01:13:44 foo kernel: .
> </snip>
>
> During which I eventually loose connection completely and have to
> manually reboot the box.
>
> When I run Linux on the box all runs well, so I don't suspect the
> ethernet card.
>
> The card is setup with a static IP address:
>
> ifconfig_re0="inet 192.168.1.3/24"
>
> So it really should NOT change the state like this.
>
> Any advice?
You probably want to use the realtek module from ports/pkgs versus the
stock re(4) driver. that's just a guess though, it would be helpful if
you could post what the actual chip is either via dmesg or pciconf.
I have this device, and using the realtek-re-kmod pkg (pkg install
realtek-re-kmod) works well on my system:
<RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet>
Cheers,
-pete
--
Pete Wright
pete@nomadlogic.org
@nomadlogicLA
--------------RgYjHEpEMEjKhYOmeHLjPfPu
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 12/7/22 16:21, <a class="moz-txt-link-abbreviated" href="mailto:iio7@tutanota.com">iio7@tutanota.com</a>
wrote:<br>
</div>
<blockquote type="cite" cite="mid:NIj5vig--3-9@tutanota.com">
<pre class="moz-quote-pre" wrap="">I have recently changed one of my long running boxes from Arch Linux
to FreeBSD 13.1, after which I see this in the log during file transfers:
<snip>
Dec 8 01:01:41 foo kernel: re0: watchdog timeout
Dec 8 01:01:41 foo kernel: re0: link state changed to DOWN
Dec 8 01:01:45 foo kernel: re0: link state changed to UP
Dec 8 01:01:51 foo kernel: re0: watchdog timeout
Dec 8 01:01:51 foo kernel: re0: link state changed to DOWN
Dec 8 01:01:55 foo kernel: re0: link state changed to UP
Dec 8 01:02:02 foo kernel: re0: watchdog timeout
Dec 8 01:02:02 foo kernel: re0: link state changed to DOWN
Dec 8 01:02:06 foo kernel: re0: link state changed to UP
Dec 8 01:02:18 foo kernel: re0: watchdog timeout
Dec 8 01:02:18 foo kernel: re0: link state changed to DOWN
Dec 8 01:02:22 foo kernel: re0: link state changed to UP
Dec 8 01:02:30 foo kernel: re0: watchdog timeout
Dec 8 01:02:30 foo kernel: re0: link state changed to DOWN
Dec 8 01:02:34 foo kernel: re0: link state changed to UP
Dec 8 01:02:45 foo kernel: re0: watchdog timeout
Dec 8 01:02:45 foo kernel: re0: link state changed to DOWN
Dec 8 01:02:49 foo kernel: re0: link state changed to UP
Dec 8 01:03:01 foo kernel: re0: watchdog timeout
Dec 8 01:03:01 foo kernel: re0: link state changed to DOWN
Dec 8 01:03:05 foo kernel: re0: link state changed to UP
Dec 8 01:03:14 foo kernel: re0: watchdog timeout
Dec 8 01:03:14 foo kernel: re0: link state changed to DOWN
Dec 8 01:03:18 foo kernel: re0: link state changed to UP
Dec 8 01:03:26 foo kernel: re0: watchdog timeout
Dec 8 01:03:26 foo kernel: re0: link state changed to DOWN
Dec 8 01:03:30 foo kernel: re0: link state changed to UP
Dec 8 01:03:47 foo kernel: re0: watchdog timeout
Dec 8 01:03:47 foo kernel: re0: link state changed to DOWN
Dec 8 01:03:51 foo kernel: re0: link state changed to UP
Dec 8 01:03:57 foo kernel: re0: watchdog timeout
Dec 8 01:03:57 foo kernel: re0: link state changed to DOWN
Dec 8 01:04:01 foo kernel: re0: link state changed to UP
Dec 8 01:04:31 foo kernel: re0: watchdog timeout
Dec 8 01:04:31 foo kernel: re0: link state changed to DOWN
Dec 8 01:04:35 foo kernel: re0: link state changed to UP
Dec 8 01:05:09 foo kernel: re0: watchdog timeout
Dec 8 01:05:09 foo kernel: re0: link state changed to DOWN
Dec 8 01:05:13 foo kernel: re0: link state changed to UP
Dec 8 01:13:39 foo kernel: re0: watchdog timeout
Dec 8 01:13:39 foo kernel: re0: link state changed to DOWN
Dec 8 01:13:41 foo kernel: .
Dec 8 01:13:42 foo kernel: , 52791.
Dec 8 01:13:43 foo kernel:
Dec 8 01:13:43 foo kernel: re0: link state changed to UP
Dec 8 01:13:44 foo kernel: .
</snip>
During which I eventually loose connection completely and have to
manually reboot the box.
When I run Linux on the box all runs well, so I don't suspect the
ethernet card.
The card is setup with a static IP address:
ifconfig_re0="inet 192.168.1.3/24"
So it really should NOT change the state like this.
Any advice?</pre>
</blockquote>
<br>
You probably want to use the realtek module from ports/pkgs versus
the stock re(4) driver. that's just a guess though, it would be
helpful if you could post what the actual chip is either via dmesg
or pciconf.<br>
<br>
I have this device, and using the realtek-re-kmod pkg (pkg install
realtek-re-kmod) works well on my system:<br>
<span style="color:#000000;background-color:#ffffff;"><RealTek
8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet></span><br>
<br>
Cheers,<br>
-pete<br>
<br>
<pre class="moz-signature" cols="72">--
Pete Wright
<a class="moz-txt-link-abbreviated" href="mailto:pete@nomadlogic.org">pete@nomadlogic.org</a>
@nomadlogicLA</pre>
</body>
</html>
--------------RgYjHEpEMEjKhYOmeHLjPfPu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b0dbf444-6589-6265-6db1-6c6bd458fba8>