Bug 62381

Summary: 'ad' driver notebook Intel PIIX4 Fujitsu MHT2040AT hdd: Incorrect xDMAx mode detected.
Product: Base System Reporter: Murray Baker <murray_baker>
Component: i386Assignee: Søren Schmidt <sos>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.9-RELEASE   
Hardware: Any   
OS: Any   

Description Murray Baker 2004-02-05 11:40:00 UTC 
      '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.

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.
How-To-Repeat:       Same combination of HW ?
Comment 1 Volker Stolz freebsd_committer freebsd_triage 2004-07-20 09:17:49 UTC 
Responsible Changed
From-To: freebsd-i386->sos

Over to Mr. ATA
Comment 2 Søren Schmidt freebsd_committer freebsd_triage 2004-08-16 13:01:03 UTC 
State Changed
From-To: open->closed

Update to -current (5.3) which is known to work on this platform.