2.6.21-rc6-mm1 ATA HPT37x regression

2.6.21-rc6-mm1 ATA HPT37x regression

[John Stoffel]

Hi Jeff and crew,

I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:

    [  148.121490] hpt37x: DPLL did not stabilize.

Where before, under 2.6.21-rc6 I got the following:

    [  173.749349] pata_hpt37x: BIOS has not set timing clocks.
    [  173.752949] hpt37x: HPT302: Bus clock 33MHz.
    [  173.754409] ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 18 (level,
    low) -> IRQ
     18
    [  173.758403] ata5: PATA max UDMA/133 cmd 0x0001ecf8 ctl 0x0001ecf2
    bmdma 0x000
    1e800 irq 18
    [  173.761396] ata6: PATA max UDMA/133 cmd 0x0001ece0 ctl 0x0001ecda
    bmdma 0x000
    1e808 irq 18
    [  173.764319] scsi6 : pata_hpt37x
    [  173.928997] ATA: abnormal status 0x78 on port 0x0001ecff
    [  173.930511] scsi7 : pata_hpt37x
    [  174.094906] ATA: abnormal status 0x8 on port 0x0001ece7


Here's my lspci infomation on the board, it's an addon.  My apologies
for the crappy word wrapping, xterms inside screen, etc. 

  03:06.0 RAID bus controller: Triones Technologies, Inc. HPT302/302N
  (rev 01)
	  Subsystem: Triones Technologies, Inc. Unknown device 0001
	  Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
  ParErr- Step
  ping- SERR+ FastB2B-
	  Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
  >TAbort- <TAbort
  - <MAbort- >SERR- <PERR-
	  Latency: 120 (2000ns min, 2000ns max)
	  Interrupt: pin A routed to IRQ 11
	  Region 0: I/O ports at ecf8 [size=8]
	  Region 1: I/O ports at ecf0 [size=4]
	  Region 2: I/O ports at ece0 [size=8]
	  Region 3: I/O ports at ecd8 [size=4]
	  Region 4: I/O ports at e800 [size=256]
	  Expansion ROM at f9000000 [disabled] [size=128K]
	  Capabilities: [60] Power Management version 2
		  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
  PME(D0-,D1-,D2-,D3hot
  -,D3cold-)
		  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

  03:0a.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891
	  Subsystem: Dell Unknown device 0087
	  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
	  ParErr- Step
  ping- SERR+ FastB2B-
	  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
	  >TAbort- <TAbort
  - <MAbort- >SERR- <PERR-
	  Latency: 64 (9750ns min, 6250ns max), Cache Line Size: 32
	  bytes
	  Interrupt: pin A routed to IRQ 18
	  BIST result: 00
	  Region 0: I/O ports at e400 [disabled] [size=256]
	  Region 1: Memory at f8fff000 (64-bit, non-prefetchable)
	  [size=4K]
	  Expansion ROM at f1000000 [disabled] [size=128K]
	  Capabilities: [dc] Power Management version 1
		  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
	  PME(D0-,D1-,D2-,D3hot
  -,D3cold-)
		  Status: D0 PME-Enable- DSel=0 DScale=0 PME-



I'm moving to 2.6.21-rc7 now, but I'm willing to test out patches as
needed.  I suspect it's the move from the 0.6.0 driver to the 0.6.5
version, and the changes in the hpt_clock hpt37x_timings_* arrays, but
god knows which ones are affecting me.

Thanks,
John

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[Sergei Shtylyov]

Hello.

John Stoffel wrote:

> I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
> and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
> disks are not longer detected and I get the following in the dmesg
> logs:

>     [  148.121490] hpt37x: DPLL did not stabilize.

> Where before, under 2.6.21-rc6 I got the following:

   For the moment I thought you're reporting another hpt366.c driver breakage but then noticed the next line:

