From nobody Wed Nov 30 22:43:24 2022 X-Original-To: questions@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 4NMvR7660Yz4jF5p for ; Wed, 30 Nov 2022 22:44:51 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Received: from keymaster.home (ns1.xn--wesstrm-f1a.se [81.4.102.176]) (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 (2048 bits) client-digest SHA256) (Client CN "keymaster.home", Issuer "keymaster.home" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NMvR66F56z4HcX for ; Wed, 30 Nov 2022 22:44:50 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of freebsd-database@pp.dyndns.biz has no SPF policy when checking 81.4.102.176) smtp.mailfrom=freebsd-database@pp.dyndns.biz; dmarc=none Received: from [192.168.254.0] ([192.168.254.0]) by keymaster.home (8.16.1/8.16.1) with ESMTP id 2AUMhOlB059071 for ; Wed, 30 Nov 2022 23:43:25 +0100 (CET) (envelope-from freebsd-database@pp.dyndns.biz) Message-ID: <8c6728f5-5b1c-547d-5c10-0e784a897983@pp.dyndns.biz> Date: Wed, 30 Nov 2022 23:43:24 +0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Subject: Re: DHCP stopped working on RTL8168/8111 Content-Language: en-GB To: questions@freebsd.org References: <54512AE0-6DF7-4653-9FC4-FE2272A721C8@l37.st> From: =?UTF-8?Q?Morgan_Wesstr=c3=b6m?= In-Reply-To: <54512AE0-6DF7-4653-9FC4-FE2272A721C8@l37.st> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-0.24 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; AUTH_NA(1.00)[]; HFILTER_HELO_IP_A(1.00)[keymaster.home]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; R_MIXED_CHARSET(0.56)[subject]; HFILTER_HELO_NORES_A_OR_MX(0.30)[keymaster.home]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ASN(0.00)[asn:198203, ipnet:81.4.100.0/22, country:NL]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[pp.dyndns.biz]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4NMvR66F56z4HcX X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N On 2022-11-30 23:14, Peter Gibbs wrote: >> re0: watchdog timeout It seems you're hitting this old bug which is still open after 10 years: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 The bug states there's a Realtek driver in Ports that doesn't experience this issue but I have never tested it. I tend to stay away from Realtek's NICs in computers I want to run 24/7. AFAIK, with the native driver you need to power cycle the NIC when this happens. Regards Morgan