From owner-freebsd-stable@FreeBSD.ORG  Sat Jan  1 12:33:20 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D7C9916A4CE
	for <freebsd-stable@freebsd.org>;
	Sat,  1 Jan 2005 12:33:20 +0000 (GMT)
Received: from gw01.mail.saunalahti.fi (gw01.mail.saunalahti.fi
	[195.197.172.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 04DCE43D46
	for <freebsd-stable@freebsd.org>;
	Sat,  1 Jan 2005 12:33:20 +0000 (GMT)
	(envelope-from pertti.kosunen@pp.nic.fi)
Received: from [127.0.0.1] (KMMLXXXI.dsl.saunalahti.fi [62.142.71.181])
	by gw01.mail.saunalahti.fi (Postfix) with ESMTP id E9F7DACEB5
	for <freebsd-stable@freebsd.org>;
	Sat,  1 Jan 2005 14:33:18 +0200 (EET)
Message-ID: <41D6988F.2000604@pp.nic.fi>
Date: Sat, 01 Jan 2005 14:33:19 +0200
From: Pertti Kosunen <pertti.kosunen@pp.nic.fi>
User-Agent: Mozilla Thunderbird 1.0 / FreeBSD 5.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Fwd: Re: ad2: FAILURE - READ_DMA, but CD on slave controller
	recognized?]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jan 2005 12:33:21 -0000

C. Fischer wrote:

>this has started bugging me ever since moving from 4-stable to 5-stable.
>"ad2", which had been recognized no problem on the former, fails on the
>latter.  since i have a multibooter, i can boot 4.10 residing on "ad2" without
>trouble.  4.10 can access "ad0" and "ad1" fine (this is how i got the initial
>install in place), but i used "ad2" for backups and this doesn't work anymore.
>
>the system otherwise works and there are no DMA related hardware errors ever
>reported except for "ad2" not beeing recognized.  this seems to indicate that
>the problem lies in the initial disk checking phase.

It's pretty common problem with 5.3, one solution is to:

Disable DMA for boot.
cat /boot/loader.conf
hw.ata.ata_dma="0"
hw.ata.atapi_dma="0"

And enable first channel DMA later.
cat /etc/rc.local
atacontrol mode 0 udma4 udma4

http://lists.freebsd.org/pipermail/freebsd-stable/
Searchs previous messages for other workarounds. Disabling APIC might help.