Bug 24367

It seems klui@cup.hp.com wrote:
> >Description:
> Sometimes, the ATA driver will find drives that doesn't exist on my A7V
> system. When this happens, I get the following error:
> ata3-slave: ata_command: timeout waiting for intr
> ata3-slave: identify failed
> ata3-master: ata_command: timeout waiting for intr
> ata3-master: identify failed
> 
> My A7V (board rev 1.02, BIOS 1005C) with Duron (800MHz) has a UDMA66 
> drive on the Primary ATA100 (Promise, onboard) controller (only drive on
> this cable) as master, and a DVD-ROM drive on the Secondary IDE
> controller (only drive on this cable) as master.

Uhm firstly the Promise isn't the primary adaptor on those baords, the
VIA '686 is, that migth lead to some confusion.

> On boot, I sometimes see the following:
> [DVD-ROM/master]
> atapci0: <VIA 82C686 ATA66 controller> port 0xd800-0xd80f at device 4.1 on pci0
> ata1: at 0x170 irq 15 on atapci0
>  .
>  .
>  .
> atapci1: <Promise ATA100 controller> port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9
> 407,0x9800-0x9803,0xa000-0xa007 mem 0xe2000000-0xe201ffff irq 10 at device 17.0 
> on pci0
> [Quantum Fireball Plus LM/master]
> ata2: at 0xa000 on atapci1
> [??]
> ata3: at 0x9400 on atapci1
> 
> Sometimes, ata3 doesn't show up, but sometimes, it does. My current
> ATA settings are all PIO. I have no cable dangling off the secondary
> ATA100 connector.

How have you setup your BIOS ? 

-Søren

On Tue, 16 Jan 2001, Soren Schmidt wrote:
> Uhm firstly the Promise isn't the primary adaptor on those baords, the
> VIA '686 is, that migth lead to some confusion.

Sorry about the confusing terminology. I read the labels off of the
A7V (1.02) motherboard. The Promise ATA100 is labeled Primary/Secondary
ATA100 while the '686A is Primary/Secondary IDE.

> 
> > On boot, I sometimes see the following:
> > [DVD-ROM/master]
> > atapci0: <VIA 82C686 ATA66 controller> port 0xd800-0xd80f at device 4.1 on pci0
> > ata1: at 0x170 irq 15 on atapci0
> >  .
> >  .
> >  .
> > atapci1: <Promise ATA100 controller> port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9
> > 407,0x9800-0x9803,0xa000-0xa007 mem 0xe2000000-0xe201ffff irq 10 at device 17.0 
> > on pci0
> > [Quantum Fireball Plus LM/master]
> > ata2: at 0xa000 on atapci1
> > [??]
> > ata3: at 0x9400 on atapci1
> > 
> > Sometimes, ata3 doesn't show up, but sometimes, it does. My current
> > ATA settings are all PIO. I have no cable dangling off the secondary
> > ATA100 connector.
> 
> How have you setup your BIOS ? 

When I was using this configuration, I was had the system boot
in this order:
   DVD-ROM (on VIA '686 secondary-master)
   ATA100/SCSI (Promise primary-master)
   Floppy
   IDE (disabled, as I didn't have any other drives attached)

The boot order of the Promise/SCSI is as per above (ATA100, then
SCSI). My SCSI card isn't installed.

Anything in particular you're interested in my BIOS configuration?

I also get this behavior if I run only on the VIA '686 primary and
secondary connectors:
   UDMA66 drive on primary-master
   DVD-ROM on secondary-master

Boot order is
   DVD-ROM
   IDE
   floppy
   ATA100/SCSI is disabled

I've also disabled the Promise ATA100 bus's BIOS in my current
setup.


Ken

Comment 3 Søren Schmidt 2001-05-29 14:35:21 UTC

State Changed
From-To: open->closed

This should be fixed in 4.3, however some "ghost" drives can 
appear when the hardware delivers bogus data on empty channels.

What constitutes a ghost driver? I still get it on 4.3-stable.


Ken