Re: libata pm

2008-02-05 Thread [EMAIL PROTECTED]
(500108 MB) sd 9:4:0:0: [sdp] Write Protect is off sd 9:4:0:0: [sdp] Mode Sense: 00 3a 00 00 sd 9:4:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED

Re: libata pm

2008-02-01 Thread [EMAIL PROTECTED]
of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: libata pm

2008-01-30 Thread [EMAIL PROTECTED]
unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: libata pm

2008-01-28 Thread [EMAIL PROTECTED]
Hello, Am Mo, 28.01.2008, 01:17, schrieb Tejun Heo: Hello, [EMAIL PROTECTED] wrote: With one, two and three drives on the pm I got no errors, so I tried to change the power supply. I got two power supplies for the 16 harddrives and the second one (with all Maxtor drives and the first pm

Re: libata pm

2008-01-27 Thread [EMAIL PROTECTED]
Am So, 27.01.2008, 01:38, schrieb [EMAIL PROTECTED]: Am Sa, 26.01.2008, 23:33, schrieb Tejun Heo: [EMAIL PROTECTED] wrote: I could solve the problem by ncq blacklisting the Maxtor 6V300F0 devices in libata-core.c That's a strange story. The reported error was PHY readiness changed

libata pm

2008-01-26 Thread [EMAIL PROTECTED]
Interrupt :05:01.0[A] - GSI 24 (level, low) - IRQ 24 sata_sil24 :05:01.0: Applying completion IRQ loss on PCI-X errata fix scsi2 : sata_sil24 scsi3 : sata_sil24 scsi4 : sata_sil24 scsi5 : sata_sil24 ata3: SATA max UDMA/100 host [EMAIL PROTECTED] port 0xfeaf irq 24 ata4: SATA max UDMA

Re: libata pm

2008-01-26 Thread [EMAIL PROTECTED]
I could solve the problem by ncq blacklisting the Maxtor 6V300F0 devices in libata-core.c Am Sa, 26.01.2008, 18:03, schrieb [EMAIL PROTECTED]: I'm currently running Linux *** 2.6.23 #1 SMP PREEMPT Sat Jan 26 17:59:58 CET 2008 x86_64 Intel(R) Pentium(R) D CPU 3.20GHz GenuineIntel GNU/Linux

Re: libata pm

2008-01-26 Thread [EMAIL PROTECTED]
Am Sa, 26.01.2008, 23:33, schrieb Tejun Heo: [EMAIL PROTECTED] wrote: I could solve the problem by ncq blacklisting the Maxtor 6V300F0 devices in libata-core.c That's a strange story. The reported error was PHY readiness changed and Device exchanged, both of which point to hotplug event

Re: libata-dev.git rebased

2006-12-13 Thread [EMAIL PROTECTED]
Jeff, Here's my rebased patch. Let me know if there's a problem with it. Thanks, Dan On 12/1/06, Jeff Garzik [EMAIL PROTECTED] wrote: I just rebased all branches of libata-dev.git, and there was a bit of fallout: 1) Dan, I'll have to ask you to resend your sata_vsc MSI patch yet again

Re: kernel history of ide performance

2005-04-05 Thread [EMAIL PROTECTED]
isn't changed as much since it should be rather mature? With kind regards, Oliver Korpilla - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [SATA] libata-dev queue updated

2005-03-29 Thread [EMAIL PROTECTED]
: ---cut here--- To-do list: * VT6420 PATA support = new line * VT6421 PATA support */ ---cut here--- Petr Novák, [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org

Re: [SATA] SATA_SIL and ATI SB400 chipset

2005-03-08 Thread [EMAIL PROTECTED]
list that the RS480M2-IL motherboard's SATA controller works with SATA_SIL driver, as it uses the ATI SB400 Chipset. ;) :) Thanks and with kind regards, Oliver Korpilla - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo

Re: via 6420 pata/sata controller

2005-03-04 Thread [EMAIL PROTECTED]
via82cxxx.c patch: #define PCI_DEVICE_ID_VIA_6420 0x4149 Your's Sincerely Petr Novák [EMAIL PROTECTED] Jeff Garzik napsal(a): If I had to guess, I would try the attached patch. The via82cxxx.c driver is a bit annoying in that, here we do not talk to the ISA bridge but to the PCI device 0x4149