>     [  173.749349] pata_hpt37x: BIOS has not set timing clocks.
>     [  173.752949] hpt37x: HPT302: Bus clock 33MHz.

   Obviously this was bacause of switching from PCI to DPLL clock. The old and new drivers are different in how they handle DPLL calibration though.  Could you try hpt366.c (there's been report about its failure too recently -- not enought details yet)?

>     [  173.754409] ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 18 (level,
>     low) -> IRQ
>      18
>     [  173.758403] ata5: PATA max UDMA/133 cmd 0x0001ecf8 ctl 0x0001ecf2
>     bmdma 0x000
>     1e800 irq 18
>     [  173.761396] ata6: PATA max UDMA/133 cmd 0x0001ece0 ctl 0x0001ecda
>     bmdma 0x000
>     1e808 irq 18
>     [  173.764319] scsi6 : pata_hpt37x
>     [  173.928997] ATA: abnormal status 0x78 on port 0x0001ecff
>     [  173.930511] scsi7 : pata_hpt37x
>     [  174.094906] ATA: abnormal status 0x8 on port 0x0001ece7
 
> Here's my lspci infomation on the board, it's an addon.  My apologies
> for the crappy word wrapping, xterms inside screen, etc. 

>   03:06.0 RAID bus controller: Triones Technologies, Inc. HPT302/302N
>   (rev 01)
> 	  Subsystem: Triones Technologies, Inc. Unknown device 0001
> 	  Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
>   ParErr- Step
>   ping- SERR+ FastB2B-
> 	  Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
>   >TAbort- <TAbort
>   - <MAbort- >SERR- <PERR-
> 	  Latency: 120 (2000ns min, 2000ns max)
> 	  Interrupt: pin A routed to IRQ 11
> 	  Region 0: I/O ports at ecf8 [size=8]
> 	  Region 1: I/O ports at ecf0 [size=4]
> 	  Region 2: I/O ports at ece0 [size=8]
> 	  Region 3: I/O ports at ecd8 [size=4]
> 	  Region 4: I/O ports at e800 [size=256]
> 	  Expansion ROM at f9000000 [disabled] [size=128K]
> 	  Capabilities: [60] Power Management version 2
> 		  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
>   PME(D0-,D1-,D2-,D3hot
>   -,D3cold-)
> 		  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

   Yeah, that's a "plain" HPT302 chip with the default 66 MHz DPLL clock.

MBR, Sergei

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[John Stoffel]

>>>>> "Sergei" == Sergei Shtylyov <sshtylyov@ru.mvista.com> writes:

Sergei> Hello.
Sergei> John Stoffel wrote:

>> I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
>> and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
>> disks are not longer detected and I get the following in the dmesg
>> logs:

>> [  148.121490] hpt37x: DPLL did not stabilize.

>> Where before, under 2.6.21-rc6 I got the following:

Sergei> For the moment I thought you're reporting another hpt366.c
Sergei> driver breakage but then noticed the next line:

I used to think that I wanted to use that driver too, but it's not
going to work.  It's because I've got the version 1 of the chip, not
the newer version 2 or higher version.  

It looks like you really mean for me to use the hpt3x2.c driver
instead, since that's the only other one which mentions the
PCI_DEVICE_ID_TTI_HPT302 device id in it's init method.

>> [  173.749349] pata_hpt37x: BIOS has not set timing clocks.
>> [  173.752949] hpt37x: HPT302: Bus clock 33MHz.

Sergei>    Obviously this was bacause of switching from PCI to DPLL
Sergei>    clock. The old and new drivers are different in how they
Sergei>    handle DPLL calibration though.  Could you try hpt366.c
Sergei>    (there's been report about its failure too recently -- not
Sergei>    enought details yet)?

I don't think it will work here, it won't even touch the card since
the pci_device_id won't match at all.  The htp366.c only looks at
HPT366 ids, while mine is an HPT302 id.  

As a quick note, 2.6.21-rc7 is working just fine here.  

>> [  173.754409] ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 18 (level,
>> low) -> IRQ
>> 18
>> [  173.758403] ata5: PATA max UDMA/133 cmd 0x0001ecf8 ctl 0x0001ecf2
>> bmdma 0x000
>> 1e800 irq 18
>> [  173.761396] ata6: PATA max UDMA/133 cmd 0x0001ece0 ctl 0x0001ecda
>> bmdma 0x000
>> 1e808 irq 18
>> [  173.764319] scsi6 : pata_hpt37x
>> [  173.928997] ATA: abnormal status 0x78 on port 0x0001ecff
>> [  173.930511] scsi7 : pata_hpt37x
>> [  174.094906] ATA: abnormal status 0x8 on port 0x0001ece7
 
>> Here's my lspci infomation on the board, it's an addon.  My apologies
>> for the crappy word wrapping, xterms inside screen, etc. 

>> 03:06.0 RAID bus controller: Triones Technologies, Inc. HPT302/302N
>> (rev 01)
>> Subsystem: Triones Technologies, Inc. Unknown device 0001
>> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
>> ParErr- Step
>> ping- SERR+ FastB2B-
>> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
>> >TAbort- <TAbort
>> - <MAbort- >SERR- <PERR-
>> Latency: 120 (2000ns min, 2000ns max)
>> Interrupt: pin A routed to IRQ 11
>> Region 0: I/O ports at ecf8 [size=8]
>> Region 1: I/O ports at ecf0 [size=4]
>> Region 2: I/O ports at ece0 [size=8]
>> Region 3: I/O ports at ecd8 [size=4]
>> Region 4: I/O ports at e800 [size=256]
>> Expansion ROM at f9000000 [disabled] [size=128K]
>> Capabilities: [60] Power Management version 2
>> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
>> PME(D0-,D1-,D2-,D3hot
>> -,D3cold-)
>> Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Sergei> Yeah, that's a "plain" HPT302 chip with the default 66 MHz
Sergei> DPLL clock.

Ok, so do I need to do anything special with the next -mm release and
the next version?

Thanks,
John

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[Sergei Shtylyov]

John Stoffel wrote:

>>>I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
>>>and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
>>>disks are not longer detected and I get the following in the dmesg
>>>logs:
 
>>>[  148.121490] hpt37x: DPLL did not stabilize.
 
>>>Where before, under 2.6.21-rc6 I got the following:
 
> Sergei> For the moment I thought you're reporting another hpt366.c
> Sergei> driver breakage but then noticed the next line:

> I used to think that I wanted to use that driver too, but it's not
> going to work.  It's because I've got the version 1 of the chip, not
> the newer version 2 or higher version.

   So what?

> It looks like you really mean for me to use the hpt3x2.c driver
> instead, since that's the only other one which mentions the
> PCI_DEVICE_ID_TTI_HPT302 device id in it's init method.

   I actually meant drivers/ide/pci/hpt366.c. :-)
 
>>>[  173.749349] pata_hpt37x: BIOS has not set timing clocks.
>>>[  173.752949] hpt37x: HPT302: Bus clock 33MHz.
 
> Sergei>    Obviously this was bacause of switching from PCI to DPLL
> Sergei>    clock. The old and new drivers are different in how they
> Sergei>    handle DPLL calibration though.  Could you try hpt366.c
> Sergei>    (there's been report about its failure too recently -- not
> Sergei>    enought details yet)?

> I don't think it will work here, it won't even touch the card since
> the pci_device_id won't match at all.  The htp366.c only looks at
> HPT366 ids, while mine is an HPT302 id.

   The driver I've named should work (unless something is broken somewhere, that is).
Basically, it uses wider range to calibrate DPLL.

> As a quick note, 2.6.21-rc7 is working just fine here.

   Yeah, it's still using PCI clock.

> Ok, so do I need to do anything special with the next -mm release and
> the next version?

   Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).

> Thanks,
> John

MBR, Sergei

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[Alan Cox]

> > Ok, so do I need to do anything special with the next -mm release and
> > the next version?
> 
>    Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).

Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let me know.
It means that Sergei's DPLL sync code seems to work better than the
vendor code and its time to swap it over.

Oh how I love highpoint PATA

Alan

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[John Stoffel]

>> > Ok, so do I need to do anything special with the next -mm release and
>> > the next version?
>> 
>> Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).

Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan> me know.  It means that Sergei's DPLL sync code seems to work
Alan> better than the vendor code and its time to swap it over.

Ok, I'll give that a whirl under 2.6.21-rc7 tonight.  I'll build them
in modular so I can switch around more easily.  I hope.  :]

Alan> Oh how I love highpoint PATA

It seemed like a good buy at the time when I was researching these
things.  Best bang for the buck I guess.  It's a RocketRaid133 card,
but obviously I got a bum deal somewhere down the line.

Now I've got a Sil3114 SATA controller, which seems to be working just
fine now.  Hopefully it won't have problems like this!

John

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[Sergei Shtylyov]

Hello.

John Stoffel wrote:

>>>>Ok, so do I need to do anything special with the next -mm release and
>>>>the next version?

>>>Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).

> Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
> Alan> me know.  It means that Sergei's DPLL sync code seems to work
> Alan> better than the vendor code and its time to swap it over.

