From owner-freebsd-current  Sun Oct 22  6:43:12 2000
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9050837B4C5; Sun, 22 Oct 2000 06:43:05 -0700 (PDT)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id PAA99326;
	Sun, 22 Oct 2000 15:40:37 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200010221340.PAA99326@freebsd.dk>
Subject: Re: Bug in tagged queuing patches causes read timeouts
In-Reply-To: <xzpwvf472t9.fsf@flood.ping.uio.no> from Dag-Erling Smorgrav at "Oct 20, 2000 02:51:14 am"
To: des@ofug.org (Dag-Erling Smorgrav)
Date: Sun, 22 Oct 2000 15:40:37 +0200 (CEST)
Cc: current@freebsd.org, sos@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Dag-Erling Smorgrav wrote:
> Fresh -CURRENT kernels render the system disk (IBM-DTTA-371010)
> unusable; even small amounts of disk activity cause repeated read
> timeouts. I've narrowed the breakage down: the latest known-good
> kernel is 09/18/2000, earliest known-bad is 09/20/2000, which means
> the September 19th tagged queuing commit is the culprit.

Hmm, have you tried the latest current ?? does that still cause trouble ??

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message