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: i386/62381: 'ad' driver notebook Intel PIIX4 Fujitsu MHT2040AT hdd: Incorrect xDMAx mode detected. Message-ID: <200402051134.i15BY8Q7012861@www.freebsd.org> Resent-Message-ID: <200402051140.i15Be1va004669@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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: freebsd-i386
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Feb 05 03:40:00 PST 2004
>Closed-Date:
>Last-Modified:
>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:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402051134.i15BY8Q7012861>