Re: AHCI - remove probing of ata2
Bill Davidsen wrote: Greg Trounson wrote: At the risk of sounding like a "me too" post: I also have an Asus P5W-DH, with the following drives connected: SATA: ST3250820AS, connected to sata1 PATA: HL-DT-ST GSA-H12N, ATAPI DVD Writer, Primary master On bootup of 2.6.19 and 2.6.20, the kernel stalls for 1 minute when probing sata2, eventually giving up and continuing the boot process. There is no physical sata2 connector on the Motherboard, just solder lugs between sata1 and sata3. From other users I understand this is really a Silicon Image SIL4723 SATA to 2-Port SATA splitter. It is detected by the kernel as a disk, as below. The relevant part of the boot process looks like: ... libata version 2.00 loaded. ahci :00:1f.2: version 2.0 ACPI: PCI Interrupt :00:1f.2[B] -> GSI 23 (level, low) -> IRQ 22 PCI: Setting latency timer of device :00:1f.2 to 64 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 0xF882A900 ctl 0x0 bmdma 0x0 irq 219 ata2: SATA max UDMA/133 cmd 0xF882A980 ctl 0x0 bmdma 0x0 irq 219 ata3: SATA max UDMA/133 cmd 0xF882AA00 ctl 0x0 bmdma 0x0 irq 219 ata4: SATA max UDMA/133 cmd 0xF882AA80 ctl 0x0 bmdma 0x0 irq 219 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ...waits 20 seconds... ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ...waits 5 seconds... ata2: port is slow to respond, please be patient (Status 0x80) ...waits 30 seconds... ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ...waits 5 seconds... ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) ... A bit of poking about shows: fdisk -l /dev/sdb Disk /dev/sdb: 0 MB, 327680 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdb doesn't contain a valid partition table So it presents itself as a 320k disk, filled with zeroes as below: dd if=/dev/sdb |hexdump 000 * 005 640+0 records in 640+0 records out 327680 bytes (328 kB) copied, 0.0106662 seconds, 30.7 MB/s ... Is this 320k of cache memory, or in any way some actual storage on the system? Have you tried to write to it out of curiosity? Seems odd that it would be detected if there were nothing at all present, although obviously it could be artifact. According to the product outline at http://www.siliconimage.com/products/product.aspx?id=64, the Silicon Image port multiplier has an EEPROM of unspecified size. With the drive appearing as precisely 320K I wouldn't be surprised if this EEPROM is what it was seeing. Even though it's currently filled with zeros I dare not write to it through fear of bricking the controller. Greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
Greg Trounson wrote: At the risk of sounding like a "me too" post: I also have an Asus P5W-DH, with the following drives connected: SATA: ST3250820AS, connected to sata1 PATA: HL-DT-ST GSA-H12N, ATAPI DVD Writer, Primary master On bootup of 2.6.19 and 2.6.20, the kernel stalls for 1 minute when probing sata2, eventually giving up and continuing the boot process. There is no physical sata2 connector on the Motherboard, just solder lugs between sata1 and sata3. From other users I understand this is really a Silicon Image SIL4723 SATA to 2-Port SATA splitter. It is detected by the kernel as a disk, as below. The relevant part of the boot process looks like: ... libata version 2.00 loaded. ahci :00:1f.2: version 2.0 ACPI: PCI Interrupt :00:1f.2[B] -> GSI 23 (level, low) -> IRQ 22 PCI: Setting latency timer of device :00:1f.2 to 64 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 0xF882A900 ctl 0x0 bmdma 0x0 irq 219 ata2: SATA max UDMA/133 cmd 0xF882A980 ctl 0x0 bmdma 0x0 irq 219 ata3: SATA max UDMA/133 cmd 0xF882AA00 ctl 0x0 bmdma 0x0 irq 219 ata4: SATA max UDMA/133 cmd 0xF882AA80 ctl 0x0 bmdma 0x0 irq 219 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ...waits 20 seconds... ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ...waits 5 seconds... ata2: port is slow to respond, please be patient (Status 0x80) ...waits 30 seconds... ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ...waits 5 seconds... ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) ... A bit of poking about shows: fdisk -l /dev/sdb Disk /dev/sdb: 0 MB, 327680 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdb doesn't contain a valid partition table So it presents itself as a 320k disk, filled with zeroes as below: dd if=/dev/sdb |hexdump 000 * 005 640+0 records in 640+0 records out 327680 bytes (328 kB) copied, 0.0106662 seconds, 30.7 MB/s Note that this is not a fatal error. The machine still boots eventually, but the seemingly mandatory 60 second pause makes startup rather cumbersome for the user. So far none of the suggested fixes have managed to stop ata2 from being detected. (noprobe=ata2, irqpoll, etc). I understand this problem wasn't present in 2.6.16 so the problem must lie in some patch since then. I see Tejun is working towards patches for this and I would be happy to try them here. Is this 320k of cache memory, or in any way some actual storage on the system? Have you tried to write to it out of curiosity? Seems odd that it would be detected if there were nothing at all present, although obviously it could be artifact. -- Bill Davidsen <[EMAIL PROTECTED]> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
Greg Trounson wrote: At the risk of sounding like a me too post: I also have an Asus P5W-DH, with the following drives connected: SATA: ST3250820AS, connected to sata1 PATA: HL-DT-ST GSA-H12N, ATAPI DVD Writer, Primary master On bootup of 2.6.19 and 2.6.20, the kernel stalls for 1 minute when probing sata2, eventually giving up and continuing the boot process. There is no physical sata2 connector on the Motherboard, just solder lugs between sata1 and sata3. From other users I understand this is really a Silicon Image SIL4723 SATA to 2-Port SATA splitter. It is detected by the kernel as a disk, as below. The relevant part of the boot process looks like: ... libata version 2.00 loaded. ahci :00:1f.2: version 2.0 ACPI: PCI Interrupt :00:1f.2[B] - GSI 23 (level, low) - IRQ 22 PCI: Setting latency timer of device :00:1f.2 to 64 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 0xF882A900 ctl 0x0 bmdma 0x0 irq 219 ata2: SATA max UDMA/133 cmd 0xF882A980 ctl 0x0 bmdma 0x0 irq 219 ata3: SATA max UDMA/133 cmd 0xF882AA00 ctl 0x0 bmdma 0x0 irq 219 ata4: SATA max UDMA/133 cmd 0xF882AA80 ctl 0x0 bmdma 0x0 irq 219 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ...waits 20 seconds... ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ...waits 5 seconds... ata2: port is slow to respond, please be patient (Status 0x80) ...waits 30 seconds... ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ...waits 5 seconds... ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) ... A bit of poking about shows: fdisk -l /dev/sdb Disk /dev/sdb: 0 MB, 327680 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdb doesn't contain a valid partition table So it presents itself as a 320k disk, filled with zeroes as below: dd if=/dev/sdb |hexdump 000 * 005 640+0 records in 640+0 records out 327680 bytes (328 kB) copied, 0.0106662 seconds, 30.7 MB/s Note that this is not a fatal error. The machine still boots eventually, but the seemingly mandatory 60 second pause makes startup rather cumbersome for the user. So far none of the suggested fixes have managed to stop ata2 from being detected. (noprobe=ata2, irqpoll, etc). I understand this problem wasn't present in 2.6.16 so the problem must lie in some patch since then. I see Tejun is working towards patches for this and I would be happy to try them here. Is this 320k of cache memory, or in any way some actual storage on the system? Have you tried to write to it out of curiosity? Seems odd that it would be detected if there were nothing at all present, although obviously it could be artifact. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
Bill Davidsen wrote: Greg Trounson wrote: At the risk of sounding like a me too post: I also have an Asus P5W-DH, with the following drives connected: SATA: ST3250820AS, connected to sata1 PATA: HL-DT-ST GSA-H12N, ATAPI DVD Writer, Primary master On bootup of 2.6.19 and 2.6.20, the kernel stalls for 1 minute when probing sata2, eventually giving up and continuing the boot process. There is no physical sata2 connector on the Motherboard, just solder lugs between sata1 and sata3. From other users I understand this is really a Silicon Image SIL4723 SATA to 2-Port SATA splitter. It is detected by the kernel as a disk, as below. The relevant part of the boot process looks like: ... libata version 2.00 loaded. ahci :00:1f.2: version 2.0 ACPI: PCI Interrupt :00:1f.2[B] - GSI 23 (level, low) - IRQ 22 PCI: Setting latency timer of device :00:1f.2 to 64 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 0xF882A900 ctl 0x0 bmdma 0x0 irq 219 ata2: SATA max UDMA/133 cmd 0xF882A980 ctl 0x0 bmdma 0x0 irq 219 ata3: SATA max UDMA/133 cmd 0xF882AA00 ctl 0x0 bmdma 0x0 irq 219 ata4: SATA max UDMA/133 cmd 0xF882AA80 ctl 0x0 bmdma 0x0 irq 219 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ...waits 20 seconds... ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ...waits 5 seconds... ata2: port is slow to respond, please be patient (Status 0x80) ...waits 30 seconds... ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ...waits 5 seconds... ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) ... A bit of poking about shows: fdisk -l /dev/sdb Disk /dev/sdb: 0 MB, 327680 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdb doesn't contain a valid partition table So it presents itself as a 320k disk, filled with zeroes as below: dd if=/dev/sdb |hexdump 000 * 005 640+0 records in 640+0 records out 327680 bytes (328 kB) copied, 0.0106662 seconds, 30.7 MB/s ... Is this 320k of cache memory, or in any way some actual storage on the system? Have you tried to write to it out of curiosity? Seems odd that it would be detected if there were nothing at all present, although obviously it could be artifact. According to the product outline at http://www.siliconimage.com/products/product.aspx?id=64, the Silicon Image port multiplier has an EEPROM of unspecified size. With the drive appearing as precisely 320K I wouldn't be surprised if this EEPROM is what it was seeing. Even though it's currently filled with zeros I dare not write to it through fear of bricking the controller. Greg - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
At the risk of sounding like a "me too" post: I also have an Asus P5W-DH, with the following drives connected: SATA: ST3250820AS, connected to sata1 PATA: HL-DT-ST GSA-H12N, ATAPI DVD Writer, Primary master On bootup of 2.6.19 and 2.6.20, the kernel stalls for 1 minute when probing sata2, eventually giving up and continuing the boot process. There is no physical sata2 connector on the Motherboard, just solder lugs between sata1 and sata3. From other users I understand this is really a Silicon Image SIL4723 SATA to 2-Port SATA splitter. It is detected by the kernel as a disk, as below. The relevant part of the boot process looks like: ... libata version 2.00 loaded. ahci :00:1f.2: version 2.0 ACPI: PCI Interrupt :00:1f.2[B] -> GSI 23 (level, low) -> IRQ 22 PCI: Setting latency timer of device :00:1f.2 to 64 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 0xF882A900 ctl 0x0 bmdma 0x0 irq 219 ata2: SATA max UDMA/133 cmd 0xF882A980 ctl 0x0 bmdma 0x0 irq 219 ata3: SATA max UDMA/133 cmd 0xF882AA00 ctl 0x0 bmdma 0x0 irq 219 ata4: SATA max UDMA/133 cmd 0xF882AA80 ctl 0x0 bmdma 0x0 irq 219 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ...waits 20 seconds... ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ...waits 5 seconds... ata2: port is slow to respond, please be patient (Status 0x80) ...waits 30 seconds... ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ...waits 5 seconds... ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) ... A bit of poking about shows: fdisk -l /dev/sdb Disk /dev/sdb: 0 MB, 327680 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdb doesn't contain a valid partition table So it presents itself as a 320k disk, filled with zeroes as below: dd if=/dev/sdb |hexdump 000 * 005 640+0 records in 640+0 records out 327680 bytes (328 kB) copied, 0.0106662 seconds, 30.7 MB/s Note that this is not a fatal error. The machine still boots eventually, but the seemingly mandatory 60 second pause makes startup rather cumbersome for the user. So far none of the suggested fixes have managed to stop ata2 from being detected. (noprobe=ata2, irqpoll, etc). I understand this problem wasn't present in 2.6.16 so the problem must lie in some patch since then. I see Tejun is working towards patches for this and I would be happy to try them here. thanks, Greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
Hello, Paul. Paul Rolland wrote: Also, please note that libata is complaining : ATA: abnormal status 0x7F on port 0x177 and later : ATA: abnormal status 0x7F on port 0x9807 You can ignore the above. The errors on ata2 are due to SIMG storage processor and will probably fixed when PMP support is implemented. The latter errors on pata_jmicron is probably due to lack of proper mode programming on that driver. I'll look into that. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
Hello, Paul. Paul Rolland wrote: Also, please note that libata is complaining : ATA: abnormal status 0x7F on port 0x177 and later : ATA: abnormal status 0x7F on port 0x9807 You can ignore the above. The errors on ata2 are due to SIMG storage processor and will probably fixed when PMP support is implemented. The latter errors on pata_jmicron is probably due to lack of proper mode programming on that driver. I'll look into that. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
At the risk of sounding like a me too post: I also have an Asus P5W-DH, with the following drives connected: SATA: ST3250820AS, connected to sata1 PATA: HL-DT-ST GSA-H12N, ATAPI DVD Writer, Primary master On bootup of 2.6.19 and 2.6.20, the kernel stalls for 1 minute when probing sata2, eventually giving up and continuing the boot process. There is no physical sata2 connector on the Motherboard, just solder lugs between sata1 and sata3. From other users I understand this is really a Silicon Image SIL4723 SATA to 2-Port SATA splitter. It is detected by the kernel as a disk, as below. The relevant part of the boot process looks like: ... libata version 2.00 loaded. ahci :00:1f.2: version 2.0 ACPI: PCI Interrupt :00:1f.2[B] - GSI 23 (level, low) - IRQ 22 PCI: Setting latency timer of device :00:1f.2 to 64 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 0xF882A900 ctl 0x0 bmdma 0x0 irq 219 ata2: SATA max UDMA/133 cmd 0xF882A980 ctl 0x0 bmdma 0x0 irq 219 ata3: SATA max UDMA/133 cmd 0xF882AA00 ctl 0x0 bmdma 0x0 irq 219 ata4: SATA max UDMA/133 cmd 0xF882AA80 ctl 0x0 bmdma 0x0 irq 219 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ...waits 20 seconds... ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ...waits 5 seconds... ata2: port is slow to respond, please be patient (Status 0x80) ...waits 30 seconds... ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ...waits 5 seconds... ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link down (SStatus 0 SControl 300) ... A bit of poking about shows: fdisk -l /dev/sdb Disk /dev/sdb: 0 MB, 327680 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdb doesn't contain a valid partition table So it presents itself as a 320k disk, filled with zeroes as below: dd if=/dev/sdb |hexdump 000 * 005 640+0 records in 640+0 records out 327680 bytes (328 kB) copied, 0.0106662 seconds, 30.7 MB/s Note that this is not a fatal error. The machine still boots eventually, but the seemingly mandatory 60 second pause makes startup rather cumbersome for the user. So far none of the suggested fixes have managed to stop ata2 from being detected. (noprobe=ata2, irqpoll, etc). I understand this problem wasn't present in 2.6.16 so the problem must lie in some patch since then. I see Tejun is working towards patches for this and I would be happy to try them here. thanks, Greg - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
Hello Tejun, I've tested your patch yesterday, but no luck, I can't find any difference in the resulting boot log. Please find attached an archive containing : - dmesg.2.6.20-rc7 : full dmesg with stock kernel - dmesg.patch : full dmesg with your patch included. I've also added a lspci -vvv, a cat /proc/interrupts and a cat /proc/ioports in case this could help. Also, please note that libata is complaining : ATA: abnormal status 0x7F on port 0x177 and later : ATA: abnormal status 0x7F on port 0x9807 I don't know if this is important or not. Sorry for the bad news, Regards, Paul Paul Rolland, rol(at)as2917.net ex-AS2917 Network administrator and Peering Coordinator -- Please no HTML, I'm not a browser - Pas d'HTML, je ne suis pas un navigateur "Some people dream of success... while others wake up and work hard at it" "I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from now, she will come to me and say 'Daddy, where were you when they took freedom of the press away from the Internet?'" --Mike Godwin, Electronic Frontier Foundation > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Paul Rolland > Sent: Monday, February 12, 2007 12:19 PM > To: 'Tejun Heo' > Cc: 'Alan'; 'Robert Hancock'; 'Linux Kernel Mailing List' > Subject: RE: AHCI - remove probing of ata2 > > Hello Tejun, > > > You have a Maxtor connected to that port, right? That's caused by > > Waoh, you are using crystal ball ? :) You are right, this is a Maxtor > disk, 250 MB. If you want more details about this disk, I can send you > a complete details. > > > firmware bug. Future kernels will consider that condition as > > protocol > > violation and blacklist the drive such that NCQ is not used > on it. I > > think it can be dangerous on rare corner/error cases but > there hasn't > > been any actual report of problems caused by that, so no need > > to worry > > about it too much. If it bothers you, you can turn NCQ off > > using sysfs > > node. Take a look at FAQ section of http://linux-ata.org > > I'm just slightly worried about that, and because all this libata > stuff is quite "new", I prefer to report everything I can > see, considering > that I can test patches on this machine if people need me to do so. > So, consider this machine as some kind of playground if you have > some code you want someone to test. > > > Slightly OT, but it's generally a good idea to use LABELs to access > > filesystems. With so many ports and EH dynamics including > > hotplug, it's > > much more difficult to keep device names persistent and > remember them. > > Yes, that's what I should do, but I've never really like that stuff ;( > > > > So, 2.6.20-rc7 results are : > > > - ata2 probing still very long and delaying boot a lot, > > > > That's sil4726's config device acting weird. When reset as > a normal > > device (not PMP device), sil4726 acts as a normal ATA > device which is > > used to configure how the chip behaves. Unfortunately, the > emulation > > seems to contain some flaws and cause lots of delays as > you've seen. > > I'm attaching a patch to clear TF before IDENTIFY which > fixes similar > > IDENTIFY failures on buggy ATAPI devices. > > OK, will try this tonite (I'm sorry, this is my home comp., > and I'm at the > office right now - will tell you tomorrow). > > > > - Jmicron PATA still not working, and doesn't even detect > > the DVD-ROM on > > >the port. > > > > This problem is likely to be fixed by clearing TF before IDENTIFY. > > > > So, please test the attached patch and report the result. > > Will do, and will test more if you more that are to be tested ! > > BTW, maybe OT, but what about setting a list of people willing to test > patches together with their configurations so that they can be send > patches related to their hardware ? That could be useful to > people developing > drivers... > > Regards, > Paul > > - > To unsubscribe from this list: send the line "unsubscribe > linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > data.tar.bz2 Description: Binary data
RE: AHCI - remove probing of ata2
Hello Tejun, > You have a Maxtor connected to that port, right? That's caused by Waoh, you are using crystal ball ? :) You are right, this is a Maxtor disk, 250 MB. If you want more details about this disk, I can send you a complete details. > firmware bug. Future kernels will consider that condition as > protocol > violation and blacklist the drive such that NCQ is not used on it. I > think it can be dangerous on rare corner/error cases but there hasn't > been any actual report of problems caused by that, so no need > to worry > about it too much. If it bothers you, you can turn NCQ off > using sysfs > node. Take a look at FAQ section of http://linux-ata.org I'm just slightly worried about that, and because all this libata stuff is quite "new", I prefer to report everything I can see, considering that I can test patches on this machine if people need me to do so. So, consider this machine as some kind of playground if you have some code you want someone to test. > Slightly OT, but it's generally a good idea to use LABELs to access > filesystems. With so many ports and EH dynamics including > hotplug, it's > much more difficult to keep device names persistent and remember them. Yes, that's what I should do, but I've never really like that stuff ;( > > So, 2.6.20-rc7 results are : > > - ata2 probing still very long and delaying boot a lot, > > That's sil4726's config device acting weird. When reset as a normal > device (not PMP device), sil4726 acts as a normal ATA device which is > used to configure how the chip behaves. Unfortunately, the emulation > seems to contain some flaws and cause lots of delays as you've seen. > I'm attaching a patch to clear TF before IDENTIFY which fixes similar > IDENTIFY failures on buggy ATAPI devices. OK, will try this tonite (I'm sorry, this is my home comp., and I'm at the office right now - will tell you tomorrow). > > - Jmicron PATA still not working, and doesn't even detect > the DVD-ROM on > >the port. > > This problem is likely to be fixed by clearing TF before IDENTIFY. > > So, please test the attached patch and report the result. Will do, and will test more if you more that are to be tested ! BTW, maybe OT, but what about setting a list of people willing to test patches together with their configurations so that they can be send patches related to their hardware ? That could be useful to people developing drivers... Regards, Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
Hello Tejun, You have a Maxtor connected to that port, right? That's caused by Waoh, you are using crystal ball ? :) You are right, this is a Maxtor disk, 250 MB. If you want more details about this disk, I can send you a complete details. firmware bug. Future kernels will consider that condition as protocol violation and blacklist the drive such that NCQ is not used on it. I think it can be dangerous on rare corner/error cases but there hasn't been any actual report of problems caused by that, so no need to worry about it too much. If it bothers you, you can turn NCQ off using sysfs node. Take a look at FAQ section of http://linux-ata.org I'm just slightly worried about that, and because all this libata stuff is quite new, I prefer to report everything I can see, considering that I can test patches on this machine if people need me to do so. So, consider this machine as some kind of playground if you have some code you want someone to test. Slightly OT, but it's generally a good idea to use LABELs to access filesystems. With so many ports and EH dynamics including hotplug, it's much more difficult to keep device names persistent and remember them. Yes, that's what I should do, but I've never really like that stuff ;( So, 2.6.20-rc7 results are : - ata2 probing still very long and delaying boot a lot, That's sil4726's config device acting weird. When reset as a normal device (not PMP device), sil4726 acts as a normal ATA device which is used to configure how the chip behaves. Unfortunately, the emulation seems to contain some flaws and cause lots of delays as you've seen. I'm attaching a patch to clear TF before IDENTIFY which fixes similar IDENTIFY failures on buggy ATAPI devices. OK, will try this tonite (I'm sorry, this is my home comp., and I'm at the office right now - will tell you tomorrow). - Jmicron PATA still not working, and doesn't even detect the DVD-ROM on the port. This problem is likely to be fixed by clearing TF before IDENTIFY. So, please test the attached patch and report the result. Will do, and will test more if you more that are to be tested ! BTW, maybe OT, but what about setting a list of people willing to test patches together with their configurations so that they can be send patches related to their hardware ? That could be useful to people developing drivers... Regards, Paul - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
Hello Tejun, I've tested your patch yesterday, but no luck, I can't find any difference in the resulting boot log. Please find attached an archive containing : - dmesg.2.6.20-rc7 : full dmesg with stock kernel - dmesg.patch : full dmesg with your patch included. I've also added a lspci -vvv, a cat /proc/interrupts and a cat /proc/ioports in case this could help. Also, please note that libata is complaining : ATA: abnormal status 0x7F on port 0x177 and later : ATA: abnormal status 0x7F on port 0x9807 I don't know if this is important or not. Sorry for the bad news, Regards, Paul Paul Rolland, rol(at)as2917.net ex-AS2917 Network administrator and Peering Coordinator -- Please no HTML, I'm not a browser - Pas d'HTML, je ne suis pas un navigateur Some people dream of success... while others wake up and work hard at it I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from now, she will come to me and say 'Daddy, where were you when they took freedom of the press away from the Internet?' --Mike Godwin, Electronic Frontier Foundation -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Rolland Sent: Monday, February 12, 2007 12:19 PM To: 'Tejun Heo' Cc: 'Alan'; 'Robert Hancock'; 'Linux Kernel Mailing List' Subject: RE: AHCI - remove probing of ata2 Hello Tejun, You have a Maxtor connected to that port, right? That's caused by Waoh, you are using crystal ball ? :) You are right, this is a Maxtor disk, 250 MB. If you want more details about this disk, I can send you a complete details. firmware bug. Future kernels will consider that condition as protocol violation and blacklist the drive such that NCQ is not used on it. I think it can be dangerous on rare corner/error cases but there hasn't been any actual report of problems caused by that, so no need to worry about it too much. If it bothers you, you can turn NCQ off using sysfs node. Take a look at FAQ section of http://linux-ata.org I'm just slightly worried about that, and because all this libata stuff is quite new, I prefer to report everything I can see, considering that I can test patches on this machine if people need me to do so. So, consider this machine as some kind of playground if you have some code you want someone to test. Slightly OT, but it's generally a good idea to use LABELs to access filesystems. With so many ports and EH dynamics including hotplug, it's much more difficult to keep device names persistent and remember them. Yes, that's what I should do, but I've never really like that stuff ;( So, 2.6.20-rc7 results are : - ata2 probing still very long and delaying boot a lot, That's sil4726's config device acting weird. When reset as a normal device (not PMP device), sil4726 acts as a normal ATA device which is used to configure how the chip behaves. Unfortunately, the emulation seems to contain some flaws and cause lots of delays as you've seen. I'm attaching a patch to clear TF before IDENTIFY which fixes similar IDENTIFY failures on buggy ATAPI devices. OK, will try this tonite (I'm sorry, this is my home comp., and I'm at the office right now - will tell you tomorrow). - Jmicron PATA still not working, and doesn't even detect the DVD-ROM on the port. This problem is likely to be fixed by clearing TF before IDENTIFY. So, please test the attached patch and report the result. Will do, and will test more if you more that are to be tested ! BTW, maybe OT, but what about setting a list of people willing to test patches together with their configurations so that they can be send patches related to their hardware ? That could be useful to people developing drivers... Regards, Paul - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ data.tar.bz2 Description: Binary data
Re: AHCI - remove probing of ata2
Hello, Paul. Paul Rolland wrote: This looks like the problems that hopefully the patches from Tejun and from Mark Lord cured (the delay after reset and the task file clear) Any chance I can find this patch(es) and try them ? Also, I've seen a : ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f FIS=004040a1:0004 What's this ? Is it really bad or just a warning ??? It's one Tejun stuck logging in for in order to investigate further. OK, will wait a little bit ;) You have a Maxtor connected to that port, right? That's caused by firmware bug. Future kernels will consider that condition as protocol violation and blacklist the drive such that NCQ is not used on it. I think it can be dangerous on rare corner/error cases but there hasn't been any actual report of problems caused by that, so no need to worry about it too much. If it bothers you, you can turn NCQ off using sysfs node. Take a look at FAQ section of http://linux-ata.org In the meantime, I've been trying 2.6.20-rc7. Things are not better, except that the ata2 probing failing results in no /dev/sdd being allocated, thus it changes all the naming afterwards. Slightly OT, but it's generally a good idea to use LABELs to access filesystems. With so many ports and EH dynamics including hotplug, it's much more difficult to keep device names persistent and remember them. So, 2.6.20-rc7 results are : - ata2 probing still very long and delaying boot a lot, That's sil4726's config device acting weird. When reset as a normal device (not PMP device), sil4726 acts as a normal ATA device which is used to configure how the chip behaves. Unfortunately, the emulation seems to contain some flaws and cause lots of delays as you've seen. I'm attaching a patch to clear TF before IDENTIFY which fixes similar IDENTIFY failures on buggy ATAPI devices. - Jmicron PATA still not working, and doesn't even detect the DVD-ROM on the port. This problem is likely to be fixed by clearing TF before IDENTIFY. So, please test the attached patch and report the result. -- tejun diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c index 667acd2..d6fcf0a 100644 --- a/drivers/ata/libata-core.c +++ b/drivers/ata/libata-core.c @@ -1478,7 +1478,16 @@ int ata_dev_read_id(struct ata_device *dev, unsigned int *p_class, } tf.protocol = ATA_PROT_PIO; - tf.flags |= ATA_TFLAG_POLLING; /* for polling presence detection */ + + /* Some devices choke if TF registers contain garbage. Make + * sure those are properly initialized. + */ + tf.flags |= ATA_TFLAG_ISADDR | ATA_TFLAG_DEVICE; + + /* Device presence detection is unreliable on some + * controllers. Always poll IDENTIFY if available. + */ + tf.flags |= ATA_TFLAG_POLLING; err_mask = ata_exec_internal(dev, , NULL, DMA_FROM_DEVICE, id, sizeof(id[0]) * ATA_ID_WORDS);
RE: AHCI - remove probing of ata2
> > This looks like the problems that hopefully the patches > from Tejun and > > from Mark Lord cured (the delay after reset and the task file clear) > > Any chance I can find this patch(es) and try them ? > > > > Also, I've seen a : > > > > > > ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f > > > FIS=004040a1:0004 > > > > > > What's this ? Is it really bad or just a warning ??? > > > > It's one Tejun stuck logging in for in order to investigate further. > > OK, will wait a little bit ;) > In the meantime, I've been trying 2.6.20-rc7. Things are not better, except that the ata2 probing failing results in no /dev/sdd being allocated, thus it changes all the naming afterwards. So, 2.6.20-rc7 results are : - ata2 probing still very long and delaying boot a lot, - Jmicron PATA still not working, and doesn't even detect the DVD-ROM on the port. Guys, should you have any patch that you'd like me to test, feel free to send, I'll do that more than happily. Regards, Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
This looks like the problems that hopefully the patches from Tejun and from Mark Lord cured (the delay after reset and the task file clear) Any chance I can find this patch(es) and try them ? Also, I've seen a : ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f FIS=004040a1:0004 What's this ? Is it really bad or just a warning ??? It's one Tejun stuck logging in for in order to investigate further. OK, will wait a little bit ;) In the meantime, I've been trying 2.6.20-rc7. Things are not better, except that the ata2 probing failing results in no /dev/sdd being allocated, thus it changes all the naming afterwards. So, 2.6.20-rc7 results are : - ata2 probing still very long and delaying boot a lot, - Jmicron PATA still not working, and doesn't even detect the DVD-ROM on the port. Guys, should you have any patch that you'd like me to test, feel free to send, I'll do that more than happily. Regards, Paul - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
Hello, Paul. Paul Rolland wrote: This looks like the problems that hopefully the patches from Tejun and from Mark Lord cured (the delay after reset and the task file clear) Any chance I can find this patch(es) and try them ? Also, I've seen a : ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f FIS=004040a1:0004 What's this ? Is it really bad or just a warning ??? It's one Tejun stuck logging in for in order to investigate further. OK, will wait a little bit ;) You have a Maxtor connected to that port, right? That's caused by firmware bug. Future kernels will consider that condition as protocol violation and blacklist the drive such that NCQ is not used on it. I think it can be dangerous on rare corner/error cases but there hasn't been any actual report of problems caused by that, so no need to worry about it too much. If it bothers you, you can turn NCQ off using sysfs node. Take a look at FAQ section of http://linux-ata.org In the meantime, I've been trying 2.6.20-rc7. Things are not better, except that the ata2 probing failing results in no /dev/sdd being allocated, thus it changes all the naming afterwards. Slightly OT, but it's generally a good idea to use LABELs to access filesystems. With so many ports and EH dynamics including hotplug, it's much more difficult to keep device names persistent and remember them. So, 2.6.20-rc7 results are : - ata2 probing still very long and delaying boot a lot, That's sil4726's config device acting weird. When reset as a normal device (not PMP device), sil4726 acts as a normal ATA device which is used to configure how the chip behaves. Unfortunately, the emulation seems to contain some flaws and cause lots of delays as you've seen. I'm attaching a patch to clear TF before IDENTIFY which fixes similar IDENTIFY failures on buggy ATAPI devices. - Jmicron PATA still not working, and doesn't even detect the DVD-ROM on the port. This problem is likely to be fixed by clearing TF before IDENTIFY. So, please test the attached patch and report the result. -- tejun diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c index 667acd2..d6fcf0a 100644 --- a/drivers/ata/libata-core.c +++ b/drivers/ata/libata-core.c @@ -1478,7 +1478,16 @@ int ata_dev_read_id(struct ata_device *dev, unsigned int *p_class, } tf.protocol = ATA_PROT_PIO; - tf.flags |= ATA_TFLAG_POLLING; /* for polling presence detection */ + + /* Some devices choke if TF registers contain garbage. Make + * sure those are properly initialized. + */ + tf.flags |= ATA_TFLAG_ISADDR | ATA_TFLAG_DEVICE; + + /* Device presence detection is unreliable on some + * controllers. Always poll IDENTIFY if available. + */ + tf.flags |= ATA_TFLAG_POLLING; err_mask = ata_exec_internal(dev, tf, NULL, DMA_FROM_DEVICE, id, sizeof(id[0]) * ATA_ID_WORDS);
RE: AHCI - remove probing of ata2
Hello, > This looks like the problems that hopefully the patches from Tejun and > from Mark Lord cured (the delay after reset and the task file clear) Any chance I can find this patch(es) and try them ? > > Also, I've seen a : > > > > ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f > > FIS=004040a1:0004 > > > > What's this ? Is it really bad or just a warning ??? > > It's one Tejun stuck logging in for in order to investigate further. OK, will wait a little bit ;) Regards, Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
> OK, rebooting again, with a new root device as /dev/sde1... > No problem for the old IDE devices, they are now /dev/sdX. > > But the Jmicron stuff is still broken though no more conflict :( Thanks. That helps a lot as it narrows it down > > PCI: Enabling device :02:00.1 ( -> 0001) > ACPI: PCI Interrupt :02:00.1[B] -> GSI 16 (level, low) -> IRQ 16 > ata7: PATA max UDMA/100 cmd 0x9C00 ctl 0x9882 bmdma 0x9400 irq 16 > ata8: PATA max UDMA/100 cmd 0x9800 ctl 0x9482 bmdma 0x9408 irq 16 > scsi6 : pata_jmicron > ata7.00: ATAPI, max UDMA/66 > ata7.00: qc timeout (cmd 0xef) > ata7.00: failed to set xfermode (err_mask=0x4) > ata7.00: limiting speed to UDMA/44 > ata7: failed to recover some devices, retrying in 5 secs > ata7.00: qc timeout (cmd 0xef) > ata7.00: failed to set xfermode (err_mask=0x4) > ata7.00: limiting speed to PIO0 > ata7: failed to recover some devices, retrying in 5 secs > ata7.00: qc timeout (cmd 0xef) > ata7.00: failed to set xfermode (err_mask=0x4) > ata7.00: disabled > scsi7 : pata_jmicron > ATA: abnormal status 0x7F on port 0x9807 This looks like the problems that hopefully the patches from Tejun and from Mark Lord cured (the delay after reset and the task file clear) > Also, I've seen a : > > ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f > FIS=004040a1:0004 > > What's this ? Is it really bad or just a warning ??? It's one Tejun stuck logging in for in order to investigate further. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
Hi Alan, > You have the old driver 0n 0x1F0 > > > > PCI: Device :02:00.0 not available because of resource > collisions > > ahci: probe of :02:00.0 failed with error -22 > > ACPI: PCI Interrupt :00:1f.1[A] -> GSI 22 (level, low) -> IRQ 22 > > ata: 0x1F0 IDE port busy > > And the new drivers trying to manage the same port > > > CONFIG_IDE=y > > CONFIG_BLK_DEV_IDE=y > > Set those to "N" and try again Done that, rebuilt and rebooted... /dev/hda and /dev/hdb (old driver) are gone... OK, rebooting again, with a new root device as /dev/sde1... No problem for the old IDE devices, they are now /dev/sdX. But the Jmicron stuff is still broken though no more conflict :( PCI: Enabling device :02:00.1 ( -> 0001) ACPI: PCI Interrupt :02:00.1[B] -> GSI 16 (level, low) -> IRQ 16 ata7: PATA max UDMA/100 cmd 0x9C00 ctl 0x9882 bmdma 0x9400 irq 16 ata8: PATA max UDMA/100 cmd 0x9800 ctl 0x9482 bmdma 0x9408 irq 16 scsi6 : pata_jmicron ata7.00: ATAPI, max UDMA/66 ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: limiting speed to UDMA/44 ata7: failed to recover some devices, retrying in 5 secs ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: limiting speed to PIO0 ata7: failed to recover some devices, retrying in 5 secs ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: disabled scsi7 : pata_jmicron ATA: abnormal status 0x7F on port 0x9807 Also, I've seen a : ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f FIS=004040a1:0004 What's this ? Is it really bad or just a warning ??? Regards, Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
On Sat, 10 Feb 2007 19:39:21 +0100 "Paul Rolland" <[EMAIL PROTECTED]> wrote: > > I've been trying this, but I ended with the ICH7 not detecting anymore > > my IDE disks... > > Should try again, maybe I missed something. > > Done a new built, and I now have : > > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > hda: Maxtor 6L200P0, ATA DISK drive > hdb: ASUS CRW-5232A3, ATAPI CD/DVD-ROM drive You have the old driver 0n 0x1F0 > PCI: Device :02:00.0 not available because of resource collisions > ahci: probe of :02:00.0 failed with error -22 > ACPI: PCI Interrupt :00:1f.1[A] -> GSI 22 (level, low) -> IRQ 22 > ata: 0x1F0 IDE port busy And the new drivers trying to manage the same port > CONFIG_IDE=y > CONFIG_BLK_DEV_IDE=y Set those to "N" and try again - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
> I've been trying this, but I ended with the ICH7 not detecting anymore > my IDE disks... > Should try again, maybe I missed something. Done a new built, and I now have : Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hda: Maxtor 6L200P0, ATA DISK drive hdb: ASUS CRW-5232A3, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: max request size: 512KiB hda: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63 hda: cache flushes supported hda: hda1 hda2 hda3 hda4 < hda5 hda6 > hdb: ATAPI 52X CD-ROM CD-R/RW drive, 1536kB Cache Uniform CD-ROM driver Revision: 3.20 ide-floppy driver 0.99.newide 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 0xC20B6900 ctl 0x0 bmdma 0x0 irq 504 ata2: SATA max UDMA/133 cmd 0xC20B6980 ctl 0x0 bmdma 0x0 irq 504 ata3: SATA max UDMA/133 cmd 0xC20B6A00 ctl 0x0 bmdma 0x0 irq 504 ata4: SATA max UDMA/133 cmd 0xC20B6A80 ctl 0x0 bmdma 0x0 irq 504 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 0 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ata2: port is slow to respond, please be patient (Status 0x80) ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32) ata3.00: ata3: dev 0 multi count 0 ata3.00: configured for UDMA/133 scsi3 : ahci ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata4.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 31/32) ata4.00: ata4: dev 0 multi count 16 ata4.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA Maxtor 6L250S0 BANC PQ: 0 ANSI: 5 SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB) sda: Write Protect is off SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB) sda: Write Protect is off SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sd 0:0:0:0: Attached scsi disk sda sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: Direct-Access ATA Config Disk RGL1 PQ: 0 ANSI: 5 SCSI device sdb: 640 512-byte hdwr sectors (0 MB) sdb: Write Protect is off SCSI device sdb: write cache: disabled, read cache: enabled, doesn't support DPO or FUA SCSI device sdb: 640 512-byte hdwr sectors (0 MB) sdb: Write Protect is off SCSI device sdb: write cache: disabled, read cache: enabled, doesn't support DPO or FUA sdb: unknown partition table sd 1:0:0:0: Attached scsi disk sdb sd 1:0:0:0: Attached scsi generic sg1 type 0 scsi 2:0:0:0: Direct-Access ATA Maxtor 6L250S0 BANC PQ: 0 ANSI: 5 SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB) sdc: Write Protect is off SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB) sdc: Write Protect is off SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: sdc1 sdc2 sd 2:0:0:0: Attached scsi disk sdc sd 2:0:0:0: Attached scsi generic sg2 type 0 scsi 3:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5 SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB) sdd: Write Protect is off SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB) sdd: Write Protect is off SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdd: sdd1 sdd2 sdd3 sd 3:0:0:0: Attached scsi disk sdd sd 3:0:0:0: Attached scsi generic sg3 type 0 PCI: Device :02:00.0 not available because of resource collisions ahci: probe of :02:00.0 failed with error -22 ACPI: PCI Interrupt :00:1f.1[A] -> GSI 22 (level, low) -> IRQ 22 ata: 0x1F0 IDE port busy ata: conflict with ide0 ata5: DUMMY ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15 scsi4 : ata_piix scsi5 : ata_piix ATA: abnormal status 0x7F on port 0x177 PCI: Enabling device :02:00.1 ( -> 0001) ACPI: PCI Interrupt :02:00.1[B] -> GSI 16 (level, low) -> IRQ 16 ata7: PATA max UDMA/100 cmd 0x9C00 ctl
RE: AHCI - remove probing of ata2
Hello, > There is something connected, I believe what's actually there on this > board on that port is the SiI4723 chip which is connected to > two other > SATA ports. For whatever reason it gets detected as a drive, > and it also > seems to be not responding until we do a few resets.. That's correct, there is this controller, used by Asus for their EZ-Backup feature. But I'm not using it, there is no disk connected on the associated ports, and it's disabled in the BIOS. > My advice on recent kernels is just set CONFIG_IDE=n and enable > PATA_JMICRON if you want JMicron support, unless you really > want to use the crusty old IDE layer.. No real preferences... except for a working machine, which is not what I have for now... I've been trying this, but I ended with the ICH7 not detecting anymore my IDE disks... Should try again, maybe I missed something. Regards, Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2 + Jmicron JMB363 ATA mode failing
Some more messages, using 2.6.20 :
- ICH7 from ATA/ATAPI/MFM/RLL support,
- Jmicron from ATA/ATAPI/MFM/RLL support,
- SATA AHCI from Serial ATA (prod)
Boot goes to :
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH7: IDE controller at PCI slot :00:1f.1
ACPI: PCI Interrupt :00:1f.1[A] -> GSI 22 (level, low) -> IRQ 22
ICH7: chipset revision 1
ICH7: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: Maxtor 6L200P0, ATA DISK drive
hdb: ASUS CRW-5232A3, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
JMB363: IDE controller at PCI slot :02:00.0
PCI: Device :02:00.0 not available because of resource collisions
ACPI: PCI Interrupt :02:00.0[A] -> GSI 17 (level, low) -> IRQ 17
JMB363: BIOS configuration fixed.
JMB363: chipset revision 2
JMB363: 100% native mode on irq 17
JMB363: port 0x01f0 already claimed by ide0
JMB363: port 0x0170 already claimed by ide1
JMB363: neither IDE port enabled (BIOS)
JMB363: IDE controller at PCI slot :02:00.1
PCI: Enabling device :02:00.1 ( -> 0001)
ACPI: PCI Interrupt :02:00.1[B] -> GSI 16 (level, low) -> IRQ 16
JMB363: chipset revision 2
JMB363: 100% native mode on irq 16
ide2: BM-DMA at 0x9400-0x9407, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x9408-0x940f, BIOS settings: hdg:pio, hdh:pio
hde: ASUS DRW-1608P, ATAPI CD/DVD-ROM drive
ide2 at 0x9c00-0x9c07,0x9882 on irq 16
hda: max request size: 512KiB
hda: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
hdb: ATAPI 52X CD-ROM CD-R/RW drive, 1536kB Cache
Uniform CD-ROM driver Revision: 3.20
ide-cd: cmd 0x5a timed out
hde: lost interrupt
ide-cd: cmd 0x5a timed out
hde: lost interrupt
hde: packet command error: status=0x51 { DriveReady SeekComplete Error }
hde: packet command error: error=0x40 { LastFailedSense=0x04 }
ide: failed opcode was: unknown
ide-cd: cmd 0x3 timed out
hde: lost interrupt
hde: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hde: request sense failure: error=0x40 { LastFailedSense=0x04 }
and then the machine is locked, no keyboard, but the DVD-ROM is correctly
detected, as the message :
hde: ASUS DRW-1608P, ATAPI CD/DVD-ROM drive
indicates.
If I remove Jmicron support from the kernel, I have ICH7 in ATA/ATAPI/...
and AHCI in Serial ATA, and the boot process is nearly fine, except the
ata2 timeout, that I can't prevent even with ata2=noprobe in the command line
:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH7: IDE controller at PCI slot :00:1f.1
ACPI: PCI Interrupt :00:1f.1[A] -> GSI 22 (level, low) -> IRQ 22
ICH7: chipset revision 1
ICH7: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: Maxtor 6L200P0, ATA DISK drive
hdb: ASUS CRW-5232A3, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 512KiB
hda: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
hdb: ATAPI 52X CD-ROM CD-R/RW drive, 1536kB Cache
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
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 0xC2054900 ctl 0x0 bmdma 0x0 irq 1272
ata2: SATA max UDMA/133 cmd 0xC2054980 ctl 0x0 bmdma 0x0 irq 1272
ata3: SATA max UDMA/133 cmd 0xC2054A00 ctl 0x0 bmdma 0x0 irq 1272
ata4: SATA max UDMA/133 cmd 0xC2054A80 ctl 0x0 bmdma 0x0 irq 1272
scsi0 : ahci
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32)
ata1.00: ata1: dev 0 multi count 0
ata1.00: configured for UDMA/133
scsi1 : ahci
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
ata2: port is slow to respond, please be patient (Status 0x80)
ata2: port failed to respond (30 secs, Status 0x80)
ata2: COMRESET failed (device not ready)
ata2: hardreset failed, retrying in 5 secs
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA
ata2.00: ata2: dev 0 multi count 1
ata2.00: configured for UDMA/133
scsi2 : ahci
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32)
ata3.00: ata3: dev 0 multi count 0
ata3.00: configured for UDMA/133
The specification summary of the board says :
Intel ICH7R Southbridge supports
- 1 x Ultra DMA 100/66/33
- 3 x Serial
Re: AHCI - remove probing of ata2
Paul Rolland wrote: Hello, I'm using an Asus P5W DH motherboard, with an Intel ICH7 controler, and a Jmicron JMB363. On the Intel, I've connected an IDE HDD and a CD-RW, no problem. On the SATA side, i've connected 3 SATA disks, but at boot time, the kernel detects 4 ports, and goes on timeout on ata2 : .. 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 0xC20BC900 ctl 0x0 bmdma 0x0 irq 505 ata2: SATA max UDMA/133 cmd 0xC20BC980 ctl 0x0 bmdma 0x0 irq 505 ata3: SATA max UDMA/133 cmd 0xC20BCA00 ctl 0x0 bmdma 0x0 irq 505 ata4: SATA max UDMA/133 cmd 0xC20BCA80 ctl 0x0 bmdma 0x0 irq 505 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 0 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ata2: port is slow to respond, please be patient (Status 0x80) ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32) ata3.00: ata3: dev 0 multi count 0 ata3.00: configured for UDMA/133 .. Is there a way to exclude ata2 from probing ? Nothing is connected, and there is no associated port on the motherboard... There is something connected, I believe what's actually there on this board on that port is the SiI4723 chip which is connected to two other SATA ports. For whatever reason it gets detected as a drive, and it also seems to be not responding until we do a few resets.. http://www.siliconimage.com/products/product.aspx?id=64 The second problem is the Jmicron controler. It can act as IDE, SATA, ... but I've configured it as IDE in the BIOS, and connected a DRD-RW on. Problem is that IDE driver detects it, as containing ide2 and ide3, and when probing for the DVD, I've got a lot of timeout on the command. .. But, I'm lost in all the JMICRON configuration possibilities in the kernel : - it is detected by the IDE driver, - it can be activated in ATA/ATAPI/MFM/RLL - it can be activated in Serial ATA (prod) and Parallel ATA (experimental) What should I select ? My advice on recent kernels is just set CONFIG_IDE=n and enable PATA_JMICRON if you want JMicron support, unless you really want to use the crusty old IDE layer.. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
Hello, This looks like the problems that hopefully the patches from Tejun and from Mark Lord cured (the delay after reset and the task file clear) Any chance I can find this patch(es) and try them ? Also, I've seen a : ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f FIS=004040a1:0004 What's this ? Is it really bad or just a warning ??? It's one Tejun stuck logging in for in order to investigate further. OK, will wait a little bit ;) Regards, Paul - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
Paul Rolland wrote: Hello, I'm using an Asus P5W DH motherboard, with an Intel ICH7 controler, and a Jmicron JMB363. On the Intel, I've connected an IDE HDD and a CD-RW, no problem. On the SATA side, i've connected 3 SATA disks, but at boot time, the kernel detects 4 ports, and goes on timeout on ata2 : .. 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 0xC20BC900 ctl 0x0 bmdma 0x0 irq 505 ata2: SATA max UDMA/133 cmd 0xC20BC980 ctl 0x0 bmdma 0x0 irq 505 ata3: SATA max UDMA/133 cmd 0xC20BCA00 ctl 0x0 bmdma 0x0 irq 505 ata4: SATA max UDMA/133 cmd 0xC20BCA80 ctl 0x0 bmdma 0x0 irq 505 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 0 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ata2: port is slow to respond, please be patient (Status 0x80) ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32) ata3.00: ata3: dev 0 multi count 0 ata3.00: configured for UDMA/133 .. Is there a way to exclude ata2 from probing ? Nothing is connected, and there is no associated port on the motherboard... There is something connected, I believe what's actually there on this board on that port is the SiI4723 chip which is connected to two other SATA ports. For whatever reason it gets detected as a drive, and it also seems to be not responding until we do a few resets.. http://www.siliconimage.com/products/product.aspx?id=64 The second problem is the Jmicron controler. It can act as IDE, SATA, ... but I've configured it as IDE in the BIOS, and connected a DRD-RW on. Problem is that IDE driver detects it, as containing ide2 and ide3, and when probing for the DVD, I've got a lot of timeout on the command. .. But, I'm lost in all the JMICRON configuration possibilities in the kernel : - it is detected by the IDE driver, - it can be activated in ATA/ATAPI/MFM/RLL - it can be activated in Serial ATA (prod) and Parallel ATA (experimental) What should I select ? My advice on recent kernels is just set CONFIG_IDE=n and enable PATA_JMICRON if you want JMicron support, unless you really want to use the crusty old IDE layer.. -- Robert Hancock Saskatoon, SK, Canada To email, remove nospam from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2 + Jmicron JMB363 ATA mode failing
Some more messages, using 2.6.20 :
- ICH7 from ATA/ATAPI/MFM/RLL support,
- Jmicron from ATA/ATAPI/MFM/RLL support,
- SATA AHCI from Serial ATA (prod)
Boot goes to :
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH7: IDE controller at PCI slot :00:1f.1
ACPI: PCI Interrupt :00:1f.1[A] - GSI 22 (level, low) - IRQ 22
ICH7: chipset revision 1
ICH7: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: Maxtor 6L200P0, ATA DISK drive
hdb: ASUS CRW-5232A3, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
JMB363: IDE controller at PCI slot :02:00.0
PCI: Device :02:00.0 not available because of resource collisions
ACPI: PCI Interrupt :02:00.0[A] - GSI 17 (level, low) - IRQ 17
JMB363: BIOS configuration fixed.
JMB363: chipset revision 2
JMB363: 100% native mode on irq 17
JMB363: port 0x01f0 already claimed by ide0
JMB363: port 0x0170 already claimed by ide1
JMB363: neither IDE port enabled (BIOS)
JMB363: IDE controller at PCI slot :02:00.1
PCI: Enabling device :02:00.1 ( - 0001)
ACPI: PCI Interrupt :02:00.1[B] - GSI 16 (level, low) - IRQ 16
JMB363: chipset revision 2
JMB363: 100% native mode on irq 16
ide2: BM-DMA at 0x9400-0x9407, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x9408-0x940f, BIOS settings: hdg:pio, hdh:pio
hde: ASUS DRW-1608P, ATAPI CD/DVD-ROM drive
ide2 at 0x9c00-0x9c07,0x9882 on irq 16
hda: max request size: 512KiB
hda: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4 hda5 hda6
hdb: ATAPI 52X CD-ROM CD-R/RW drive, 1536kB Cache
Uniform CD-ROM driver Revision: 3.20
ide-cd: cmd 0x5a timed out
hde: lost interrupt
ide-cd: cmd 0x5a timed out
hde: lost interrupt
hde: packet command error: status=0x51 { DriveReady SeekComplete Error }
hde: packet command error: error=0x40 { LastFailedSense=0x04 }
ide: failed opcode was: unknown
ide-cd: cmd 0x3 timed out
hde: lost interrupt
hde: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hde: request sense failure: error=0x40 { LastFailedSense=0x04 }
and then the machine is locked, no keyboard, but the DVD-ROM is correctly
detected, as the message :
hde: ASUS DRW-1608P, ATAPI CD/DVD-ROM drive
indicates.
If I remove Jmicron support from the kernel, I have ICH7 in ATA/ATAPI/...
and AHCI in Serial ATA, and the boot process is nearly fine, except the
ata2 timeout, that I can't prevent even with ata2=noprobe in the command line
:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH7: IDE controller at PCI slot :00:1f.1
ACPI: PCI Interrupt :00:1f.1[A] - GSI 22 (level, low) - IRQ 22
ICH7: chipset revision 1
ICH7: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: Maxtor 6L200P0, ATA DISK drive
hdb: ASUS CRW-5232A3, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 512KiB
hda: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4 hda5 hda6
hdb: ATAPI 52X CD-ROM CD-R/RW drive, 1536kB Cache
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
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 0xC2054900 ctl 0x0 bmdma 0x0 irq 1272
ata2: SATA max UDMA/133 cmd 0xC2054980 ctl 0x0 bmdma 0x0 irq 1272
ata3: SATA max UDMA/133 cmd 0xC2054A00 ctl 0x0 bmdma 0x0 irq 1272
ata4: SATA max UDMA/133 cmd 0xC2054A80 ctl 0x0 bmdma 0x0 irq 1272
scsi0 : ahci
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32)
ata1.00: ata1: dev 0 multi count 0
ata1.00: configured for UDMA/133
scsi1 : ahci
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
ata2: port is slow to respond, please be patient (Status 0x80)
ata2: port failed to respond (30 secs, Status 0x80)
ata2: COMRESET failed (device not ready)
ata2: hardreset failed, retrying in 5 secs
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA
ata2.00: ata2: dev 0 multi count 1
ata2.00: configured for UDMA/133
scsi2 : ahci
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32)
ata3.00: ata3: dev 0 multi count 0
ata3.00: configured for UDMA/133
The specification summary of the board says :
Intel ICH7R Southbridge supports
- 1 x Ultra DMA 100/66/33
- 3 x Serial ATA 3.0 Gb/s
RE: AHCI - remove probing of ata2
Hello, There is something connected, I believe what's actually there on this board on that port is the SiI4723 chip which is connected to two other SATA ports. For whatever reason it gets detected as a drive, and it also seems to be not responding until we do a few resets.. That's correct, there is this controller, used by Asus for their EZ-Backup feature. But I'm not using it, there is no disk connected on the associated ports, and it's disabled in the BIOS. My advice on recent kernels is just set CONFIG_IDE=n and enable PATA_JMICRON if you want JMicron support, unless you really want to use the crusty old IDE layer.. No real preferences... except for a working machine, which is not what I have for now... I've been trying this, but I ended with the ICH7 not detecting anymore my IDE disks... Should try again, maybe I missed something. Regards, Paul - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
I've been trying this, but I ended with the ICH7 not detecting anymore my IDE disks... Should try again, maybe I missed something. Done a new built, and I now have : Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hda: Maxtor 6L200P0, ATA DISK drive hdb: ASUS CRW-5232A3, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: max request size: 512KiB hda: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63 hda: cache flushes supported hda: hda1 hda2 hda3 hda4 hda5 hda6 hdb: ATAPI 52X CD-ROM CD-R/RW drive, 1536kB Cache Uniform CD-ROM driver Revision: 3.20 ide-floppy driver 0.99.newide 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 0xC20B6900 ctl 0x0 bmdma 0x0 irq 504 ata2: SATA max UDMA/133 cmd 0xC20B6980 ctl 0x0 bmdma 0x0 irq 504 ata3: SATA max UDMA/133 cmd 0xC20B6A00 ctl 0x0 bmdma 0x0 irq 504 ata4: SATA max UDMA/133 cmd 0xC20B6A80 ctl 0x0 bmdma 0x0 irq 504 scsi0 : ahci ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32) ata1.00: ata1: dev 0 multi count 0 ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) ata2: port is slow to respond, please be patient (Status 0x80) ata2: port failed to respond (30 secs, Status 0x80) ata2: COMRESET failed (device not ready) ata2: hardreset failed, retrying in 5 secs ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 31/32) ata3.00: ata3: dev 0 multi count 0 ata3.00: configured for UDMA/133 scsi3 : ahci ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata4.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 31/32) ata4.00: ata4: dev 0 multi count 16 ata4.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA Maxtor 6L250S0 BANC PQ: 0 ANSI: 5 SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB) sda: Write Protect is off SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB) sda: Write Protect is off SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sd 0:0:0:0: Attached scsi disk sda sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: Direct-Access ATA Config Disk RGL1 PQ: 0 ANSI: 5 SCSI device sdb: 640 512-byte hdwr sectors (0 MB) sdb: Write Protect is off SCSI device sdb: write cache: disabled, read cache: enabled, doesn't support DPO or FUA SCSI device sdb: 640 512-byte hdwr sectors (0 MB) sdb: Write Protect is off SCSI device sdb: write cache: disabled, read cache: enabled, doesn't support DPO or FUA sdb: unknown partition table sd 1:0:0:0: Attached scsi disk sdb sd 1:0:0:0: Attached scsi generic sg1 type 0 scsi 2:0:0:0: Direct-Access ATA Maxtor 6L250S0 BANC PQ: 0 ANSI: 5 SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB) sdc: Write Protect is off SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB) sdc: Write Protect is off SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: sdc1 sdc2 sd 2:0:0:0: Attached scsi disk sdc sd 2:0:0:0: Attached scsi generic sg2 type 0 scsi 3:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5 SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB) sdd: Write Protect is off SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB) sdd: Write Protect is off SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdd: sdd1 sdd2 sdd3 sd 3:0:0:0: Attached scsi disk sdd sd 3:0:0:0: Attached scsi generic sg3 type 0 PCI: Device :02:00.0 not available because of resource collisions ahci: probe of :02:00.0 failed with error -22 ACPI: PCI Interrupt :00:1f.1[A] - GSI 22 (level, low) - IRQ 22 ata: 0x1F0 IDE port busy ata: conflict with ide0 ata5: DUMMY ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15 scsi4 : ata_piix scsi5 : ata_piix ATA: abnormal status 0x7F on port 0x177 PCI: Enabling device :02:00.1 ( - 0001) ACPI: PCI Interrupt :02:00.1[B] - GSI 16 (level, low) - IRQ 16 ata7: PATA max UDMA/100 cmd 0x9C00 ctl 0x9882 bmdma
Re: AHCI - remove probing of ata2
On Sat, 10 Feb 2007 19:39:21 +0100 Paul Rolland [EMAIL PROTECTED] wrote: I've been trying this, but I ended with the ICH7 not detecting anymore my IDE disks... Should try again, maybe I missed something. Done a new built, and I now have : Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hda: Maxtor 6L200P0, ATA DISK drive hdb: ASUS CRW-5232A3, ATAPI CD/DVD-ROM drive You have the old driver 0n 0x1F0 PCI: Device :02:00.0 not available because of resource collisions ahci: probe of :02:00.0 failed with error -22 ACPI: PCI Interrupt :00:1f.1[A] - GSI 22 (level, low) - IRQ 22 ata: 0x1F0 IDE port busy And the new drivers trying to manage the same port CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y Set those to N and try again - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: AHCI - remove probing of ata2
Hi Alan, You have the old driver 0n 0x1F0 PCI: Device :02:00.0 not available because of resource collisions ahci: probe of :02:00.0 failed with error -22 ACPI: PCI Interrupt :00:1f.1[A] - GSI 22 (level, low) - IRQ 22 ata: 0x1F0 IDE port busy And the new drivers trying to manage the same port CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y Set those to N and try again Done that, rebuilt and rebooted... /dev/hda and /dev/hdb (old driver) are gone... OK, rebooting again, with a new root device as /dev/sde1... No problem for the old IDE devices, they are now /dev/sdX. But the Jmicron stuff is still broken though no more conflict :( PCI: Enabling device :02:00.1 ( - 0001) ACPI: PCI Interrupt :02:00.1[B] - GSI 16 (level, low) - IRQ 16 ata7: PATA max UDMA/100 cmd 0x9C00 ctl 0x9882 bmdma 0x9400 irq 16 ata8: PATA max UDMA/100 cmd 0x9800 ctl 0x9482 bmdma 0x9408 irq 16 scsi6 : pata_jmicron ata7.00: ATAPI, max UDMA/66 ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: limiting speed to UDMA/44 ata7: failed to recover some devices, retrying in 5 secs ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: limiting speed to PIO0 ata7: failed to recover some devices, retrying in 5 secs ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: disabled scsi7 : pata_jmicron ATA: abnormal status 0x7F on port 0x9807 Also, I've seen a : ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f FIS=004040a1:0004 What's this ? Is it really bad or just a warning ??? Regards, Paul - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHCI - remove probing of ata2
OK, rebooting again, with a new root device as /dev/sde1... No problem for the old IDE devices, they are now /dev/sdX. But the Jmicron stuff is still broken though no more conflict :( Thanks. That helps a lot as it narrows it down PCI: Enabling device :02:00.1 ( - 0001) ACPI: PCI Interrupt :02:00.1[B] - GSI 16 (level, low) - IRQ 16 ata7: PATA max UDMA/100 cmd 0x9C00 ctl 0x9882 bmdma 0x9400 irq 16 ata8: PATA max UDMA/100 cmd 0x9800 ctl 0x9482 bmdma 0x9408 irq 16 scsi6 : pata_jmicron ata7.00: ATAPI, max UDMA/66 ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: limiting speed to UDMA/44 ata7: failed to recover some devices, retrying in 5 secs ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: limiting speed to PIO0 ata7: failed to recover some devices, retrying in 5 secs ata7.00: qc timeout (cmd 0xef) ata7.00: failed to set xfermode (err_mask=0x4) ata7.00: disabled scsi7 : pata_jmicron ATA: abnormal status 0x7F on port 0x9807 This looks like the problems that hopefully the patches from Tejun and from Mark Lord cured (the delay after reset and the task file clear) Also, I've seen a : ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f FIS=004040a1:0004 What's this ? Is it really bad or just a warning ??? It's one Tejun stuck logging in for in order to investigate further. Alan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
