From owner-freebsd-questions@FreeBSD.ORG Thu May 14 18:38:19 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84226106564A for ; Thu, 14 May 2009 18:38:19 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 4E5F28FC0C for ; Thu, 14 May 2009 18:38:19 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (mailhub.lan.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id CB8FC7E837; Thu, 14 May 2009 10:38:17 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Thu, 14 May 2009 20:38:16 +0200 User-Agent: KMail/1.11.2 (FreeBSD/8.0-CURRENT; KDE/4.2.2; i386; ; ) References: <238d5340e95e0d4c0d3329bf5c5f59f4.squirrel@relay.lc-words.com> <20090513211136.106e75cd@suszko.eu> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905142038.16460.mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: Maciej Suszko , Zbigniew Szalbot Subject: Re: /tmp/security on 7.1-Release X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 18:38:19 -0000 On Thursday 14 May 2009 08:35:40 Zbigniew Szalbot wrote: > Hello, > > >> Ever since upgrading from 7.0-Release to 7.1-Release I get the > >> following in the daily security reports: > >> > >> master.lc-words.com kernel log messages: > >> +++ /tmp/security.yMzCQbS8 2009-05-13 03:01:25.000000000 +0200 > >> +re0: watchdog timeout > >> +re0: link state changed to DOWN > >> +re0: link state changed to UP > >> > >> It just happens around 3 a.m. each day and so I wonder if I should be > >> concerned about it...? > >> > >> Thank you in advance for your suggestions! > > > > I can bet it's NIC related problem, probably your re0 is sharing IRQ > > with something and it's going up/down. The time you see (~3.oo AM) is > > the moment periodic works, so it doesn't mean the problem happend then. > > > > I've seen similar problems on cheap PC hardware with integrated NIC > > and/or external PCI NIC (re/rl/em). Search for 're0: watchdog timeout' > > on google. > > > > The solution is to replace re with something else - em for example, but > > there is no guarantee it's going to work - I had same problems on > > crappy hardware with two identical interfaces plugged in (some model of > > em - IRRC Intel PRO/1000 GT) > > Yes, you are most likely right but I am left wondering why this has never > been a problem on 7.0-Release...? Run a 7.0-RELEASE kernel to be sure of this. It can just be that the hardware went bad around the same time you upgraded. Bad cable or negotiation with a switch are also causes of this. See the DIAGNOSTICS section of the re driver. -- Mel