> Ok, I'll give that a whirl under 2.6.21-rc7 tonight.  I'll build them
> in modular so I can switch around more easily.  I hope.  :]

   You can't switch from the old IDE driver -- they're *not* unloadable. :-/

> Alan> Oh how I love highpoint PATA

   More like PITA. :-D

> It seemed like a good buy at the time when I was researching these
> things.  Best bang for the buck I guess.  It's a RocketRaid133 card,

   As for bang, it's true. You can't imagine how many days/nights I spent bangin' with the driver. :-D

> but obviously I got a bum deal somewhere down the line.

   HPT chips are surely not a good example of how to do things, more like an example how *not* to do. :-)

> John

MBR, Sergei

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[Mark Lord]

Sergei Shtylyov wrote:
>
>   HPT chips are surely not a good example of how to do things, more like 
> an example how *not* to do. :-)

That explains a lot!  :)

(guess who's first ATA work was on the Highpoint driver..
 .. no need to post the answer here, though)

Cheers

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[John Stoffel]

>>>>> "John" == John Stoffel <john@stoffel.org> writes:

>>> > Ok, so do I need to do anything special with the next -mm release and
>>> > the next version?
>>> 
>>> Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).

Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan> me know.  It means that Sergei's DPLL sync code seems to work
Alan> better than the vendor code and its time to swap it over.

John> Ok, I'll give that a whirl under 2.6.21-rc7 tonight.  I'll build them
John> in modular so I can switch around more easily.  I hope.  :]

Ok, here's the dmesg output using the hpt366 old IDE driver,
2.6.21-rc7, SMP: 

[  160.926355] HPT302: IDE controller at PCI slot 0000:03:06.0
[  160.928030] ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 18 (level, low) -> IRQ
 18
[  160.931212] HPT302: chipset revision 1
[  160.932801] HPT302: DPLL base: 66 MHz, f_CNT: 100, assuming 33 MHz PCI
[  160.941157] HPT302: using 66 MHz DPLL clock
[  160.942646] HPT302: 100% native mode on irq 18
[  160.943918]     ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:DMA, hdf:pi
o
[  160.946636]     ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:DMA, hdh:pi
o
[  160.949439] Probing IDE interface ide2...
[  161.213560] hde: WDC WD1200JB-00CRA1, ATA DISK drive
[  161.828020] ide2 at 0xecf8-0xecff,0xecf2 on irq 18
[  161.829616] Probing IDE interface ide3...
[  162.094086] hdg: WDC WD1200JB-00EVA0, ATA DISK drive
[  162.709002] ide3 at 0xece0-0xece7,0xecda on irq 18


Which looks ok to me I guess.  It found my MD disks on there and
assmebled them, eventually.  *grin*

I'll reboot and send out the corresponding ATA HPT37x driver dmesg...

John

Re: 2.6.21-rc6-mm1 ATA HPT37x regression

[John Stoffel]

>>>>> "John" == John Stoffel <john@stoffel.org> writes:

>>>>> "John" == John Stoffel <john@stoffel.org> writes:
>>>> > Ok, so do I need to do anything special with the next -mm release and
>>>> > the next version?
>>>> 
>>>> Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).

Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan> me know.  It means that Sergei's DPLL sync code seems to work
Alan> better than the vendor code and its time to swap it over.

John> Ok, I'll give that a whirl under 2.6.21-rc7 tonight.  I'll build them
John> in modular so I can switch around more easily.  I hope.  :]

John> Ok, here's the dmesg output using the hpt366 old IDE driver,
John> 2.6.21-rc7, SMP: 

John> [  160.926355] HPT302: IDE controller at PCI slot 0000:03:06.0
John> [  160.928030] ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 18 (level, low) -> IRQ
John>  18
John> [  160.931212] HPT302: chipset revision 1
John> [  160.932801] HPT302: DPLL base: 66 MHz, f_CNT: 100, assuming 33 MHz PCI
John> [  160.941157] HPT302: using 66 MHz DPLL clock
John> [  160.942646] HPT302: 100% native mode on irq 18
John> [  160.943918]     ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:DMA, hdf:pi
John> o
John> [  160.946636]     ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:DMA, hdh:pi
John> o
John> [  160.949439] Probing IDE interface ide2...
John> [  161.213560] hde: WDC WD1200JB-00CRA1, ATA DISK drive
John> [  161.828020] ide2 at 0xecf8-0xecff,0xecf2 on irq 18
John> [  161.829616] Probing IDE interface ide3...
John> [  162.094086] hdg: WDC WD1200JB-00EVA0, ATA DISK drive
John> [  162.709002] ide3 at 0xece0-0xece7,0xecda on irq 18


