From nobody@FreeBSD.org  Thu Feb  5 03:34:10 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8744916A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  5 Feb 2004 03:34:10 -0800 (PST)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C211643D66
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  5 Feb 2004 03:34:08 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i15BY8dL012862
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 5 Feb 2004 03:34:08 -0800 (PST)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.10/8.12.10/Submit) id i15BY8Q7012861;
	Thu, 5 Feb 2004 03:34:08 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200402051134.i15BY8Q7012861@www.freebsd.org>
Date: Thu, 5 Feb 2004 03:34:08 -0800 (PST)
From: Murray Baker <murray_baker@NOSPAM.ihug.com.au>
To: freebsd-gnats-submit@FreeBSD.org
Subject: 'ad' driver notebook Intel PIIX4 Fujitsu MHT2040AT hdd: Incorrect xDMAx mode detected.
X-Send-Pr-Version: www-2.0

>Number:         62381
>Category:       i386
>Synopsis:       'ad' driver notebook Intel PIIX4 Fujitsu MHT2040AT hdd: Incorrect xDMAx mode detected.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 05 03:40:00 PST 2004
>Closed-Date:    Mon Aug 16 12:01:53 GMT 2004
>Last-Modified:  Mon Aug 16 12:01:53 GMT 2004
>Originator:     Murray Baker
>Release:        4.9-RELEASE
>Organization:
>Environment:
Sorry, can't do. Problem is no boot. (4.9 boot flop, or 4.9 GENERIC)
>Description:
      'ad' driver detects and sets incorrect xxDMAxx mode, kernel usually
locks up during boot. HW details...
 Compaq Armada 4210T, Intel PIIX4, Fujitsu MHT2040AT (2.5" 40G)
~1 in 10 boots, HDD is detected, 'UDMA33' is shown, and kernel locks up.
~9 in 10 boots, HDD is not detected, and kernel locks up.
Never a successful boot.

Same HW, a 'closed source os' runs ok, reports 'DMA' but not which mode.

Same HDD, same 4.9 GENERIC, 'iron box' desktop VIA Apollo correctly IDs
 HDD and WDMA2 and operates correctly.

>How-To-Repeat:
      Same combination of HW ?
>Fix:
      I have hacked 'ad' to force PIO4 mode and have a stable reliable
system. This is not intended to be a permanent solution. The machine will
build 4.9 GENERIC but not boot with the un-hacked 'ad'.

I can assist with further investigation, testing patches etc.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-i386->sos 
Responsible-Changed-By: vs 
Responsible-Changed-When: Tue Jul 20 08:17:49 GMT 2004 
Responsible-Changed-Why:  
Over to Mr. ATA 

http://www.freebsd.org/cgi/query-pr.cgi?pr=62381 
State-Changed-From-To: open->closed 
State-Changed-By: sos 
State-Changed-When: Mon Aug 16 12:01:03 GMT 2004 
State-Changed-Why:  
Update to -current (5.3) which is known to work on this platform. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=62381 
>Unformatted:
