Re: CONFIG_IBM_BAY

On Sun 18. Mar - 14:38:42, Tejun Heo wrote: Hello, Kristen Carlson Accardi wrote: 1. It will handle all device types (ATAPI, PATA, SATA, batteries); 2. It will do the right thing on plug and unplug. This means telling the rest of the kernel to disable the device in the bay, for

RE: [git patches] libata fixes

Hello, Can you put the harddisk under high load and see what happens? How often do those errors occur? Care to post full dmesg? I started again a stock 2.6.21-rc4, and ran that : while (/bin/true); do tar jxf linux-2.6.19.1.tar.bz2; rm -rf linux-2.6.19.1; echo -n .; done After several

Re: [git patches] libata fixes

Paul Rolland wrote: Hello, Can you put the harddisk under high load and see what happens? How often do those errors occur? Care to post full dmesg? I started again a stock 2.6.21-rc4, and ran that : while (/bin/true); do tar jxf linux-2.6.19.1.tar.bz2; rm -rf linux-2.6.19.1; echo -n .;

RE: [git patches] libata fixes

Hello, Yeap, more than three HSM violations in ten minutes. That's the criteria for turning off NCQ. Good to see it working. It look like a lot because libata reports all active commands (can't help as on HSM failure, there's no way to determine which caused it) and the SCSI prints

Re: DVD drive fails in 2.6.20.2

Vlad Codrea wrote: Albert Lee wrote: Vlad Codrea wrote: Albert Lee wrote: ata2: protocol 7 task_state 4 === The device interrupts to receive CDB ata2: protocol 7 task_state 4 (dev_stat 0x58) == Good, DRQ seen. CDB sent. ata2: protocol 7 task_state 2 === interrupt. We

RE: [git patches] libata fixes

Hi, This is NCQ protocol violation on the drive's side shown on some early drives. No need to worry too much about it. The drive will just get blacklisted for NCQ and should work fine. Thx. Also, remember one of the problem I have, with ata2 going to timeout because this port of the ICH7

RE: [git patches] libata fixes

Doh ! Got that : ACPI: PCI Interrupt :00:1f.2[B] - GSI 23 (level, low) - IRQ 23 ahci :00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode ahci :00:1f.2: flags: 64bit ncq led clo pio slum part ata1: SATA max UDMA/133 cmd 0xc208e900 ctl 0x

Re: Add suport for Marvell 88SE6121 in ahci

El Domingo, 18 de Marzo de 2007, Tejun Heo escribió: Jose Alberto Reguero wrote: I found that the driver work well for Marvel 6121 without the flag ATA_FLAG_SKIP_D2H_BSY. What is the meaning of this flag? This is usually meaningful with hotplug. The problem is that, on some SATA

[PATCH 2/2] ahci: move port_map handling to ahci_save_initial_config()

Move cross checking between port_map and cap.n_ports into ahci_save_initial_config(). After save_initial_config is done, hpriv-port_map is always setup properly. Tested on JMB363, ICH7 and ICH8 (with dummy ports). Signed-off-by: Tejun Heo [EMAIL PROTECTED] --- This moves all special case fixup

Re: Add suport for Marvell 88SE6121 in ahci

Jose Alberto Reguero wrote: The flag is there primarily for ICH ahci's. Marvell might be different. Care to remove SKIP_D2H_BSY and test a LOT of hotplugging with several different devices? :-) With SKIP_D2H_BSY I have a old dmesg - dmesg1 (2.6.20 I think) I test with and a external

Re: libata: CD and dvd devices not recognized