John> Which looks ok to me I guess.  It found my MD disks on there and
John> assmebled them, eventually.  *grin*

John> I'll reboot and send out the corresponding ATA HPT37x driver dmesg...

And here's the output (much more verbose!) from the hpt37x ATA driver:

[  158.712007] hpt37x: HPT302: Bus clock 33MHz.
[  158.713390] ACPI: PCI Interrupt 0000:03:06.0[A] -> GSI 18 (level, low) -> IRQ
 18
[  158.716254] ata5: PATA max UDMA/133 cmd 0x0001ecf8 ctl 0x0001ecf2 bmdma 0x000
1e800 irq 18
[  158.719019] ata6: PATA max UDMA/133 cmd 0x0001ece0 ctl 0x0001ecda bmdma 0x000
1e808 irq 18
[  158.722257] scsi7 : pata_hpt37x
[  158.878133] ata5.00: ATA-5: WDC WD1200JB-00CRA1, 17.07W17, max UDMA/100
[  158.879576] ata5.00: 234441648 sectors, multi 16: LBA 
[  158.880934] Find mode for 12 reports C829C62
[  158.882240] Find mode for DMA 69 reports 1C6DDC62
[  158.888152] ata5.00: configured for UDMA/100
[  158.889437] scsi8 : pata_hpt37x
[  158.900338] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[  158.901660] ide: Assuming 33MHz system bus speed for PIO modes; override with
 idebus=xx
[  159.047026] ata6.00: ATA-6: WDC WD1200JB-00EVA0, 15.05R15, max UDMA/100
[  159.048412] ata6.00: 234441648 sectors, multi 16: LBA48 
[  159.050008] Find mode for 12 reports C829C62
[  159.051371] Find mode for DMA 69 reports 1C6DDC62
[  159.057079] ata6.00: configured for UDMA/100
[  159.063655] scsi 7:0:0:0: Direct-Access     ATA      WDC WD1200JB-00C 17.0 PQ
: 0 ANSI: 5
[  159.067506] SCSI device sdi: 234441648 512-byte hdwr sectors (120034 MB)
[  159.069004] sdi: Write Protect is off
[  159.070412] sdi: Mode Sense: 00 3a 00 00
[  159.070487] SCSI device sdi: write cache: enabled, read cache: enabled, doesn
't support DPO or FUA
[  159.073427] SCSI device sdi: 234441648 512-byte hdwr sectors (120034 MB)
[  159.074882] sdi: Write Protect is off
[  159.076262] sdi: Mode Sense: 00 3a 00 00
[  159.076339] SCSI device sdi: write cache: enabled, read cache: enabled, doesn
't support DPO or FUA
[  159.079097]  sdi: sdi1
[  159.097634] sd 7:0:0:0: Attached scsi disk sdi
[  159.099212] sd 7:0:0:0: Attached scsi generic sg9 type 0
[  159.102344] scsi 8:0:0:0: Direct-Access     ATA      WDC WD1200JB-00E 15.0 PQ
: 0 ANSI: 5
[  159.106197] SCSI device sdj: 234441648 512-byte hdwr sectors (120034 MB)
[  159.107722] sdj: Write Protect is off
[  159.109188] sdj: Mode Sense: 00 3a 00 00
[  159.109271] SCSI device sdj: write cache: enabled, read cache: enabled, doesn
't support DPO or FUA
[  159.112455] SCSI device sdj: 234441648 512-byte hdwr sectors (120034 MB)
[  159.114094] sdj: Write Protect is off
[  159.115870] sdj: Mode Sense: 00 3a 00 00
[  159.115943] SCSI device sdj: write cache: enabled, read cache: enabled, doesn
't support DPO or FUA
[  159.118965]  sdj: sdj1
[  159.138036] sd 8:0:0:0: Attached scsi disk sdj
[  159.139682] sd 8:0:0:0: Attached scsi generic sg10 type 0



In both cases, my RAID1 disks are found and come up cleanly, which is
good.  Thanks for all the work you guys have done on the IDE stuff, as
well as the new libATA stuff.

Let me know if you need more testing done here, I've only got a
scratch volume on this raid set.

John