It seems Brian Somers wrote:
> Hi,
>
> I don't know if you'd class this as a bug report or more as an
> observation. I have a machine with the following:
bug :)
> ata-pci0: <AcerLabs Aladdin ATA-33 controller> port 0xf000-0xf00f at device 15.0 on
>pci0
> ata-pci0: Busmastering DMA supported
> ata0 at 0x01f0 irq 14 on ata-pci0
> ata1 at 0x0170 irq 15 on ata-pci0
> [.....]
> ad0: <FUJITSU M1623TAU/5245> ATA-0 disk at ata0 as master
> ad0: 1623MB (3324384 sectors), 3298 cyls, 16 heads, 63 S/T, 512 B/S
> ad0: 16 secs/int, 1 depth queue, WDMA2
> ad1: <QUANTUM FIREBALL EL7.6A/A08.1100> ATA-4 disk at ata1 as master
> ad1: 7339MB (15032115 sectors), 15907 cyls, 15 heads, 63 S/T, 512 B/S
> ad1: 16 secs/int, 1 depth queue, UDMA33
> ad2: <FUJITSU MPE3273AT/ED-82-25> ATA-4 disk at ata1 as slave
> ad2: 26063MB (53377152 sectors), 52953 cyls, 16 heads, 63 S/T, 512 B/S
> ad2: 16 secs/int, 1 depth queue, UDMA33
>
> Note that ad0 is on a controller of its own, and ad[12] are on the
> second controller. If I put the second (7Gb) disk on the first
> controller as slave, I can't get the machine to boot. The wd driver
> works ok, but ad, although coming up in the ``?'' list in
> vfs_mountroot_ask(), won't boot... I get error 6 when I try
> ufs:/dev/rad0s1a at the prompt.
>
> This has stopped me going to the ata driver on this machine for a
> long time :-/
>
> Moving the two UDMA disks to a controller of their own has solved the
> problem....
Hmm, I'll investigate this, it sure adds more data to the equation..
Thanks for the report!
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message