linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: Alex Deucher <alexdeucher@gmail.com>, Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: ATA failure regression in kernel 4.2
Date: Mon, 27 Jul 2015 11:01:54 +0800	[thread overview]
Message-ID: <55B59F22.2010102@linux.intel.com> (raw)
In-Reply-To: <CADnq5_PNrHMMOu8y1MDbC3pc2Lza1tw+W8JjTCtpfuOb4vis=A@mail.gmail.com>

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

  reply	other threads:[~2015-07-27  3:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 17:48 ATA failure regression in kernel 4.2 Alex Deucher
2015-07-23 18:35 ` Tejun Heo
2015-07-23 18:44   ` Alex Deucher
2015-07-24 17:38     ` Alex Deucher
2015-07-27  3:01       ` Jiang Liu [this message]
2015-07-27 15:21         ` Alex Deucher
2015-07-27 16:30           ` Jiang Liu
2015-07-27 17:36             ` Alex Deucher
2015-07-28 18:19             ` Alex Deucher
2015-07-28 18:37               ` Alexander Holler
2015-07-30 17:01                 ` [Debug Patch] Collect more information about the regression Jiang Liu
2015-07-31 10:38                 ` ATA failure regression in kernel 4.2 Alexander Holler
2015-07-31 10:42                   ` Jiang Liu
2015-07-31 18:59                     ` Alexander Holler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55B59F22.2010102@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=alexdeucher@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).