From owner-freebsd-current@FreeBSD.ORG Thu Sep 16 20:36:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C47D216A4CE for ; Thu, 16 Sep 2004 20:36:49 +0000 (GMT) Received: from tomoyo.MyBSD.org.my (duke.void.net.my [202.157.186.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id D26DD43D45 for ; Thu, 16 Sep 2004 20:36:44 +0000 (GMT) (envelope-from skywizard@MyBSD.org.my) Received: from kasumi.MyBSD.org.my (unknown [219.94.61.254]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tomoyo.MyBSD.org.my (Postfix) with ESMTP id 51C576CC23; Fri, 17 Sep 2004 04:37:59 +0800 (MYT) Date: Fri, 17 Sep 2004 04:36:53 +0800 From: Ariff Abdullah To: "Kevin Oberman" Message-Id: <20040917043653.419a8e0e.skywizard@MyBSD.org.my> In-Reply-To: <20040916201342.A127A5D04@ptavv.es.net> References: <20040916201342.A127A5D04@ptavv.es.net> Organization: MyBSD X-Mailer: /usr/local/lib/ruby/1.8/net/smtp.rb Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: daniel_k_eriksson@telia.com cc: sos@DeepCore.dk cc: current@freebsd.org Subject: Re: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=207594611 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 20:36:49 -0000 On Thu, 16 Sep 2004 13:13:42 -0700 "Kevin Oberman" wrote: > > From: "Daniel Eriksson" > > Date: Thu, 16 Sep 2004 21:17:45 +0200 > > Sender: owner-freebsd-current@freebsd.org > > > > > > This is a me-too report: > > > > After upgrading a 6-CURRENT kernel and world from > > 2004.09.09.08.00.00 to 2004.09.16.13.00.00, I am now getting these > > messages on a machine that previously worked just fine: > > Thanks! This should greatly simplify my search for the change that > is causing the problem. I can start with 9/9/04 and work forward. I > saw the problem on 9/11/04 in RELENG_5, so I now have a window. I > could shrink it to less than nothing if I was REALLY confident that > nothing was MT5 in less than 3 days, so something the was moved to > RELENG_5 after a very short time is suspect. > > I am currently building a 9/9/04 RELENG_5 kernel and I'll test it > later today (if nobody beats me to it.) One more thing to consider, the default scheduler. I found that those errors occured with SCHED_4BSD (PREEMPTION or NOT), while SCHED_ULE (of course without PREEMPTION, or *else*), nothing such that. Note that this is *my* case, your mileage may vary. -- Ariff Abdullah MyBSD http://www.MyBSD.org.my (IPv6/IPv4) http://staff.MyBSD.org.my (IPv6/IPv4) http://tomoyo.MyBSD.org.my (IPv6/IPv4)