Re: CompactFlash and HD unhappy together on the same IDE channel

Mark Lord wrote: Malcolm Gillies wrote: 2) the HD runs error-free at UDMA/33 when I use a different, PIO-only CF card but otherwise the same cabling, adaptor etc. It would be useful to see the boot log for this scenario. In particular, I'm curious what timings get chosen for the two devices. B

[PATCH 2.6.23-rc3] libata: pata_pdc2027x PLL detection minor cleanup

Minor cleanup to remove the unneeded rmb()s per Jeff's advice. Also removed the pll_clock < 0 check since pll_clock now guaranteed to be >= 0 after Mikael's patch. Signed-off-by: Albert Lee <[EMAIL PROTECTED]> --- Tested ok on both x86 and ppc64, together with Mikael's patch. diff -Nrup 01_mika

[PATCH #upstream-fixes 1/2] libata: invert ATA_PFLAG_INITIALIZING to RUNNING

Invert the meaning of ATA_PFLAG_INITIALIZING and rename it to ATA_PFLAG_RUNNING. This will be used to prevent EH from being scheduled during host removal. Signed-off-by: Tejun Heo <[EMAIL PROTECTED]> --- drivers/ata/libata-core.c |4 +--- drivers/ata/libata-eh.c |2 +- include/linux/li

[PATCH #upstream-fixes 2/2] libata: prevent EH from being scheduled after port is detached

SCSI EH thread is stopped during SCSI host release which can happen after ATA host detach and free. This leads to the following oops. general protection fault: [1] PREEMPT SMP CPU 0 Modules linked in: ahci libata Pid: 98, comm: kblockd/0 Not tainted 2.6.23-rc2-work #19 RIP: 0010:

Re: [PATCH #upstream-fixes 2/2] libata: prevent EH from being scheduled after port is detached

Tejun Heo wrote: > SCSI EH thread is stopped during SCSI host release which can happen > after ATA host detach and free. This leads to the following oops. > > general protection fault: [1] PREEMPT SMP > CPU 0 > Modules linked in: ahci libata > Pid: 98, comm: kblockd/0 Not tainted 2

Re: Resets on sil3124 & sil3726 PMP

Hi Tejun, I've taken your advice, reseat-ed and re-cabled everything. I did find one bad drive that I've removed, but sadly I'm still having problems. I've done some more testing that may be able to help you out. I've tested all 5 WDC drives, they all work. The problem is I get this ex

sata_via: write errors on PATA drive connected to VT6421

Hello, I've built a new machine with VT6421 add-on card that has two SATA and one PATA port: sata_via :00:0a.0: version 2.2 sata_via :00:0a.0: routed to hard irq line 12 scsi0 : sata_via scsi1 : sata_via scsi2 : sata_via ata1: SATA max UDMA/133 cmd 0x00016300 ctl 0x0001630a bmdma 0x000167

[git patches] IDE fixes

Please pull from: master.kernel.org:/pub/scm/linux/kernel/git/bart/ide-2.6.git/ to receive the following updates: arch/cris/arch-v10/drivers/Kconfig |1 + arch/cris/arch-v32/drivers/Kconfig |1 + drivers/ide/Kconfig| 12 - drivers/ide/cris/ide-cris.c|

Re: Resets on sil3124 & sil3726 PMP

Hi Tejun, Just as some further testing and poking I added the drives to the list of disks to disable NCQ for, it didn't resolve the issue. I increased the PMP timeout to 1000 rather then 250 and that didn't resolve the problem either. The interface still has timeout errors writing the ext

4 Port eSATA RAID5/JBOD PCI-E 8x Controller

This looks like a potentially good, cheap candidate for md use. Although Linux support is not explicitly mentioned, SiI 3124 is used. Regards, Richard - To unsubscribe from this list: send the line "unsubscribe linux-ide" in t

[PATCH take #6] [libata] libata driver for bf548 on chip ATAPI controller.

Fix all issues pointed out in Jeff's email. Acked-by: Alan Cox <[EMAIL PROTECTED]> Signed-off-by: Sonic Zhang <[EMAIL PROTECTED]> --- drivers/ata/Kconfig | 16 drivers/ata/Makefile |1 drivers/ata/pata_bf54x.c | 1627 +++ 3 f