From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 06:12:38 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 C90AF106568C for ; Wed, 10 Dec 2008 06:12:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id 8CEAC8FC2A for ; Wed, 10 Dec 2008 06:12:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so269543rvf.43 for ; Tue, 09 Dec 2008 22:12:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=QcNRwdk5TE4/471haVCtuNFM69b3fZbafBotTOqSmwA=; b=Dz+mcvUffJjlvXWPDYtcxPnGcySmBvvDV5Df16vh8Xbkt/MnnGKramOWv7S7f2rUzb qmCl8d/aeKvyMaITeAZS3Y97uoTW62Yj37xobLGqSP4F9PNHtC+0TGIYN+fft8LVnXyV KDDTGb9NkmsqPfDPq2QEk/baKc0jNJimmlpX8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=llKlzC31kl9n38b+aeY3qjyk4/6JA956Fb/mV8d1d0/1f4LJmVDw/Aqspa+fr9Fuz4 Xzygh/MKCZ44Zooya4qhXwLi2zjGGLJg4/lXLggUFxejudUVWDvwl0WyP8oLHss37Et3 CAgv2VcF5RgmS+GUqUzRhJuiCPeOP61nl9mAw= Received: by 10.140.193.15 with SMTP id q15mr464966rvf.274.1228889558062; Tue, 09 Dec 2008 22:12:38 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id l31sm1974933rvb.2.2008.12.09.22.12.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 09 Dec 2008 22:12:36 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBA6CTZ7038941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Dec 2008 15:12:29 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBA6CQjL038940; Wed, 10 Dec 2008 15:12:26 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 10 Dec 2008 15:12:26 +0900 From: Pyun YongHyeon To: Victor Balada Diaz Message-ID: <20081210061226.GC37837@cdnetworks.co.kr> References: <20081209185236.GA1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081209185236.GA1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.1i 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 Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 06:12:38 -0000 On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > Hello, > > I got various machines[1] at hetzner.de and I've been having problems > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > been trying to narrow the problem so someone more knowledgeable than me > is able to fix it. This mail is an other attempt to ask a question > with regards ATA code to see if this time i got something. > > For the ones that don't actually know what happened: > > With FreeBSD 7.0 -RELEASE for amd64 and default kernel > the system shared re0 interrupt with OHCI and this caused > re(4) to corrupt packets and create interrupt storms. Tried re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily triggered on systems with > 4GB memory. But I dont' know whether this is related with interrupt storms. > updating to 7.1 -BETA2 and still had some problems with it. > > I've opened the PR kern/128287[2] and Remko quickly answered > with a workaround: that workaround was removing USB support from > my kernel. I did it and re(4) wasn't sharing interrupts anylonger, > and the interrupt storms were gone. Now sometime later the interface > goes up and down from time to time, but less often. Also sometimes > the machine losts the network interface but continues to work. > It seems that your controller supports MSI so you can set a tunable hw.re.msi_disable to 0 to enable MSI. With MSI you can remove interrupt sharing(e.g. add hw.re.msi_disable="0" to /boot/loader.conf file.) However there were several issues on re(4) w.r.t MSI so it was off by default. > I know it continues to work because some days later i can see that > it tried to deliver the status reports but was unable to resolve the > aliases hostnames. I can't ping the machine and i know the network > is OK. If i reboot the machine everything is working again. > Recently I've made small changes to re(4) which may help to detect link state change event. Would you try re(4) in HEAD? -- Regards, Pyun YongHyeon