From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 08:10:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D19D1065677; Thu, 11 Dec 2008 08:10:47 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id E36558FC1D; Thu, 11 Dec 2008 08:10:46 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id A7D6D119CF7; Thu, 11 Dec 2008 09:10:45 +0100 (CET) Date: Thu, 11 Dec 2008 09:10:45 +0100 From: Victor Balada Diaz To: Pyun YongHyeon Message-ID: <20081211081045.GJ1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> <20081211075707.GH1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081211075707.GH1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 08:10:47 -0000 On Thu, Dec 11, 2008 at 08:57:07AM +0100, Victor Balada Diaz wrote: > On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote: > > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote: > > > Also i didn't see any problem with interfaces going up and down, > > > but that usually happen after some hours of uptime, so i'll let > > > you know if the error happens again. > > > > > After writing to the HD with dd for a few hours and using > stress -i 10 -d 10 the machine lost connectivity. I waited until > today to be sure if the machine hung, paniced or just lost network > connectivity. I don't have local access or serial access, so this > is the only way i could do it. I've seen in the logs during the > night various messages of: > > > Dec 10 00:33:49 yac kernel: re0: watchdog timeout > Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN > Dec 10 00:33:52 yac kernel: re0: link state changed to UP > > The interface never recovered and i wasn't able to ping the machine > until i rebooted. Nagios was checking all the time and no recovery > happened. > > The netstat -i in daily scripts shows just one Oerrs. I'm used to > have a lot of them, but seems this time the card didn't recover from > the only one. I also want to say that this is not a regression, as > it happened before with 7.1 -BETA 2 code. > > Is there anything more i can try? Sorry it's too early in the morning and i thought today was 10 instead of 11. I don't even know the day i'm today. Looking at today's log i see no link state changed messages but i see this other messages that started happening more or less at the same time i lost connectivity to the server: Dec 10 18:20:32 yac kernel: re0: link state changed to DOWN Dec 10 18:20:32 yac kernel: re0: PHY read failed Sorry for the noise. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros.