From owner-freebsd-stable@freebsd.org Sun Dec 10 17:40:19 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 458B8E921E8 for ; Sun, 10 Dec 2017 17:40:19 +0000 (UTC) (envelope-from rroot@rootautomation.com) Received: from mail.4fast.net (mail.4fast.net [209.232.198.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.4fast.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2508B78FF2 for ; Sun, 10 Dec 2017 17:40:18 +0000 (UTC) (envelope-from rroot@rootautomation.com) Received: (qmail 17744 invoked by uid 89); 10 Dec 2017 17:35:13 -0000 Received: by simscan 1.4.0 ppid: 17498, pid: 17690, t: 0.2061s scanners: clamav: 0.99.2/m:58/d:24116 Received: from unknown (HELO ?192.168.0.103?) (rroot@rootautomation.com@162.254.181.135) by mail.4fast.net with ESMTPA; 10 Dec 2017 17:35:12 -0000 In-Reply-To: <20171210.210252.781237165340630505.yasu@utahime.org> References: <20171210.210252.781237165340630505.yasu@utahime.org> X-Referenced-Uid: UID153679-1441241621 Thread-Topic: Two problems about ASUS N3150I-C User-Agent: Android MIME-Version: 1.0 Subject: Re: Two problems about ASUS N3150I-C From: Ryan Root Date: Sun, 10 Dec 2017 09:35:10 -0800 To: Yasuhiro KIMURA CC: freebsd-stable@freebsd.org Message-ID: <72573a2b-8a47-4bdf-8877-93c1b4e3da47@rootautomation.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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 17:40:19 -0000 Without more info it's likely going to be hard for anyone to help but both = these symptoms you mention could be possibly related to processes that depe= nd on the system clock not being messed with=2E=C2=A0 Some people these day= s try to cheat on games and stuff like that by using hacks that mess with t= he system clock=2E=C2=A0 Those symptoms you are observing could be a way of= your system letting you know it won't work right if you let apps mess with= the system clock=2E=C2=A0 Maybe not=2E=C2=A0 If others have the same mothe= rboard and use the same Realtek NIC but are not having problems I'd guess i= t's related programs on your system adjusting the system clock=2E=C2=A0 If = that's not the case you may want to make sure ntp is working and maybe chos= e a different ntp server=2E=C2=A0 Maybe it's something else=2E=C2=A0 You'll= likely be asked for more technical feedback from log files though if you w= ant help with this issue=2E=C2=A0 You also could try disabling the onboard = NIC and by a new NIC=2E Ryan =E2=81=A3Sent from BlueMail =E2=80=8B On De= c 10, 2017, 4:02 AM, at 4:02 AM, Yasuhiro KIMURA wrote= : >Hello=2E > >I have two 11=2E1-RELEASE amd64 boxes working as my home ser= vers=2E Their >hardware spec are same and ASUS N3150I-C is used as motherbo= ad=2E And >there are two problems about it=2E > >1=2E 'shutdown -r now' doe= sn'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=2E B= ut, for example, if I try it after one week >of uptime, then it doesn't wor= k anymore=2E OS is shutdown successfully >but reset never happens=2E I upda= ted BIOS of motherboard to latest one >but it didn't fix the problem=2E And= this problem happens on both boxes=2E > >2=2E NIC gets no response with 'r= e0: watchdog timeout' kernel message > >Realtek RTL8111H is used as NIC of = this motherboad=2E Sometime it gets >no response after following kernel mes= sages are displayed some times=2E > >Dec 10 01:11:37 maybe kernel: re0: wat= chdog timeout >Dec 10 01:11:37 maybe kernel: re0: link state changed to DOW= N >Dec 10 01:11:41 maybe kernel: re0: link state changed to UP > >If this h= appens system need to be rebooted=2E It is very variable when >NIC get this= status=2E Sometime it happens after few hours system is up, >but sometimes= it doesn't happen after a month of uptime=2E And this >problem happens onl= y one of two boxes=2E One box is used for internal >services and the other = is used for external ones=2E The problem only >happens on the latter=2E As = is explaind above they have same hardware >spec, but OS settings and/or ins= talled applications are differnt=2E So >it seems some of them specific to t= he latter are cause of NIC hangup=2E > >Then, are there any way to fix thes= e problems or investigate why they >happens? Any suggestions or comments ar= e welcome=2E > >--- >Yasuhiro KIMURA >_____________________________________= __________ >freebsd-stable@freebsd=2Eorg mailing list >https://lists=2Efree= bsd=2Eorg/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to= >"freebsd-stable-unsubscribe@freebsd=2Eorg"