On Thu, Dec 04, 2003 at 02:07:42AM +0900, Ryo HAYASAKA wrote:
> Hi,
> 
> It seems that pdcide also has the similar problem, which causes booting
> process hang.  The following is the booting message of my machine:
> 
> ---------------------------------------------------------------------------
> NetBSD 1.6ZF (BONNIE) #396: Thu Dec  4 00:15:34 JST 2003
> (snip)
> pdcide0 at pci0 dev 9 function 0
> pdcide0: Promise Ultra100TX2/ATA Bus Master IDE Accelerator (rev. 0x01)
> pdcide0: bus-master DMA support present
> pdcide0: primary channel configured to native-PCI mode
> pdcide0: using irq 12 for native-PCI interrupt
> atabus0 at pdcide0 channel 0
> pdcide0: secondary channel configured to native-PCI mode
> atabus1 at pdcide0 channel 1
> (snip)
> Kernelized RAIDframe activated
> vinum: loaded
> IPsec: Initialized Security Association Processing.
> scsibus0: waiting 2 seconds for devices to settle...
> <It hangs here!>
> ---------------------------------------------------------------------------
> 
> If I change pdcide.c just for a test as follows, it successfully boots
> up.

This shouldn't be needed.
I also have a Ultra100TX2 and don't have problems with it:
pdcide2: Promise Ultra100TX2/ATA Bus Master IDE Accelerator (rev. 0x02)
pdcide2: bus-master DMA support present
pdcide2: primary channel configured to native-PCI mode
pdcide2: using irq 12 for native-PCI interrupt
atabus6 at pdcide2 channel 0
pdcide2: secondary channel configured to native-PCI mode
atabus7 at pdcide2 channel 1
wd4 at atabus6 drive 0: <ST38410A>
wd4: drive supports 32-sector PIO transfers, LBA addressing
wd4: 8223 MB, 16708 cyl, 16 head, 63 sec, 512 bytes/sect x 16841664 sectors
wd4: 32-bit data port
wd4: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
wd4(pdcide2:0:0): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using DMA data 
transfers)

Did you check that it is entering an interrupt loop ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--