RE: [PATCH 2.6.24] ata_piix: IDE mode SATA patch for Intel ICH10 DeviceID's
-Original Message- From: Jeff Garzik [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 29, 2008 9:14 AM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [PATCH 2.6.24] ata_piix: IDE mode SATA patch for Intel ICH10 DeviceID's Jason Gaston wrote: This patch adds the Intel ICH10 IDE mode SATA Controller DeviceID's. Signed-off-by: Jason Gaston [EMAIL PROTECTED] --- linux-2.6.24/drivers/ata/ata_piix.c.orig 2008-01-24 14:58:37.0 -0800 +++ linux-2.6.24/drivers/ata/ata_piix.c 2008-01-28 14:58:22.0 - 0800 @@ -263,6 +263,14 @@ { 0x8086, 0x292e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci }, /* SATA Controller IDE (Tolapai) */ { 0x8086, 0x5028, PCI_ANY_ID, PCI_ANY_ID, 0, 0, tolapai_sata_ahci }, +/* SATA Controller IDE (ICH10) */ +{ 0x8086, 0x3a00, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci }, +/* SATA Controller IDE (ICH10) */ +{ 0x8086, 0x3a06, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_2port_sata }, +/* SATA Controller IDE (ICH10) */ +{ 0x8086, 0x3a20, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci }, +/* SATA Controller IDE (ICH10) */ +{ 0x8086, 0x3a26, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_2port_sata }, can these do AHCI mode without losing any PATA ports? if so, I would prefer to always drive the hardware in AHCI mode, if it is capable of doing so. They do not have PATA. Jason - 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 4726 Testing
Gaston, for the initial detection failure messages when connected to ICH AHCI, I don't really have much idea what's going on or how to fix it. I suspect it's related to initial FISes from drives arriving asynchronously after hard resets but can't tell much without bus analyzer. Anyways, as EH can handle the case quickly enough, I guess we can leave it at that for now. If you have ideas on what's going on or how to fix it, please lemme know. Thanks. -- Tejun Ok, thank you for all the work that you have done! Jason - 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 4726 Testing
-Original Message- From: [EMAIL PROTECTED] [mailto:linux-ide- [EMAIL PROTECTED] On Behalf Of Tejun Heo Sent: Wednesday, January 09, 2008 7:19 PM To: Gaston, Jason D Cc: Andrew Ryder; linux-ide@vger.kernel.org Subject: Re: Sata 4726 Testing Gaston, Jason D wrote: Attached are two dmesg outputs from 2.6.24-rc7 with only this simg quirk patch applied. The first (dmesg_wSipatch) was generated with the PMP turned off during boot and then powered on, while connected to eSATA. The second (dmesg_poweronoff) was generated with the PMP turned on and connected to eSATA during boot. Then I turned the PMP off, let the drives disappear from /sys/block/ and then turned on the PMP and let the drives reappear in /sys/block/. Please let me know if there is something else I can do. Thanks for testing. It seems the errors you're seeing occur while the drives are initializing. I'll look into that more but with or without the patch, all the devices are detected and usable, right? On 3726, the quirk patch has an unfortunate side effect of causing the first DMA commands to timeout. I'll go and test 4726. Thanks. -- tejun Correct, with or without the patch, the drives are detected and usable. Thanks, Jason - 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 PMP support in 2.6.24-rc3?
-Original Message- From: Tejun Heo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 9:34 PM To: Gaston, Jason D Cc: Tom Evans; linux-ide@vger.kernel.org Subject: Re: SATA PMP support in 2.6.24-rc3? Gaston, Jason D wrote: For reference, here is the dmesg output from the 2.6.24-rc7 kernel W/O the patch applied. Man, this is weird. Do you happen to have a addonics device too? I have one 4726 and two 3726s here and none shows such problem. Also, there are quite a few people confirming that detection is okay on 3726 and 4726s. The failure you're seeing is very similar to what happens on my 4726 if the first fan-out port is not occupied. 4726 behaves very strangely when its first port is empty. Even BIOS has to time out on 4726 if the first port is empty, so I've been thinking it's the peculiarity of the chip (and considering the shitty ATA emulation of the pseudo config device I'm not surprised). Also, marvell PMP and new generation of SIMG PMPs (5723 and friends) work fine with the current code. I've never used windows or the binary only Linux driver. Do they work fine when the first port is unoccupied? Also, is your PMP from addonics? In most reports, they're saying the array is addonics. I'm not sure whether it's because that vendor is so popular that there aren't many alternatives or their hardware is somehow quirky. -- Tejun I am using a Sans Digital PMP, which has a Sil3726CBHU controller in it. I also have an Addonics PMP and it has the same controller in it. Jason - 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 PMP support in 2.6.24-rc3?
-Original Message- From: Tejun Heo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 4:28 AM To: Tom Evans Cc: Gaston, Jason D; linux-ide@vger.kernel.org Subject: Re: SATA PMP support in 2.6.24-rc3? Tom Evans wrote: I'm also seeing this with 2.6.23-rc3 on my Alpha system - sata_sil24 and a SiliconImage PMP. Gaston, Tom, can you guys please apply the attached patch on top of 2.6.24-rc7 and see whether the problem goes away. Thanks. -- Tejun I moved to another ICH9 system that has support for PMP in the BIOS. Before and after the patch, I am able to use the PMP, but I still get errors. I have attached the dmesg output w/ patch to this email. In this case, I booted the system with the PMP turned off and then switched it on after the system was up and running, so you will see the PMP messages at the bottom. On the old system, I get the error messages, but still never see the drives in /sys/block/ Thanks, Jason Linux version 2.6.24-rc7 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue Jan 8 16:18:05 PST 2008 Command line: ro root=/dev/VolGroup00/LogVol00 pci=nommconf rhgb quiet BIOS-provided physical RAM map: BIOS-e820: - 0009d000 (usable) BIOS-e820: 0009d000 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 3e7dd000 (usable) BIOS-e820: 3e7dd000 - 3e81e000 (ACPI NVS) BIOS-e820: 3e81e000 - 3e822000 (reserved) BIOS-e820: 3e822000 - 3e879000 (ACPI NVS) BIOS-e820: 3e879000 - 3ea28000 (reserved) BIOS-e820: 3ea28000 - 3ea3c000 (ACPI NVS) BIOS-e820: 3ea3c000 - 3efde000 (reserved) BIOS-e820: 3efde000 - 3efed000 (ACPI NVS) BIOS-e820: 3efed000 - 3f0d2000 (reserved) BIOS-e820: 3f0d2000 - 3f114000 (ACPI data) BIOS-e820: 3f114000 - 3f134000 (ACPI NVS) BIOS-e820: 3f134000 - 3f136000 (reserved) BIOS-e820: 3f136000 - 3f138000 (ACPI NVS) BIOS-e820: 3f138000 - 3f4d (reserved) BIOS-e820: 3f4d - 3f50 (ACPI NVS) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fed1c000 - fed2 (reserved) BIOS-e820: ffa8 - ffc0 (reserved) BIOS-e820: ffe8 - 0001 (reserved) Entering add_active_range(0, 0, 157) 0 entries of 3200 used Entering add_active_range(0, 256, 255965) 1 entries of 3200 used end_pfn_map = 1048576 DMI 2.4 present. ACPI: RSDP 000F03C0, 0024 (r2AMI) ACPI: XSDT 3F0D6E18, 004C (r1AMI PILLARRK 6222004 MSFT10013) ACPI: FACP 3EFE0918, 00F4 (r4AMI PILLARRK 6222004 MSFT10013) ACPI: DSDT 3EA28018, 98BA (r1AMI PILLARRK0 INTL 20060912) ACPI: FACS 3F136E40, 0040 ACPI: APIC 3F0D2F18, 006C (r2AMI PILLARRK 6222004 MSFT10013) ACPI: MCFG 3F131D18, 003C (r1 A M I GMCH945. 6222004 MSFT 97) ACPI: SSDT 3EFDE918, 0425 (r1 TrmRef PtidDevc 1000 INTL 20060912) ACPI: SSDT 3EFEC698, 05F9 (r1 PmRefCpuPm 3000 INTL 20060912) No NUMA configuration found Faking a node at -3e7dd000 Entering add_active_range(0, 0, 157) 0 entries of 3200 used Entering add_active_range(0, 256, 255965) 1 entries of 3200 used Bootmem setup node 0 -3e7dd000 [e200-e21f] PMD -81000120 on node 0 [e220-e23f] PMD -81000160 on node 0 [e240-e25f] PMD -810001a0 on node 0 [e260-e27f] PMD -810001e0 on node 0 [e280-e29f] PMD -81000220 on node 0 [e2a0-e2bf] PMD -81000260 on node 0 [e2c0-e2df] PMD -810002a0 on node 0 Zone PFN ranges: DMA 0 - 4096 DMA324096 - 1048576 Normal1048576 - 1048576 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0:0 - 157 0: 256 - 255965 On node 0 totalpages: 255866 DMA zone: 56 pages used for memmap DMA zone: 1949 pages reserved DMA zone: 1992 pages, LIFO batch:0 DMA32 zone: 3443 pages used for memmap DMA32 zone: 248426 pages, LIFO batch:31 Normal zone: 0 pages used for memmap Movable zone: 0 pages used for memmap ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 (Bootup-CPU) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high
RE: SATA PMP support in 2.6.24-rc3?
-Original Message- From: Gaston, Jason D Sent: Tuesday, January 08, 2008 4:21 PM To: 'Tejun Heo'; Tom Evans Cc: linux-ide@vger.kernel.org Subject: RE: SATA PMP support in 2.6.24-rc3? -Original Message- From: Tejun Heo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 4:28 AM To: Tom Evans Cc: Gaston, Jason D; linux-ide@vger.kernel.org Subject: Re: SATA PMP support in 2.6.24-rc3? Tom Evans wrote: I'm also seeing this with 2.6.23-rc3 on my Alpha system - sata_sil24 and a SiliconImage PMP. Gaston, Tom, can you guys please apply the attached patch on top of 2.6.24-rc7 and see whether the problem goes away. Thanks. -- Tejun I moved to another ICH9 system that has support for PMP in the BIOS. Before and after the patch, I am able to use the PMP, but I still get errors. I have attached the dmesg output w/ patch to this email. In this case, I booted the system with the PMP turned off and then switched it on after the system was up and running, so you will see the PMP messages at the bottom. On the old system, I get the error messages, but still never see the drives in /sys/block/ Thanks, Jason For reference, here is the dmesg output from the 2.6.24-rc7 kernel W/O the patch applied. Thanks, Jason Linux version 2.6.24-rc7_WOpatch ([EMAIL PROTECTED]) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue Jan 8 17:58:25 PST 2008 Command line: ro root=/dev/VolGroup00/LogVol00 pci=nommconf rhgb quiet BIOS-provided physical RAM map: BIOS-e820: - 0009d000 (usable) BIOS-e820: 0009d000 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 3e7dd000 (usable) BIOS-e820: 3e7dd000 - 3e81e000 (ACPI NVS) BIOS-e820: 3e81e000 - 3e822000 (reserved) BIOS-e820: 3e822000 - 3e879000 (ACPI NVS) BIOS-e820: 3e879000 - 3ea28000 (reserved) BIOS-e820: 3ea28000 - 3ea3c000 (ACPI NVS) BIOS-e820: 3ea3c000 - 3efde000 (reserved) BIOS-e820: 3efde000 - 3efed000 (ACPI NVS) BIOS-e820: 3efed000 - 3f0d2000 (reserved) BIOS-e820: 3f0d2000 - 3f114000 (ACPI data) BIOS-e820: 3f114000 - 3f134000 (ACPI NVS) BIOS-e820: 3f134000 - 3f136000 (reserved) BIOS-e820: 3f136000 - 3f138000 (ACPI NVS) BIOS-e820: 3f138000 - 3f4d (reserved) BIOS-e820: 3f4d - 3f50 (ACPI NVS) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fed1c000 - fed2 (reserved) BIOS-e820: ffa8 - ffc0 (reserved) BIOS-e820: ffe8 - 0001 (reserved) Entering add_active_range(0, 0, 157) 0 entries of 3200 used Entering add_active_range(0, 256, 255965) 1 entries of 3200 used end_pfn_map = 1048576 DMI 2.4 present. ACPI: RSDP 000F03C0, 0024 (r2AMI) ACPI: XSDT 3F0D6E18, 004C (r1AMI PILLARRK 6222004 MSFT10013) ACPI: FACP 3EFE0918, 00F4 (r4AMI PILLARRK 6222004 MSFT10013) ACPI: DSDT 3EA28018, 98BA (r1AMI PILLARRK0 INTL 20060912) ACPI: FACS 3F136E40, 0040 ACPI: APIC 3F0D2F18, 006C (r2AMI PILLARRK 6222004 MSFT10013) ACPI: MCFG 3F131D18, 003C (r1 A M I GMCH945. 6222004 MSFT 97) ACPI: SSDT 3EFDE918, 0425 (r1 TrmRef PtidDevc 1000 INTL 20060912) ACPI: SSDT 3EFEC698, 05F9 (r1 PmRefCpuPm 3000 INTL 20060912) No NUMA configuration found Faking a node at -3e7dd000 Entering add_active_range(0, 0, 157) 0 entries of 3200 used Entering add_active_range(0, 256, 255965) 1 entries of 3200 used Bootmem setup node 0 -3e7dd000 [e200-e21f] PMD -81000120 on node 0 [e220-e23f] PMD -81000160 on node 0 [e240-e25f] PMD -810001a0 on node 0 [e260-e27f] PMD -810001e0 on node 0 [e280-e29f] PMD -81000220 on node 0 [e2a0-e2bf] PMD -81000260 on node 0 [e2c0-e2df] PMD -810002a0 on node 0 Zone PFN ranges: DMA 0 - 4096 DMA324096 - 1048576 Normal1048576 - 1048576 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0:0 - 157 0: 256 - 255965 On node 0 totalpages: 255866 DMA zone: 56 pages used for memmap DMA zone: 1949 pages reserved DMA zone: 1992 pages, LIFO batch:0 DMA32 zone: 3443 pages used for memmap DMA32 zone: 248426 pages, LIFO batch:31 Normal zone: 0 pages used for memmap Movable zone: 0 pages used for memmap ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 (Bootup-CPU) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 ACPI: LAPIC
RE: SATA PMP support in 2.6.24-rc3?
Gaston, Jason D wrote: Does 2.6.24-rc3 support SATA port multipliers? I am getting ata6.03: COMRESET failed (errno=-5) error messages with a SiliconImage PMP connected to an Intel ICH9 SATA controller in AHCI mode. Yeah, it should work. Dmesg output attached. Eeek.. Can you please tell me more about the configuration? Which devices are connected to which downstream port, etc... Thanks. -- tejun I have tried connecting the PMP to several of the ICH9 ports, with no change. Right now, on ICH9, I have: -LH-20A1S DVD on ICH9 port0 -ST3320620AS HD on ICH9 port1 -Sil3726CBHU PMP on ICH9 port2 On the Sil3726 PMP, I have: -ST3750640NS HD on PMP port0 -ST3750640NS HD on PMP port1 Thanks, Jason - 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
SATA PMP support in 2.6.24-rc3?
Does 2.6.24-rc3 support SATA port multipliers? I am getting ata6.03: COMRESET failed (errno=-5) error messages with a SiliconImage PMP connected to an Intel ICH9 SATA controller in AHCI mode. Dmesg output attached. Thanks, Jason Linux version 2.6.24-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue Nov 20 17:43:24 PST 2007 Command line: ro root=/dev/VolGroup00/LogVol00 pci=nommconf rhgb quiet BIOS-provided physical RAM map: BIOS-e820: - 0009c000 (usable) BIOS-e820: 0009c000 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 7d3a (usable) BIOS-e820: 7d3a - 7d3ae000 (ACPI data) BIOS-e820: 7d3ae000 - 7d3f (ACPI NVS) BIOS-e820: 7d3f - 7d70 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ffa6b000 - ffa6c000 (reserved) BIOS-e820: ffb0 - 0001 (reserved) Entering add_active_range(0, 0, 156) 0 entries of 3200 used Entering add_active_range(0, 256, 512928) 1 entries of 3200 used end_pfn_map = 1048576 DMI present. ACPI: RSDP 000F93C0, 0014 (r0 ACPIAM) ACPI: RSDT 7D3A, 0044 (r1 080107 RSDT1024 20070801 MSFT 97) ACPI: FACP 7D3A0200, 0084 (r2 080107 FACP1024 20070801 MSFT 97) ACPI: DSDT 7D3A0490, 687F (r1 VVBLI9 VVBLI958 58 INTL 20051117) ACPI: FACS 7D3AE000, 0040 ACPI: APIC 7D3A0390, 006C (r1 080107 APIC1024 20070801 MSFT 97) ACPI: MCFG 7D3A0450, 003C (r1 080107 OEMMCFG 20070801 MSFT 97) ACPI: OEMB 7D3AE040, 008A (r1 080107 OEMB1024 20070801 MSFT 97) ACPI: ASF! 7D3A6D10, 0099 (r32 LEGEND I865PASF1 INTL 20051117) ACPI: GSCI 7D3AE0D0, 2024 (r1 080107 GMCHSCI 20070801 MSFT 97) ACPI: iEIT 7D3B0100, 00B0 (r1 080107 EITTABLE 20070801 MSFT 97) ACPI: SSDT 7D3B0C90, 0877 (r1 DpgPmmCpuPm 12 INTL 20051117) No NUMA configuration found Faking a node at -7d3a Entering add_active_range(0, 0, 156) 0 entries of 3200 used Entering add_active_range(0, 256, 512928) 1 entries of 3200 used Bootmem setup node 0 -7d3a [e200-e21f] PMD -81000120 on node 0 [e220-e23f] PMD -81000160 on node 0 [e240-e25f] PMD -810001a0 on node 0 [e260-e27f] PMD -810001e0 on node 0 [e280-e29f] PMD -81000220 on node 0 [e2a0-e2bf] PMD -81000260 on node 0 [e2c0-e2df] PMD -810002a0 on node 0 [e2e0-e2ff] PMD -810002e0 on node 0 [e2000100-e200011f] PMD -81000320 on node 0 [e2000120-e200013f] PMD -81000360 on node 0 [e2000140-e200015f] PMD -810003a0 on node 0 [e2000160-e200017f] PMD -810003e0 on node 0 [e2000180-e200019f] PMD -81000420 on node 0 [e20001a0-e20001bf] PMD -81000460 on node 0 Zone PFN ranges: DMA 0 - 4096 DMA324096 - 1048576 Normal1048576 - 1048576 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0:0 - 156 0: 256 - 512928 On node 0 totalpages: 512828 DMA zone: 56 pages used for memmap DMA zone: 1952 pages reserved DMA zone: 1988 pages, LIFO batch:0 DMA32 zone: 6956 pages used for memmap DMA32 zone: 501876 pages, LIFO batch:31 Normal zone: 0 pages used for memmap Movable zone: 0 pages used for memmap ACPI: PM-Timer IO Port: 0x808 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 (Bootup-CPU) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 8000 (gap: 7d70:8170) SMP: Allowing 4 CPUs, 2 hotplug CPUs PERCPU: Allocating 63928 bytes of per cpu data Built 1 zonelists in Node order, mobility grouping on. Total pages: 503864 Policy zone: DMA32 Kernel command line: ro root=/dev/VolGroup00/LogVol00 pci=nommconf rhgb quiet Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) TSC calibrated against PM_TIMER time.c: Detected 2992.493 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled Checking aperture... Memory:
RE: ATAPI devices in AHCI mode not working
-Original Message- From: [EMAIL PROTECTED] [mailto:linux-ide- [EMAIL PROTECTED] On Behalf Of Tejun Heo Sent: Wednesday, October 31, 2007 1:07 AM To: Gaston, Jason D Cc: Alan Cox; linux-ide@vger.kernel.org Subject: Re: ATAPI devices in AHCI mode not working Gaston, Jason D wrote: -Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 3:14 PM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org Subject: Re: ATAPI devices in AHCI mode not working ata1: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xd9101100 irq 216 ata2: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xd9101180 irq 216 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATAPI: ATAPI DVD D DH16D2S, EP52, max UDMA/100 ata1.00: configured for UDMA/100 Much better - no misdetected link type, no device claiming to be PATA when its SATA. Right that eliminates all the obvious goings on being caused by broken devices which is a start. Doesn't shed any light on the rest of it. What happens if you boot with irqpoll enabled ? (wondering if the timeouts are ACPI or IRQ routing stuff) I rebuilt the kernel; the DVD and USB devices are functional now. I'm not sure what the problem was before. On a side note: In 2.6.24.rc1 the DVD starts working right away, but on a SLES10_SP1 kernel, it takes some time for it to step down to a PIO mode before the DVD can be mounted. Oh well. Yeah, there has been quite some update in libata between SLES10_SP1 and 2.6.24-rc1. The controller being ahci, I wonder whether this is caused by the different in check_atapi_dma(). 1. Does other optical drives have the same problem? If not, please post the result of hdparm -I /dev/sr0 with the problematic one attached. 2. If you apply the attached patch to 2.6.24-rc1, does it behave the same as the SLES10SP1 kernel? -- Tejun All of the ATAPI drives seem to have the issue of taking a while to slow down and start working. I will try the patch and see what happens. I will also get the hdparm info from all of the drives I am using to see if something stands out. Thanks, Jason - 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: ATAPI devices in AHCI mode not working
Yeah, there has been quite some update in libata between SLES10_SP1 and 2.6.24-rc1. The controller being ahci, I wonder whether this is caused by the different in check_atapi_dma(). 1. Does other optical drives have the same problem? If not, please post the result of hdparm -I /dev/sr0 with the problematic one attached. 2. If you apply the attached patch to 2.6.24-rc1, does it behave the same as the SLES10SP1 kernel? -- Tejun All of the ATAPI drives seem to have the issue of taking a while to slow down and start working. I will try the patch and see what happens. I will also get the hdparm info from all of the drives I am using to see if something stands out. Thanks, Jason Tejun, Attached are the hdparm -I /dev/cdrom results for the three other drives I am using. These do not include the original drive that had the major issues on, TSSTcorpCD/DVDW SH-S183L. Applying the patch to the 2.6.24-rc kernel did not cause the same behavior, which I am seeing with older kernels. Instead, everything seemed to be fine until I tried to automount the drive, which said that there was no media. I was however, able to manually mount the drive. Thanks, Jason hdparm_cdrom Description: hdparm_cdrom
RE: ATAPI devices in AHCI mode not working
-Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 1:30 PM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org Subject: Re: ATAPI devices in AHCI mode not working ata1.00: ATAPI: TSSTcorpCD/DVDW SH-S183L, SB01, max UDMA/33, ATAPI AN Everyones favourite vendor right now ata1.00: applying bridge limits ata1.00: configured for UDMA/33 It seems to be seeing a SATA/PATA bridge here ? This is a PATA device on a SATA bridge ? If not something is very very broken as we are seeing a SATA cable type and a device not indentifying itself as SATA. ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata1.00: status: { DRDY } We try and talk to it, it ends up stuck busy. ata1: soft resetting link ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/33 ata1: EH complete Kick it, back it comes sr0: scsi3-mmc drive: 32x/40x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:0:0: Attached scsi CD-ROM sr0 Fails again ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata1.00: status: { DRDY } ata1: soft resetting link Repeat ata1: SATA link down (SStatus 11 SControl 300) ata1: failed to recover some devices, retrying in 5 secs ata1: hard resetting link ata1: SATA link down (SStatus 0 SControl 300) ata1: limiting SATA link speed to 1.5 Gbps Try again at 1.5Gbit ata1: hard resetting link ata1: SATA link down (SStatus 0 SControl 310) ata1.00: disabled ata1: EH complete We give up on it. First guess would be to replace the TSST drive with another vendors device and see what occurs. If that does the same thing it eliminates drive firmware. If that doesn't help then need to know more about the bridge etc Alan I have tried a Plextor and a couple of Lite-On DVD drives with the same behavior. Dmesg below for the Lite-On using the 2.6.24-rc1 kernel. The other weird thing, is that when the ATAPI drive is attached and I am seeing this issue, USB also does not work (USB mice and flashdrives). If I reboot with the ATAPI drive disconnected then the USB device work fine. What other information can I give you? Thanks, Jason ... libata version 3.00 loaded. ahci :00:1f.2: version 3.0 ACPI: PCI Interrupt :00:1f.2[B] - GSI 19 (level, low) - IRQ 19 ahci :00:1f.2: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode ahci :00:1f.2: flags: 64bit ncq sntf ilck stag pm led clo pio slum part PCI: Setting latency timer of device :00:1f.2 to 64 scsi0 : ahci scsi1 : ahci ata1: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xd9101100 irq 216 ata2: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xd9101180 irq 216 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATAPI: ATAPI DVD D DH16D2S, EP52, max UDMA/100 ata1.00: configured for UDMA/100 ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-7: WDC WD1600JS-61MHB1, 10.02E01, max UDMA/133 ata2.00: 312581808 sectors, multi 0: LBA48 ata2.00: configured for UDMA/133 scsi 0:0:0:0: CD-ROMATAPIDVD D DH16D2S EP52 PQ: 0 ANSI: 5 scsi 1:0:0:0: Direct-Access ATA WDC WD1600JS-61M 10.0 PQ: 0 ANSI: 5 sd 1:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 1:0:0:0: [sda] Attached SCSI disk sr 0:0:0:0: Attached scsi generic sg0 type 5 sd 1:0:0:0: Attached scsi generic sg1 type 0 ACPI: Processor [CPU1] (supports 8 throttling states) ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata1.00: status: { DRDY } ata1: soft resetting link ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/100 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata1.00: status: { DRDY } ata1: soft resetting link ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/100 ata1: EH complete ReiserFS: sda2: found reiserfs format 3.6 with standard journal ReiserFS: sda2: using ordered data mode ReiserFS
RE: ATAPI devices in AHCI mode not working
-Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 3:14 PM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org Subject: Re: ATAPI devices in AHCI mode not working ata1: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xd9101100 irq 216 ata2: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xd9101180 irq 216 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATAPI: ATAPI DVD D DH16D2S, EP52, max UDMA/100 ata1.00: configured for UDMA/100 Much better - no misdetected link type, no device claiming to be PATA when its SATA. Right that eliminates all the obvious goings on being caused by broken devices which is a start. Doesn't shed any light on the rest of it. What happens if you boot with irqpoll enabled ? (wondering if the timeouts are ACPI or IRQ routing stuff) I rebuilt the kernel; the DVD and USB devices are functional now. I'm not sure what the problem was before. On a side note: In 2.6.24.rc1 the DVD starts working right away, but on a SLES10_SP1 kernel, it takes some time for it to step down to a PIO mode before the DVD can be mounted. Oh well. Thanks! Jason - 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: [PATCH 2.6.23]ata_piix: SATA 2port controller port map fix
this was full of spaces, and should be converted to tabs (I did this manually) In the future, make sure to run your patch through scripts/checkpatch.pl. Some of that script's complaints are a bit insane, but most are good. static const struct piix_map_db *piix_map_db_table[] = { [ich5_sata] = ich5_map_db, [ich6_sata] = ich6_map_db, @@ -463,6 +476,7 @@ [ich6m_sata_ahci] = ich6m_map_db, [ich8_sata_ahci]= ich8_map_db, [tolapai_sata_ahci] = tolapai_map_db, +[ich9_2port_sata] = ich9_2port_map_db, }; static struct ata_port_info piix_port_info[] = { @@ -587,6 +601,17 @@ .udma_mask = ATA_UDMA6, .port_ops = piix_sata_ops, }, + +/* ich9_2port_sata: 12: */ changed this to [ich9_2port_sata] = since we have started using the (C99? gcc?) method of initializing piix_port_info[] array entries based on the given index, rather than simply noting the index in a comment and depending on the order of other entries not to change. Jeff Thank you Jeff! I guess it is time to switch email clients, as this one keeps trashing my file import. I thought I had it worked out, guess not. Thanks again, Jason - 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: ICH9 2 port SATA controller port map?
What is the difference between NA and RV? If the controller only has access to 2 ports, does it matter which I set the nonexistent port values to in the map? NA is used for unimplemented ports of a valid configuration while RV is used to mark invalid MAP value. So, NA should be mixed with P[0-3] while RV can't be mixed with any other values. -- Tejun When you say can't be mixed do you mean I should not have [P0 RV P1 RV] on the same line? If that is the case, then I assume my only choice, for the 2 port controller (physically ports 5 6) would be [P0 NA P1 NA]. Thanks! Jason - 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: ICH9 2 port SATA controller port map?
-Original Message- From: Tejun Heo [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 26, 2007 6:08 PM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org Subject: Re: ICH9 2 port SATA controller port map? Gaston, Jason D wrote: Hello, ICH9 has DeviceID's for 2 port, IDE mode, SATA controllers. The current port map in ata_piix is setup for the 4 port controllers. This seems to work ok, but I wonder if a new port map should be defined for the 2 port controllers, where the two ports are PM, SM? You can refer to the ICH9 Datasheet on intel.com for detail. Yes, please go ahead and define new entry for the controllers. Thanks. -- Tejun What is the difference between NA and RV? If the controller only has access to 2 ports, does it matter which I set the nonexistent port values to in the map? Thanks, Jason - 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
ICH9 2 port SATA controller port map?
Hello, ICH9 has DeviceID's for 2 port, IDE mode, SATA controllers. The current port map in ata_piix is setup for the 4 port controllers. This seems to work ok, but I wonder if a new port map should be defined for the 2 port controllers, where the two ports are PM, SM? You can refer to the ICH9 Datasheet on intel.com for detail. Currently, ata_piix has ICH9 using this: static const struct piix_map_db ich8_map_db = { .mask = 0x3, .port_enable = 0x3, .map = { /* PM PS SM SS MAP */ { P0, P2, P1, P3 }, /* 00b (hardwired when in AHCI) */ { RV, RV, RV, RV }, { P0, P2, IDE, IDE }, /* 10b (IDE mode) */ { RV, RV, RV, RV }, }, }; Thanks, Jason - 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: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai
-Original Message- From: Jeff Garzik [mailto:[EMAIL PROTECTED] Sent: Friday, September 07, 2007 3:39 PM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED] Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai Gaston, Jason D wrote: -Original Message- From: Gaston, Jason D Sent: Friday, August 31, 2007 10:10 AM To: 'Jeff Garzik' Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED] Subject: RE: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai This device has both AHCI and RAID modes that use the ahci driver. Only the RAID mode DID's are being added as the PCI class code support will cover the AHCI mode. Looking at the Generic, PCI class code support section, it uses board_ahci. I assumed that they should be the same as the generic class code support is working on this platform. Thanks, Jason -Original Message- From: Jeff Garzik [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 12:47 AM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED] Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai Jason Gaston wrote: Resend trying to remove 8-bit characters in the email. This patch adds the Intel Tolapai RAID controller DID's for SATA support. Signed-off-by: Jason Gaston [EMAIL PROTECTED] --- linux-2.6.23-rc4/drivers/ata/ahci.c.orig 2007-08-27 18:32:35.0 -0700 +++ linux-2.6.23-rc4/drivers/ata/ahci.c 2007-08-28 16:58:11.0 - 0700 @@ -411,6 +411,8 @@ { PCI_VDEVICE(INTEL, 0x292f), board_ahci_pi }, /* ICH9M */ { PCI_VDEVICE(INTEL, 0x294d), board_ahci_pi }, /* ICH9 */ { PCI_VDEVICE(INTEL, 0x294e), board_ahci_pi }, /* ICH9M */ + { PCI_VDEVICE(INTEL, 0x502a), board_ahci }, /* Tolapai */ + { PCI_VDEVICE(INTEL, 0x502b), board_ahci }, /* Tolapai */ Why did you not use board_ahci_pi? Is the AHCI ports-implemented register unreliable on this platform? Jeff, Do I need to change this to board_ahci_pi or is it ok to leave it at board_ahci, which will be used by the AHCI class code devices? You are the one who needs to answer this question ;-) Most new Intel AHCI have a sane and reliable Ports-Implemented register value even across reset, unlike earlier ones or some clones. For those, we use board_ahci_pi. If PI is not reliable across reset or if BIOS is absent (yes we care about that case, when we do our own PCI resume for example), then you should use board_ahci. Jeff At this time, I don't have any way to test those particular DeviceID's and I know that the AHCI mode DeviceID works by using the class code support. So, I would like to just leave them at they are, if that is ok. Thanks, Jason - 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: [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch for Intel Tolapai
-Original Message- From: Jeff Garzik [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 12:51 AM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch for Intel Tolapai Jason Gaston wrote: Resend trying to remove 8-bit characters in the email. This patch adds the Intel Tolapai IDE mode SATA controller DID's. Signed-off-by: Jason Gaston [EMAIL PROTECTED] applied Jeff, I just noticed that the following section came through as spaces instead of tabs. Do I need to resend a corrected version? +static const struct piix_map_db tolapai_map_db = { +.mask = 0x3, +.port_enable = 0x3, +.map = { +/* PM PS SM SS MAP */ +{ P0, NA, P1, NA }, /* 00b */ +{ RV, RV, RV, RV }, /* 01b */ +{ RV, RV, RV, RV }, /* 10b */ +{ RV, RV, RV, RV }, +}, +}; + Thanks, Jason - 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: [PATCH 2.6.23-rc4][RESEND] ahci: RAID mode SATA patch for Intel Tolapai
-Original Message- From: Gaston, Jason D Sent: Thursday, August 30, 2007 5:54 PM To: [EMAIL PROTECTED]; Gaston, Jason D Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED] Subject: [PATCH 2.6.23-rc4][RESEND] ahci: RAID mode SATA patch for Intel Tolapai Resend without wordwrap. This patch adds the Intel Tolapai RAID controller DID's for SATA support. Signed-off-by: Jason Gaston [EMAIL PROTECTED] --- linux-2.6.23-rc4/drivers/ata/ahci.c.orig 2007-08-27 18:32:35.0 -0700 +++ linux-2.6.23-rc4/drivers/ata/ahci.c2007-08-28 16:58:11.0 - 0700 @@ -411,6 +411,8 @@ { PCI_VDEVICE(INTEL, 0x292f), board_ahci_pi }, /* ICH9M */ { PCI_VDEVICE(INTEL, 0x294d), board_ahci_pi }, /* ICH9 */ { PCI_VDEVICE(INTEL, 0x294e), board_ahci_pi }, /* ICH9M */ + { PCI_VDEVICE(INTEL, 0x502a), board_ahci }, /* Tolapai */ + { PCI_VDEVICE(INTEL, 0x502b), board_ahci }, /* Tolapai */ /* JMicron 360/1/3/5/6, match class to avoid IDE function */ { PCI_VENDOR_ID_JMICRON, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, I am having trouble sending these patches. When I look in the LKML.org message archive, I see =A0 and =20 in the messages. I am using KMail to send these, I have wordwrap turned off and am inserting the patch file. Does anyone know what I am doing wrong? Thanks, Jason - 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
no need to add new DID's to AHCI driver?
Hello, Now that the AHCI driver has support for all controllers with the 0x0106 (AHCI) class code, I am not planning on adding controller DeviceID's for AHCI controllers. I want to verify that this is the correct course of action. Note: I still will have to add the Intel SW RAID controller DeviceID's as they have a 0x0104 (RAID) class code. Thanks, Jason - 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: [patch 2.6.22-rc6] ATA: add a PCI ID for Intel Santa Rosa PATA controller
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 05, 2007 1:30 PM To: Thorsten Leemhuis Cc: Thorsten Leemhuis; Chuck Ebbert; Jeff Garzik; IDE/ATA development list; Gaston, Jason D; Alan Cox; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [patch 2.6.22-rc6] ATA: add a PCI ID for Intel Santa Rosa PATA controller On Wednesday, 4. July 2007, Thorsten Leemhuis wrote: Maybe Alan or someone from Intel can answer that and thus tell us how to move forward; it would be really nice to get the patch that started this thread (it got posted by Chuck again today) could go into 2.6.22, but I assume the time runs away... Jeff is on holiday and Intel doesn't respond at all... So, if someone has a ICH5 or ICH7/7-R with a ATA133 captable HDD... could you please try the following patch? (Of course, I don't know if it works,... It may cause data loss, serve corruption, or damage your controller/hdd/pc, so make backups and keep a first-aid kit handy!) On the other hand, we can leave it, because of a off-by-one error in ata_piix.c, do_pata_set_dmamode, line ~770: [...] Thanks, Chr. I quickly tried this patch on an ICH7-R system with an ATA133 Maxtor HD and it did not seem to do anything bad. I see no difference in function or performance with the patch. Jason - 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: libata: ATA_PIIX missing ICH8M PCIIDs.
FYI: DID 2850 is the PATA IDE controller. Most likely, the laptop does not have SATA drives and is running off of PATA. The old IDE subsystem (piix.c) is where I added that PATA DID to. #define PCI_DEVICE_ID_INTEL_ICH8_6 0x2850 in pci_ids.h Jason -Original Message- From: [EMAIL PROTECTED] [mailto:linux-ide- [EMAIL PROTECTED] On Behalf Of Chr Sent: Monday, June 18, 2007 6:53 AM To: linux-ide@vger.kernel.org Cc: [EMAIL PROTECTED] Subject: Re: libata: ATA_PIIX missing ICH8M PCIIDs. On Monday, 18. June 2007, Alan Cox wrote: On Mon, 18 Jun 2007 15:20:06 +0200 Chr [EMAIL PROTECTED] wrote: Hi, I got a new laptop and I had a little problem that the DVD drive wasn't recognized by libata's piix driver (but the old IDE Subsystem found it!). So, after adding the new pciid 8086:2850 it works! But, I don't know if it's ich_pata_100 or ich_pata_133 since the dvd/cd drives only goes up to udma2 speeds. Its ich_pata_133 - all the newer chips are. They work even better if you set them into AHCI mode in the BIOS and then they should just work with recent kernels as the AHCI driver now matches by class. Alan No go.. I've tried 2.6.20-1-amd64 (debian sid) and a vanilla 2.6.22-rc5. (The problem is that there are no options for that in the BIOS. The BIOS itself is only useful on these laptops, if you want to set a BIOS password, setting the system clock or change the boot order... and nothing else) Thanks, Chr. - 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 - 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: libata: ATA_PIIX missing ICH8M PCIIDs.
I don't think we want to have a PATA controller DID added to the SATA IDE mode driver. This DID is already in the PATA piix.c driver. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:linux-ide- [EMAIL PROTECTED] On Behalf Of Chr Sent: Monday, June 18, 2007 6:20 AM To: linux-ide@vger.kernel.org Cc: [EMAIL PROTECTED] Subject: libata: ATA_PIIX missing ICH8M PCIIDs. Hi, I got a new laptop and I had a little problem that the DVD drive wasn't recognized by libata's piix driver (but the old IDE Subsystem found it!). So, after adding the new pciid 8086:2850 it works! But, I don't know if it's ich_pata_100 or ich_pata_133 since the dvd/cd drives only goes up to udma2 speeds. Thanks, Chr. (I'm not on the list, please keep the cc!) - this patch adds a necessary PCIID for santa rosa's PATA controller. Signed-off-by: Christian Lamparter [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/majordomo-info.html
RE: [PATCH] Add new ICH9M pci id (8086:2850) to ata_piix id list
DID 2850 is not a SATA controller. This is an ICH8 PATA controller DID. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:linux-ide- [EMAIL PROTECTED] On Behalf Of Michal Piotrowski Sent: Sunday, June 17, 2007 2:36 PM To: Maurizio Monge Cc: [EMAIL PROTECTED]; linux-ide@vger.kernel.org; Alan Cox; Jeff Garzik Subject: Re: [PATCH] Add new ICH9M pci id (8086:2850) to ata_piix id list Hi, Maurizio Monge pisze: To make ata_piix recognize my ich9m chip i had to apply the modification that follows. Best regards Maurizio Monge diff -Nurb old/drivers/ata/ata_piix.c new/drivers/ata/ata_piix.c --- old/drivers/ata/ata_piix.c 2007-06-17 23:06:12.0 +0200 +++ new/drivers/ata/ata_piix.c 2007-06-17 23:15:57.0 +0200 @@ -243,6 +243,8 @@ { 0x8086, 0x292d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci }, /* SATA Controller IDE (ICH9M) */ { 0x8086, 0x292e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci }, + /* Mobile SATA Controller IDE (ICH9M) */ + { 0x8086, 0x2850, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_sata_ahci }, http://pci-ids.ucw.cz/iii/?i=80862850 Is this really a SATA controller? ((ICH8M/ICH8M-E) IDE Controller) Regards, Michal -- LOG http://www.stardust.webpages.pl/log/ - 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 - 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: libata: ATA_PIIX missing ICH8M PCIIDs.
I don't think we want to have the same DeviceID supported in more then one driver. Would they not conflict with each other? Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 18, 2007 11:50 AM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org Subject: Re: libata: ATA_PIIX missing ICH8M PCIIDs. On Monday, 18. June 2007, Gaston, Jason D wrote: FYI: DID 2850 is the PATA IDE controller. Most likely, the laptop does not have SATA drives and is running off of PATA. The old IDE subsystem (piix.c) is where I added that PATA DID to. #define PCI_DEVICE_ID_INTEL_ICH8_6 0x2850 in pci_ids.h Jason Yes, I've already said that the old IDE subsystem knows about ICH 8M (read the stuff in the brackets in the original post!). But one day the old ide subsystem will be gone... that's why I've added the PCIID to ata_piix.c today, so I don't have to do it tomorrow. Another thing, Kconfig's description clearly states: config ATA_PIIX tristate Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support ... This option enables support for ICH5/6/7/8 Serial ATA and support for PATA on the Intel ESB/ICH/PIIX3/PIIX4 series host controllers. so, either change the description to: ... support for PATA on the Intel ESB/ICH(all old chipsets 0,2,3M,3,4,5,6,7,7-R; but not 8M, because you have use the old subsystem, for your new technology!)/PIIX3/PIIX4 series or accept the 1+1=2 logic and merge the patch into the git. (hint: but only after changing ich_pata_100 to ich_pata_133 of course!) :D Thanks, Chr. On Monday, 18. June 2007, Alan Cox wrote: On Mon, 18 Jun 2007 15:20:06 +0200 Chr [EMAIL PROTECTED] wrote: Hi, I got a new laptop and I had a little problem that the DVD drive wasn't recognized by libata's piix driver (but the old IDE Subsystem found it!). So, after adding the new pciid 8086:2850 it works! But, I don't know if it's ich_pata_100 or ich_pata_133 since the dvd/cd drives only goes up to udma2 speeds. Its ich_pata_133 - all the newer chips are. They work even better if you set them into AHCI mode in the BIOS and then they should just work with recent kernels as the AHCI driver now matches by class. Alan No go.. I've tried 2.6.20-1-amd64 (debian sid) and a vanilla 2.6.22-rc5. (The problem is that there are no options for that in the BIOS. The BIOS itself is only useful on these laptops, if you want to set a BIOS password, setting the system clock or change the boot order... and nothing else) Thanks, Chr. - - 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
AHCI hot replace sdX incrementing
Hello, When I hot-remove a SATA HD in AHCI mode and then hot-plug the drive back in again, the /dev/sdX number changes to the next available number. Is this going to be a problem when using a RAID array that includes that drive? Thanks, Jason - 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: [PATCH 2.6.19-rc6][RESEND] ata_piix: IDE mode SATA patch for Intel ICH9
Yes, I sent an updated patch that uses the ICH8 structures. Do you need me to send this again. Jason -Original Message- From: Jeff Garzik [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 28, 2006 12:41 AM To: Gaston, Jason D Cc: linux-ide@vger.kernel.org; linux-kernel@vger.kernel.org; [EMAIL PROTECTED] Subject: Re: [PATCH 2.6.19-rc6][RESEND] ata_piix: IDE mode SATA patch for Intel ICH9 did I see a resend of this floating around? I can't apply this one... Looks OK though - 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