i386/71924: timeouts with ata+hpt366 controller on BE6II motherboard

[Thierry Herbelot]

The following reply was made to PR i386/71924; it has been noted by GNATS.

From: Thierry Herbelot <thierry at herbelot.com>
To: bug-followup at FreeBSD.org, sandeto_t at yahoo.com
Cc:  
Subject: Re: i386/71924: timeouts with ata+hpt366 controller on BE6II motherboard
Date: Fri, 15 Apr 2005 18:50:43 +0200

 <Me too>
 
 I am having the same problem with a recent -Current :
 the kernel messages preceding the crash were :
 login: ad8: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=9806831
 ad8: FAILURE - device detached
 subdisk8: detached
 ad8: detached
 
 the HPT controller is :
 atapci2: <HighPoint HPT366 UDMA66 controller> port 
 0xb400-0xb407,0xb800-0xb803,0xbc00-0xbcff irq 18 at device 19.0 on pci0
 ata4: <ATA channel 0> on atapci2
 atapci3: <HighPoint HPT366 UDMA66 controller> port 
 0xc000-0xc007,0xc400-0xc403,0xc800-0xc8ff irq 18 at device 19.1 on pci0
 ata5: <ATA channel 0> on atapci3
 
 the disks connected to the HPT-366 are :
 ad8: 9671MB <IBM DTTA-351010 T56OA73A> at ata4-master UDMA33
 ad10: 9671MB <IBM DTTA-351010 T56OA73A> at ata5-master UDMA33
 
 the disks were configured as a gmirror raid :
 GEOM_MIRROR: Device gm0s1 created (id=2240757196).
 GEOM_MIRROR: Device gm0s1: provider ad8s1 detected.
 GEOM_MIRROR: Device gm0s1: provider ad10s1 detected.
 GEOM_MIRROR: Device gm0s1: provider ad10s1 activated.
 GEOM_MIRROR: Device gm0s1: provider ad8s1 activated.
 GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched.
 
 the motherboard is an Abit BP6 (a bit older than the BE6-II of the original 
 report), running SMP.
 
 The kernel run is a straight generic : (with WITNESS and all debug flags)
 FreeBSD 6.0-CURRENT #571: Mon Apr  4 06:25:21 CEST 2005
     XXX at YYY:/usr/obj/usr/src/sys/GENERIC
 
 I have seen the problem three times, once on a disk and twice on the other.
 the problem was seen while building the world, with /usr/src on the gmirror 
 and /usr/obj on another disk.
 
 I have reconnected the disks to the onboard 440BX to determine that my problem 
 does not come from the oldish disks (I have built around 20 worlds with this 
 new configuration, with so far no disk problems).
 
 	Cheers
 
 	TfH