Re: PROBLEM: Oops when using both channels of the PDC20262

[Sebastian Witt]

Bartlomiej Zolnierkiewicz wrote:
>
> Please return back to 2.6.5 and try this patch, it disables PIO autotune.
> It fixed hangs for people disabling Promise BIOS but...
>
>  linux-2.6.6-rc2-bk1-bzolnier/drivers/ide/pci/pdc202xx_old.c |    2 +-
>  1 files changed, 1 insertion(+), 1 deletion(-)
>  ...

Thanks, this patch works. I've tested now multiple times a 2.6.5 kernel 
with and without this patch. The BIOS of my controller is also disabled 
if this is important...

PDC20262: IDE controller at PCI slot 0000:00:11.0
PDC20262: chipset revision 1
PDC20262: 100% native mode on irq 17
PDC20262: (U)DMA Burst Bit DISABLED Primary PCI Mode Secondary PCI Mode.
    ide2: BM-DMA at 0xdc00-0xdc07, BIOS settings: hde:DMA, hdf:DMA
    ide3: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdg:DMA, hdh:DMA

                                Ultra66 Chipset.
------------------------------- General Status
---------------------------------
Burst Mode                           : disabled
Host Mode                            : Normal
Bus Clocking                         : 33 PCI Internal
IO pad select                        : 4 mA
Status Polling Period                : 9
Interrupt Check Status Polling Delay : 9
--------------- Primary Channel ---------------- Secondary Channel 
-------------
                enabled                          enabled
66 Clocking     disabled                         disabled
           Mode PCI                         Mode PCI
                FIFO Empty                       FIFO Empty
--------------- drive0 --------- drive1 -------- drive0 ---------- 
drive1 ------
DMA enabled:    yes              yes             yes               yes
DMA Mode:       UDMA 4           UDMA 4          UDMA 4            UDMA 4
PIO Mode:       PIO ?            PIO ?           PIO ?            PIO ?

-------------

If you need some more testing etc. I'm available.

Thanks,
Sebastian

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/