From owner-freebsd-questions@FreeBSD.ORG  Mon Feb 13 13:31:13 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CDE9816A422
	for <freebsd-questions@freebsd.org>;
	Mon, 13 Feb 2006 13:31:13 +0000 (GMT)
	(envelope-from stcoles@tripos.com)
Received: from mx2.tripos.com (mx1.tripos.com [192.160.145.7])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5738443D6A
	for <freebsd-questions@freebsd.org>;
	Mon, 13 Feb 2006 13:31:12 +0000 (GMT)
	(envelope-from stcoles@tripos.com)
X-SEF-Processed: 5_0_0_713__2006_02_13_07_31_11
X-SEF-B36DBD05-D5C8-4F1B-9AD7-DA304379853F: 1
From: "Steve Coles" <stcoles@tripos.com>
To: <freebsd-questions@freebsd.org>
Date: Mon, 13 Feb 2006 13:28:59 -0000
Message-ID: <028a01c630a1$72ca5b50$649b14ac@tripos.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYwoXGURrWhzQuES0ymZ5Zg9lX7jQ==
X-Spam_score: 0.6
X-Spam_score_int: 6
X-Spam_bar: /
Subject: SMP ATA woes on 6.0-RELEASE
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2006 13:31:13 -0000

I have a strange deterministic boot problem with ATA devices on 2-way dell
precision machines which boot from their SCSI disks. I have 4 of these
boxes, and the only difference is the add-in ATA controller in the affected
box.

A good summary would be "which kernels work":
 
a) GENERIC from the distribution boots fine (uniprocessor)
b) GENERIC built from 6.0-RELEASE boots fine
c) SMP built from 6.0-RELEASE hangs during the ATA probe of my disks
d) <custom> SMP kernel built from 6.0-RELEASE with no ATA options/devices
boots fine
e) <custom> SMP kernel built from 6.0-RELEASE with ATA options/devices hangs
as in c) above

.. It gets weirder

F) <custom> SMP kernel built from 6.0-RELEASE with no ATA options/devices
boots fine (same as option d) above, then I load the ata modules from my
normal login shell:

$> kldload atapci (loads ata.ko etc )
$> Kldload atadisk

.. And it produces a stable, fast, ATA disk subsystem

G) <custom> SMP kernel built from 6.0-RELEASE with no ATA options/devices
boots fine (option d) above with a

atapci_load="YES"
atadisk_load="YES"

In loader.conf produces the same hang as c)

So...I presume the problem is related to the fact that the second CPU must
be launched else the ATA code gets confused with my ATA subsystem (Naieve
explanation of facts)

Q: Is this a known bug ?
Q: If it is, is it fixed in -STABLE ?
Q: If so - when is a good cvsup date that gives me a fixed ata driver with a
"stable stable"

Help is much appreciated

Cheers

Steve