From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Genoud Subject: Re: [bug ?] device reported invalid CHS sector 0 / NCQ disabled due to excessive errors Date: Sun, 25 Apr 2010 19:49:07 +0200 Message-ID: References: <4BD4721D.2090202@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-pv0-f174.google.com ([74.125.83.174]:56276 "EHLO mail-pv0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753165Ab0DYRtW convert rfc822-to-8bit (ORCPT ); Sun, 25 Apr 2010 13:49:22 -0400 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Robert Hancock Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org 2010/4/25 Robert Hancock : > On Sun, Apr 25, 2010 at 10:57 AM, Richard Genoud > wrote: >> 2010/4/25 Robert Hancock : >>> Usually this sort of thing is some kind of hardware problem - eithe= r a >>> firmware bug in the drive, or else a SATA link communication proble= m like a >>> bad cable, or the drives not getting clean power under load. >> I'll try other sata cables, but I'm afraid, like you said, that it's= a >> firmware bug... >> >>> The log is missing the detail messages indicating what actually hap= pened - >>> can you post the output from dmesg instead? >> you're right, there's more informations in there : >> >> [ =C2=A0 =C2=A02.701742] ahci 0000:00:1f.2: version 3.0 >> [ =C2=A0 =C2=A02.701751] =C2=A0 alloc irq_desc for 21 on node 0 >> [ =C2=A0 =C2=A02.701752] =C2=A0 alloc kstat_irqs on node 0 >> [ =C2=A0 =C2=A02.701756] ahci 0000:00:1f.2: PCI INT D -> GSI 21 (lev= el, low) -> IRQ 21 >> [ =C2=A0 =C2=A02.701826] =C2=A0 alloc irq_desc for 35 on node 0 >> [ =C2=A0 =C2=A02.701827] =C2=A0 alloc kstat_irqs on node 0 >> [ =C2=A0 =C2=A02.701833] ahci 0000:00:1f.2: irq 35 for MSI/MSI-X >> [ =C2=A0 =C2=A02.701855] ahci: SSS flag set, parallel bus scan disab= led >> [ =C2=A0 =C2=A02.719878] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots = 6 ports 3 >> Gbps 0x3f impl SATA mode >> [ =C2=A0 =C2=A02.719947] ahci 0000:00:1f.2: flags: 64bit ncq sntf st= ag pm led >> clo pmp pio slum part ems >> [ =C2=A0 =C2=A02.720011] ahci 0000:00:1f.2: setting latency timer to= 64 >> [ =C2=A0 =C2=A02.819723] scsi0 : ahci >> [ =C2=A0 =C2=A02.819817] scsi1 : ahci >> [ =C2=A0 =C2=A02.819888] scsi2 : ahci >> [ =C2=A0 =C2=A02.819960] scsi3 : ahci >> [ =C2=A0 =C2=A02.820034] scsi4 : ahci >> [ =C2=A0 =C2=A02.820104] scsi5 : ahci >> [ =C2=A0 =C2=A02.820226] ata1: SATA max UDMA/133 abar m2048@0xfbaf70= 00 port >> 0xfbaf7100 irq 35 >> [ =C2=A0 =C2=A02.820288] ata2: SATA max UDMA/133 abar m2048@0xfbaf70= 00 port >> 0xfbaf7180 irq 35 >> [ =C2=A0 =C2=A02.820349] ata3: SATA max UDMA/133 abar m2048@0xfbaf70= 00 port >> 0xfbaf7200 irq 35 >> [ =C2=A0 =C2=A02.820411] ata4: SATA max UDMA/133 abar m2048@0xfbaf70= 00 port >> 0xfbaf7280 irq 35 >> [ =C2=A0 =C2=A02.820472] ata5: SATA max UDMA/133 abar m2048@0xfbaf70= 00 port >> 0xfbaf7300 irq 35 >> [ =C2=A0 =C2=A02.820534] ata6: SATA max UDMA/133 abar m2048@0xfbaf70= 00 port >> 0xfbaf7380 irq 35 >> [ =C2=A0 =C2=A02.820630] ahci 0000:03:00.0: PCI INT A -> GSI 18 (lev= el, low) -> IRQ 18 >> [ =C2=A0 =C2=A02.839665] ahci 0000:03:00.0: AHCI 0001.0000 32 slots = 2 ports 3 >> Gbps 0x3 impl SATA mode >> [ =C2=A0 =C2=A02.839736] ahci 0000:03:00.0: flags: 64bit ncq led clo= pmp pio >> [ =C2=A0 =C2=A02.839787] ahci 0000:03:00.0: setting latency timer to= 64 >> [ =C2=A0 =C2=A02.839869] scsi6 : ahci >> [ =C2=A0 =C2=A02.839939] scsi7 : ahci >> [ =C2=A0 =C2=A02.840024] ata7: SATA max UDMA/133 abar m8192@0xfbdfa0= 00 port >> 0xfbdfa100 irq 18 >> [ =C2=A0 =C2=A02.840086] ata8: SATA max UDMA/133 abar m8192@0xfbdfa0= 00 port >> 0xfbdfa180 irq 18 >> [ =C2=A0 =C2=A03.348939] ata1: SATA link up 3.0 Gbps (SStatus 123 SC= ontrol 300) >> [ =C2=A0 =C2=A03.366808] ata1.00: ATA-7: HDS728080PLA380, PF2OA60A, = max UDMA/133 >> [ =C2=A0 =C2=A03.366869] ata1.00: 160836480 sectors, multi 0: LBA48 = NCQ (depth 31/32) >> [ =C2=A0 =C2=A03.368030] ata1.00: configured for UDMA/133 >> [ =C2=A0 =C2=A04.317329] ata2: SATA link up 3.0 Gbps (SStatus 123 SC= ontrol 300) >> [ =C2=A0 =C2=A04.338405] ata2.00: ATA-7: HDS728080PLA380, PF2OA60A, = max UDMA/133 >> [ =C2=A0 =C2=A04.338466] ata2.00: 160836480 sectors, multi 0: LBA48 = NCQ (depth 31/32) >> [ =C2=A0 =C2=A04.339643] ata2.00: configured for UDMA/133 >> [ =C2=A0 =C2=A05.285674] ata3: SATA link up 3.0 Gbps (SStatus 123 SC= ontrol 300) >> [ =C2=A0 =C2=A05.305917] ata3.00: ATA-8: Hitachi HDP725050GLA360, GM= 4OA5CA, max UDMA/133 >> [ =C2=A0 =C2=A05.305979] ata3.00: 976773168 sectors, multi 0: LBA48 = NCQ (depth 31/32) >> [ =C2=A0 =C2=A05.307132] ata3.00: configured for UDMA/133 >> [ =C2=A0 =C2=A05.675046] ata4: SATA link down (SStatus 0 SControl 30= 0) >> [ =C2=A0 =C2=A06.044399] ata5: SATA link down (SStatus 0 SControl 30= 0) >> [ =C2=A0 =C2=A06.413775] ata6: SATA link down (SStatus 0 SControl 30= 0) > .. > >> [16840.450530] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action= 0x6 frozen >> [16840.450535] ata1.00: cmd 61/b8:00:20:d5:8b/02:00:05:00:00/40 tag = 0 >> ncq 356352 out >> [16840.450536] =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0res 40/00:00:00:4f:= c2/00:01:00:00:00/00 Emask >> 0x4 (timeout) >> [16840.450538] ata1.00: status: { DRDY } >> [16840.450541] ata1.00: cmd 61/80:08:99:bd:86/01:00:09:00:00/40 tag = 1 >> ncq 196608 out >> [16840.450542] =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0res 40/00:00:00:00:= 00/00:00:00:00:00/00 Emask >> 0x4 (timeout) >> [16840.450543] ata1.00: status: { DRDY } >> [16840.450546] ata1: hard resetting link >> [16840.978820] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300= ) >> [16840.981055] ata1.00: configured for UDMA/133 >> [16840.981064] ata1.00: device reported invalid CHS sector 0 >> [16840.981069] ata1.00: device reported invalid CHS sector 0 >> [16840.981078] ata1: EH complete > > Looks like it's only happening on one of the drives, I'd suspect > there's some kind of drive fault or power problem specific to that > one.. > Actually, it's always happening only on one drive, but it's not always the same: on one boot it's ata1 and in the next boot, it can be ata2.