From owner-freebsd-stable  Wed May 29 11:26:28 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 1954837B409
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 May 2002 11:26:19 -0700 (PDT)
Received: from apollo.backplane.com (localhost [127.0.0.1])
	by apollo.backplane.com (8.12.3/8.12.3) with ESMTP id g4TIQH4j062085;
	Wed, 29 May 2002 11:26:18 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.12.3/8.12.3/Submit) id g4TIQECP062080;
	Wed, 29 May 2002 11:26:14 -0700 (PDT)
	(envelope-from dillon)
Date: Wed, 29 May 2002 11:26:14 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200205291826.g4TIQECP062080@apollo.backplane.com>
To: "Robert Blayzor" <rblayzor@inoc.net>,
	"Karl M. Joch" <k.joch@kmjeuro.com>,
	Martin Kraemer <Martin.Kraemer@Fujitsu-Siemens.com>,
	"Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: <freebsd-stable@FreeBSD.ORG>
Subject: 4.6-RC: indefinite wait buffer... (was Re: RE: Swap_pager error)
References:  <003c01c20711$277ce450$6f00000a@z0.inoc.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

    Hi again Robert,

    I'm tying your thread into another ' 4.6-RC: indefinite wait buffer...'
    Since you appear to be having a very similar problem to the one
    Martin is reporting.

    In case anyone in the other thread misssed it, Robert is also reporting
    a similar issue under I/O load, though his is with a RAID controller
    and there is no DAT.

    Martin, I don't know how much time you have to play but if you are 
    adept at CVS you can try compiling various kernels checked out by date
    (cvs's -D option when doing a cvs update or checkout) and attempt to 
    figure out which commit broke your SCSI system.  It can be quite time
    consuming to do this but if the SCSI guys run out of ideas it may be the
    only way to track the bug down.

						-Matt


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