From owner-freebsd-current@FreeBSD.ORG  Tue May  4 13:18:52 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 224B916A4CE
	for <current@freebsd.org>; Tue,  4 May 2004 13:18:52 -0700 (PDT)
Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 263FB43D58
	for <current@freebsd.org>; Tue,  4 May 2004 13:18:49 -0700 (PDT)
	(envelope-from w@evip.pl)
Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22)
	id 1BL6NJ-0008CF-Ga
	for current@freebsd.org; Tue, 04 May 2004 22:18:45 +0200
Received: from w by mail.evip.pl with local (Exim 4.22)
	id 1BL6NJ-0008C5-D8
	for current@freebsd.org; Tue, 04 May 2004 22:18:45 +0200
Date: Tue, 4 May 2004 22:18:45 +0200
From: Wiktor Niesiobedzki <bsd@w.evip.pl>
To: current@freebsd.org
Message-ID: <20040504201845.GC304@mail.evip.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Subject: SATA drives won't detect with WITNESS
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 May 2004 20:18:52 -0000

Hi,

My last kernels, build on May 1 (from the fresh CURRENT sources), expose some
strange behaviour, namely, kernel with options added:
options        INVARIANTS
options        INVARIANT_SUPPORT
options        WITNESS
options        WITNESS_SKIPSPIN

Will not detect properly the SATA drive. Anyone also sees this bug? Any clues,
what may cause the problem?

The difference in verbose dmesg, concerning the failing drive is:
With working kernel:
ata3: reset tp1 mask=01 ostat0=7f ostat1=00

With non-working kernel:
ata3: reset tp1 mask=00 ostat0=ff ostat1=00

The mask is different.


Full verbose dmesg from working kernel is available at:
http://www.evip.pl/~w/dmesg-ok-sata.txt

Full verbose dmesg from non-working kernel is available at:
http://www.evip.pl/~w/dmesg-fail-sata.txt



Cheers,

Wiktor Niesiobedzki