From owner-freebsd-stable@FreeBSD.ORG Fri Feb 29 16:44:46 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 6CA8E106567A for ; Fri, 29 Feb 2008 16:44:46 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id E2C208FC20 for ; Fri, 29 Feb 2008 16:44:45 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so411694uge.37 for ; Fri, 29 Feb 2008 08:44:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=mYflbcP2KaFJCitFS1bsY3/PMlfuh+H7iHMQgfdpHaY=; b=XlAQPlr+cYQlgjsSSKqafZgqsLskF07r8COc3sBia5o3b4FI4FWrILv7SOYN0xt91fr5kkRSzDzYKBqQJNnY7FM/n66ypqXe7up8dJnhbsShrmPacPh51s1esz7Rhv3+PRfBYyIogRpVwFPQtjrt+p/ii9Gok93q6mxTrOqmsow= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hgzqyR4rJUpWyed6asJu+P9bGqJPLRQ/cp6nvFfQZUIvnv7n9NSV5FPQwIGJ68HyVn81jqwPEoENetkxUDynCBwDGBF7kgKoW19bi8SufQXpuFNySQnmk8Xw+W1KMx+/LQYRcVsMr8w9WwDSUxf8/erDuIEZg3xVA5C8hV1OoyU= Received: by 10.66.220.17 with SMTP id s17mr1788958ugg.20.1204303484357; Fri, 29 Feb 2008 08:44:44 -0800 (PST) Received: by 10.66.219.18 with HTTP; Fri, 29 Feb 2008 08:44:44 -0800 (PST) Message-ID: <3aaaa3a0802290844j7ad5707fw436b440a050be803@mail.gmail.com> Date: Fri, 29 Feb 2008 16:44:44 +0000 From: Chris To: "Mark Linimon" In-Reply-To: <20080228222415.GA25086@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47C52948.2070500@sasktel.net> <20080227121129.GA76419@eos.sc1.parodius.com> <47C5ACD0.8000009@sasktel.net> <20080227190509.GA9987@eos.sc1.parodius.com> <3aaaa3a0802280647v25e288fgf786d9c8a0bfc667@mail.gmail.com> <20080228222415.GA25086@soaustin.net> Cc: Jeremy Chadwick , freebsd-stable@freebsd.org, Stephen Hurd Subject: Re: ad0 READ_DMA TIMEOUT errors on install of 7.0-RELEASE 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: Fri, 29 Feb 2008 16:44:46 -0000 On 28/02/2008, Mark Linimon wrote: > On Thu, Feb 28, 2008 at 02:47:28PM +0000, Chris wrote: > > Did they push ahead with release because waiting for the mia dev? > > There's a lot of things that go into deciding when to release. The > release cycle this time was not supposed to be as long as it was. > We kept finding showstoppers and needing to go back and fix them > (especially for things like TCP performance and stability). > > However, sooner or later you do have to release something. There are > bugs in every software program ever released. > > It seems that in certain cases (we're not sure exactly which) the ata > subsystem has regressed. There's debate on the lists about exactly > how common this is: with bugmeister hat on, I don't think it's as > common as some folks seem to think it is (otherwise we would be overwhelmed > with bug reports). > > There's a lot of badly-written firmware out there, and a lot of workarounds > for it in the current ata stack. I'm not familiar with the code, but > fixing all this is a totally non-trivial task. > > Of course it would be nice to have several committers with sufficient > variety of boards, and time, and experience to do a lot more QA, but > we're a volunteer project and have to go with what we have in some cases. > > I'm open to suggestions about how we can get more people involved in > QAing ata. > > mcl > Well I have now 3 servers running freebsd 7 and one is showing the dma errors, a friend of mine has another 2 servers they both dont have dma errors. So the problem doesnt seem to be frequent but is a serious problem when it does occur assuming I am affected by the problem as my problem could be hardware related.. Chris