NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/57704: re0: RTL8168H/8111H (0x5400) unable to send or receive data. Watchdog timeout.
The following reply was made to PR kern/57704; it has been noted by GNATS.
From: Bartlomiej Krawczyk <bbartlomiej.mail%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc:
Subject: Re: kern/57704: re0: RTL8168H/8111H (0x5400) unable to send or
receive data. Watchdog timeout.
Date: Mon, 8 Jan 2024 21:56:12 +0100
On 11/18/23 19:15, bbartlomiej.mail%gmail.com@localhost wrote:
> [ 1.026877] re0 at pci4 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. 0x15)
> [ 1.026877] re0: interrupting at msix3 vec 0
> [ 1.026877] re0: RTL8168H/8111H (0x5400)
> [ 1.026877] re0: Ethernet address d4:5d:64:7f:f0:27
> [ 1.026877] re0: using 256 tx descriptors
> [ 1.026877] rgephy0 at re0 phy 7: RTL8251 1000BASE-T media interface, rev. 0
> [ 24.878627] re0: watchdog timeout
> [ 37.888665] re0: watchdog timeout
> [ 56.898721] re0: watchdog timeout
> [ 69.908759] re0: watchdog timeout
> [ 75.918777] re0: watchdog timeout
> [ 103.933809] re0: watchdog timeout
What I consistently experience now is if I get any "re0: watchdog
timeout" messages during boot I know network will not work. A workaround
for me is to shut down the system completely and turn the power off so
the network card gets fully powered down. Then after a fresh boot it's
been working so far.
I get the same issues (intermittent again) on 10.0RC2 (fresh installation).
I don't get the same experience with Windows 11 nor with Fedora Linux 38
and 39. Seems like sometimes hardware is in an awkward state and NetBSD
driver doesn't do whatever it needs to do to make it sane.
--
Regards,
Bartlomiej Krawczyk
Home |
Main Index |
Thread Index |
Old Index