From owner-freebsd-stable@freebsd.org Sun Dec 10 12:04:44 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BCB8E8A911 for ; Sun, 10 Dec 2017 12:04:44 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 0B0966E584 for ; Sun, 10 Dec 2017 12:04:43 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id E074FD235; Sun, 10 Dec 2017 21:04:35 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 7268012921; Sun, 10 Dec 2017 21:04:35 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 34B1112920; Sun, 10 Dec 2017 21:04:35 +0900 (JST) Date: Sun, 10 Dec 2017 21:02:52 +0900 (JST) Message-Id: <20171210.210252.781237165340630505.yasu@utahime.org> To: freebsd-stable@freebsd.org Subject: Two problems about ASUS N3150I-C From: Yasuhiro KIMURA X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 12:04:44 -0000 Hello. I have two 11.1-RELEASE amd64 boxes working as my home servers. Their hardware spec are same and ASUS N3150I-C is used as motherboad. And there are two problems about it. 1. 'shutdown -r now' doesn't work after system has been up for a while If I try 'shutdown -r now' just after system is up or after few hours, it works as is expected. But, for example, if I try it after one week of uptime, then it doesn't work anymore. OS is shutdown successfully but reset never happens. I updated BIOS of motherboard to latest one but it didn't fix the problem. And this problem happens on both boxes. 2. NIC gets no response with 're0: watchdog timeout' kernel message Realtek RTL8111H is used as NIC of this motherboad. Sometime it gets no response after following kernel messages are displayed some times. Dec 10 01:11:37 maybe kernel: re0: watchdog timeout Dec 10 01:11:37 maybe kernel: re0: link state changed to DOWN Dec 10 01:11:41 maybe kernel: re0: link state changed to UP If this happens system need to be rebooted. It is very variable when NIC get this status. Sometime it happens after few hours system is up, but sometimes it doesn't happen after a month of uptime. And this problem happens only one of two boxes. One box is used for internal services and the other is used for external ones. The problem only happens on the latter. As is explaind above they have same hardware spec, but OS settings and/or installed applications are differnt. So it seems some of them specific to the latter are cause of NIC hangup. Then, are there any way to fix these problems or investigate why they happens? Any suggestions or comments are welcome. --- Yasuhiro KIMURA