Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1191179 > unrolled thread
| Started by | Alex Deucher <alexdeucher@gmail.com> |
|---|---|
| First post | 2015-07-23 19:50 +0200 |
| Last post | 2015-07-27 05:10 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.kernel
ATA failure regression in kernel 4.2 Alex Deucher <alexdeucher@gmail.com> - 2015-07-23 19:50 +0200
Re: ATA failure regression in kernel 4.2 Tejun Heo <tj@kernel.org> - 2015-07-23 20:40 +0200
Re: ATA failure regression in kernel 4.2 Alex Deucher <alexdeucher@gmail.com> - 2015-07-23 20:50 +0200
Re: ATA failure regression in kernel 4.2 Jiang Liu <jiang.liu@linux.intel.com> - 2015-07-27 05:10 +0200
| From | Alex Deucher <alexdeucher@gmail.com> |
|---|---|
| Date | 2015-07-23 19:50 +0200 |
| Subject | ATA failure regression in kernel 4.2 |
| Message-ID | <pPsN4-5io-5@gated-at.bofh.it> |
Something new in kernel 4.2 seems to have broken one of my hard drives (ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the relevant logs. Kernel 4.1: [ 1.435809] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.435837] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.444814] input: Logitech Inc. iFeel Mouse as /devices/pci0000:00/0000:00:10.0/usb1/1-1/1-1:1.0/0003:046D:C030.0001/input/input3 [ 1.445156] hid-generic 0003:046D:C030.0001: input,hidraw0: USB HID v1.00 Mouse [Logitech Inc. iFeel Mouse ] on usb-0000:00:10.0-1/input0 [ 1.447770] ata2.00: ATA-8: KINGSTON SV300S37A120G, 506ABBF0, max UDMA/133 [ 1.447773] ata2.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.457610] ata2.00: configured for UDMA/133 [ 1.472799] ata1.00: HPA detected: current 156299375, native 156301488 [ 1.472805] ata1.00: ATA-7: ST380815AS, 4.AAB, max UDMA/133 [ 1.472807] ata1.00: 156299375 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 1.531057] ata1.00: configured for UDMA/133 [ 1.531223] scsi 0:0:0:0: Direct-Access ATA ST380815AS B PQ: 0 ANSI: 5 [ 1.531438] sd 0:0:0:0: [sda] 156299375 512-byte logical blocks: (80.0 GB/74.5 GiB) [ 1.531476] sd 0:0:0:0: [sda] Write Protect is off [ 1.531478] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.531484] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 1.531491] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.531686] scsi 1:0:0:0: Direct-Access ATA KINGSTON SV300S3 BBF0 PQ: 0 ANSI: 5 [ 1.531847] sd 1:0:0:0: [sdb] 234441648 512-byte logical blocks: (120 GB/111 GiB) [ 1.531879] sd 1:0:0:0: [sdb] Write Protect is off [ 1.531881] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 1.531891] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.531904] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 1.534210] sdb: sdb1 [ 1.534466] sd 1:0:0:0: [sdb] Attached SCSI disk [ 1.579337] sda: sda1 [ 1.579628] sd 0:0:0:0: [sda] Attached SCSI disk Kernel 4.2: [ 1.552246] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.552308] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.568731] input: Logitech Inc. iFeel Mouse as /devices/pci0000:00/0000:00:10.0/usb1/1-1/1-1:1.0/0003:046D:C030.0001/input/input3 [ 1.569086] hid-generic 0003:046D:C030.0001: input,hidraw0: USB HID v1.00 Mouse [Logitech Inc. iFeel Mouse ] on usb-0000:00:10.0-1/input0 [ 1.597811] ata1.00: HPA detected: current 156299375, native 156301488 [ 1.597900] ata1.00: ATA-7: ST380815AS, 4.AAB, max UDMA/133 [ 1.597983] ata1.00: 156299375 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 1.656075] ata1.00: configured for UDMA/133 [ 1.656417] scsi 0:0:0:0: Direct-Access ATA ST380815AS B PQ: 0 ANSI: 5 [ 1.656744] sd 0:0:0:0: [sda] 156299375 512-byte logical blocks: (80.0 GB/74.5 GiB) [ 1.656801] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 1.657071] sd 0:0:0:0: [sda] Write Protect is off [ 1.657166] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.657201] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.704347] sda: sda1 [ 1.704779] sd 0:0:0:0: [sda] Attached SCSI disk [ 2.059840] tsc: Refined TSC clocksource calibration: 3693.283 MHz [ 2.059936] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x6a7918f751d, max_idle_ns: 881590915016 ns [ 3.059155] clocksource: Switched to clocksource tsc [ 6.547628] ata2.00: qc timeout (cmd 0xec) [ 6.547721] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.007213] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 16.997819] ata2.00: qc timeout (cmd 0xec) [ 16.997910] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.997995] ata2: limiting SATA link speed to 3.0 Gbps [ 17.457400] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 47.429257] ata2.00: qc timeout (cmd 0xec) [ 47.429349] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 47.888822] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Any ideas? Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Tejun Heo <tj@kernel.org> |
|---|---|
| Date | 2015-07-23 20:40 +0200 |
| Message-ID | <pPtzr-6sr-13@gated-at.bofh.it> |
| In reply to | #1191179 |
Hello, On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote: > Something new in kernel 4.2 seems to have broken one of my hard drives > (ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the > relevant logs. > ... > [ 6.547628] ata2.00: qc timeout (cmd 0xec) > [ 6.547721] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 7.007213] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 16.997819] ata2.00: qc timeout (cmd 0xec) > [ 16.997910] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 16.997995] ata2: limiting SATA link speed to 3.0 Gbps > [ 17.457400] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) > [ 47.429257] ata2.00: qc timeout (cmd 0xec) > [ 47.429349] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 47.888822] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nothing really rings a bell. Timeouts on IDENTIFY. Could be IRQ related. Which controller is it (lspci -nn)? Also, can you try to bisect the issue? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Alex Deucher <alexdeucher@gmail.com> |
|---|---|
| Date | 2015-07-23 20:50 +0200 |
| Message-ID | <pPtJ8-6DM-15@gated-at.bofh.it> |
| In reply to | #1191213 |
On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo <tj@kernel.org> wrote: > Hello, > > On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote: >> Something new in kernel 4.2 seems to have broken one of my hard drives >> (ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the >> relevant logs. >> > ... >> [ 6.547628] ata2.00: qc timeout (cmd 0xec) >> [ 6.547721] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) >> [ 7.007213] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) >> [ 16.997819] ata2.00: qc timeout (cmd 0xec) >> [ 16.997910] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) >> [ 16.997995] ata2: limiting SATA link speed to 3.0 Gbps >> [ 17.457400] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) >> [ 47.429257] ata2.00: qc timeout (cmd 0xec) >> [ 47.429349] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) >> [ 47.888822] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) > > Nothing really rings a bell. Timeouts on IDENTIFY. Could be IRQ > related. Which controller is it (lspci -nn)? Also, can you try to > bisect the issue? 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7801] (rev 40) 00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD] FCH IDE Controller [1022:780c] I can take a look at bisecting later this week. Alex > > Thanks. > > -- > tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Jiang Liu <jiang.liu@linux.intel.com> |
|---|---|
| Date | 2015-07-27 05:10 +0200 |
| Message-ID | <pQGXD-5R8-3@gated-at.bofh.it> |
| In reply to | #1191222 |
On 2015/7/25 1:38, Alex Deucher wrote: > On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher <alexdeucher@gmail.com> wrote: >> On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo <tj@kernel.org> wrote: >>> Hello, >>> >>> On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote: >>>> Something new in kernel 4.2 seems to have broken one of my hard drives >>>> (ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the >>>> relevant logs. >>>> >>> ... >>>> [ 6.547628] ata2.00: qc timeout (cmd 0xec) >>>> [ 6.547721] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) >>>> [ 7.007213] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) >>>> [ 16.997819] ata2.00: qc timeout (cmd 0xec) >>>> [ 16.997910] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) >>>> [ 16.997995] ata2: limiting SATA link speed to 3.0 Gbps >>>> [ 17.457400] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) >>>> [ 47.429257] ata2.00: qc timeout (cmd 0xec) >>>> [ 47.429349] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) >>>> [ 47.888822] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) >>> >>> Nothing really rings a bell. Timeouts on IDENTIFY. Could be IRQ >>> related. Which controller is it (lspci -nn)? Also, can you try to >>> bisect the issue? >> >> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH >> SATA Controller [AHCI mode] [1022:7801] (rev 40) >> 00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD] FCH >> IDE Controller [1022:780c] >> >> I can take a look at bisecting later this week. > > You were right about the interrupts. This is an AMD Kaveri APU system. Hi Alex, Could you please help to provide more information about the system so we could identify the issue? Dmesg and /proc/interrupts from good and bad kernels are welcomed. Thanks! Gerry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web