Hello Bartek, Thanks, does reading from CD/DVD media also work fine now? Yes, drives can read all media cd and dvd I have. It seems that the drive works just fine in PIO mode with pdc202xx_new IDE driver (it doesn't support ATAPI DMA at the moment) and fails with pata_pdc2027x libata (even

Re: libata: CD and dvd devices not recognized

On Sunday 18 March 2007, YUP wrote: Hello Bartek, Thanks, does reading from CD/DVD media also work fine now? Yes, drives can read all media cd and dvd I have. OK, thanks for testing. The conclusion here is that the problem experienced by Yarema is clearly some libata regression wrt

Re: libata: CD and dvd devices not recognized

I'll do it for sure!!! Thanks for help again! Yarema You may also want to bring up this problem with Ubuntu developers. Bart - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at

[PATCH 2.6.22] Add LED trigger to libata core

This duplicates the IDE core LED trigger in the libata core. I plan to use this by allowing PMU LED control on G5 towers. My test platform is a PowerMac 7,3 (Dual G5 2.0GHz, June 2004) with a K2 (sata_svw) controller. Signed-off-by: Tony Vroon [EMAIL PROTECTED] ---

Re: [PATCH] libata: implement and use DMA mask configuration helper

Tejun Heo wrote: Jeff Garzik wrote: Tejun Heo wrote: Implement and use DMA mask configuration helper. Signed-off-by: Tejun Heo [EMAIL PROTECTED] --- This function probably belongs to pci layer. Put it in libata with pci_test_bits() for the time being. AFAIK the default DMA mask is always

Re: [PATCH] libata: implement and use DMA mask configuration helper

Jeff Garzik wrote: Tejun Heo wrote: Jeff Garzik wrote: Tejun Heo wrote: Implement and use DMA mask configuration helper. Signed-off-by: Tejun Heo [EMAIL PROTECTED] --- This function probably belongs to pci layer. Put it in libata with pci_test_bits() for the time being. AFAIK the

Re: CONFIG_IBM_BAY

On Sun, 18 Mar 2007, Tejun Heo wrote: Kristen Carlson Accardi wrote: 1. It will handle all device types (ATAPI, PATA, SATA, batteries); 2. It will do the right thing on plug and unplug. This means telling the rest of the kernel to disable the device in the bay, for example. Right now

Re: CONFIG_IBM_BAY

On Sun, 18 Mar 2007, Holger Macht wrote: those ThinkPads where it is needed. Afterwards it does the corresponding dock/undock request on ibm_acpi. And this works reliably good what I can see from the feedback I already got. But for this to work, userspace would It should work with the generic

Re: CONFIG_IBM_BAY

On Sun 18. Mar - 15:36:52, Henrique de Moraes Holschuh wrote: On Sun, 18 Mar 2007, Holger Macht wrote: those ThinkPads where it is needed. Afterwards it does the corresponding dock/undock request on ibm_acpi. And this works reliably good what I can see from the feedback I already got. But

Re: CONFIG_IBM_BAY

On Sun, 18 Mar 2007, Holger Macht wrote: It doesn't work, I've already tried. The bay driver only emits an event if you really try to remove the bay, but not on docking/undocking. Ah, now I understand what you mean. Looks like we really need the dock driver to sort of like act as a bus. --

[2/6] 2.6.21-rc4: known regressions

This email lists some known regressions in Linus' tree compared to 2.6.20. If you find your name in the Cc header, you are either submitter of one of the bugs, maintainer of an affectected subsystem or driver, a patch of you caused a breakage or I'm considering you in any other way possibly

[3/6] 2.6.21-rc4: known regressions

This email lists some known regressions in Linus' tree compared to 2.6.20. If you find your name in the Cc header, you are either submitter of one of the bugs, maintainer of an affectected subsystem or driver, a patch of you caused a breakage or I'm considering you in any other way possibly

Re: Loading both the pata_atiixp and the ahci driver causes problems

Tejun Heo wrote: Jon Masters wrote: Chuck Ebbert wrote: If you try to load both the pata_atiixp and the ahci driver (for the same ATI SB600 adapter), very strange things happen. The AHCI driver churns for three minutes or so, spewing messages like this, then nothing works: 6ata3: SATA

Re: [PATCH 2.6.22] Add LED trigger to libata core

Tony Vroon wrote: This duplicates the IDE core LED trigger in the libata core. I plan to use this by allowing PMU LED control on G5 towers. My test platform is a PowerMac 7,3 (Dual G5 2.0GHz, June 2004) with a K2 (sata_svw) controller. I think this fits better in

Re: DVD drive fails in 2.6.20.2

Vlad Codrea wrote: Albert Lee wrote: This is the first problem. It's weird to see HSM violation here, without any debug task_state trace. In your previous log, it was detected correctly with debug task_state trace. ata2.00: ATAPI, max MWDMA2, CDB intr ata2.00: configured for MWDMA2 PM: