Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Dec 2008 16:48:51 +0900
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Victor Balada Diaz <victor@bsdes.net>
Cc:        freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org
Subject:   Re: [ATA] and re(4) stability issues
Message-ID:  <20081216074851.GD62771@cdnetworks.co.kr>
In-Reply-To: <20081216071919.GR1320@alf.bsdes.net>
References:  <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> <20081211075707.GH1320@alf.bsdes.net> <20081211081045.GJ1320@alf.bsdes.net> <20081211090056.GH42370@cdnetworks.co.kr> <20081211095021.GL1320@alf.bsdes.net> <20081212121309.GM1320@alf.bsdes.net> <20081215090207.GN1320@alf.bsdes.net> <20081216071919.GR1320@alf.bsdes.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 16, 2008 at 08:19:19AM +0100, Victor Balada Diaz wrote:
 > On Mon, Dec 15, 2008 at 10:02:07AM +0100, Victor Balada Diaz wrote:
 > > Stopped stress testing this morning. After all the weekend testing
 > > seems the re(4) problems were fixed. No single interface up/down error.
 > > netstat -i reports no errors and everything is fine. Thanks a lot!
 > > 
 > > I'm going to deploy the patches on our production machines.
 > > 
 > > I've been able to trigger interrupt storms with ATA code, though.
 > 
 > After deploying it in various machines this night i've found in the
 > logs messages like this one:
 > 
 > re0: watchdog timeout (missed Tx interrupts) -- recovering
 > 
 > I know you told me this is harmless, so this is just so you

Yes, it's not real watchdog timeout as long as re(4) still works
correctly.

 > know it's happening.
 > 

Ok. I'll update re(4) when I find spare time.

-- 
Regards,
Pyun YongHyeon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081216074851.GD62771>