Date: Thu, 14 May 2009 20:38:16 +0200 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Cc: Maciej Suszko <maciej@suszko.eu>, Zbigniew Szalbot <z.szalbot@lcwords.com> Subject: Re: /tmp/security on 7.1-Release Message-ID: <200905142038.16460.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <c4f9e89a8ebfb27c33a41df880784587.squirrel@relay.lc-words.com> References: <238d5340e95e0d4c0d3329bf5c5f59f4.squirrel@relay.lc-words.com> <20090513211136.106e75cd@suszko.eu> <c4f9e89a8ebfb27c33a41df880784587.squirrel@relay.lc-words.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905142038.16460.mel.flynn%2Bfbsd.questions>