From owner-freebsd-alpha Sun Oct 3 8: 9:51 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from calis.blacksun.org (Calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id 4FE7414D21 for ; Sun, 3 Oct 1999 08:09:47 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id LAA08153; Sun, 3 Oct 1999 11:09:54 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Sun, 3 Oct 1999 11:09:54 -0400 (EDT) From: Don To: "Kenneth D. Merry" Cc: mjacob@feral.com, alpha@FreeBSD.ORG Subject: Re: NCR Problem In-Reply-To: <199910030922.DAA64199@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If he is using -current, then this is almost certainly because of PHK's > changes. It should have been fixed by his checkin earlier Saturday. > > I reproduced this behavior on my test system that has an Adaptec > controller. The symptoms were the same -- a READ command with a block > number specified but with no length. > > I'm not sure why there is a data phase at all, but my guess is that the > drive tries to return at least one block. > > In any case, cvsup again, try a new kernel and see if the problem goes > away. Current from this morning fixed this problem. -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message