public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Borislav Petkov <bp@alien8.de>, Shane Huang <Shane.Huang@amd.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: ata1: COMRESET failed
Date: Tue, 08 Jan 2013 12:46:20 +0100	[thread overview]
Message-ID: <50EC070C.2090101@suse.cz> (raw)
In-Reply-To: <50EB770A.4090302@intel.com>

On 01/08/2013 02:31 AM, Aaron Lu wrote:
> On 01/08/2013 01:24 AM, Borislav Petkov wrote:
>> Adding some more people.
>>
>> Aaron, Shane, do you guys have any ideas? I've been seeing something
>> similar on an AMD desktop box recently and Jiri sees it on a laptop with
>> an SSD.
> 
> I've seen a similar problem on a bug report recently for a Crucial SSD,
> and upgrading the disk's firmware fixed the problem:
> https://bugzilla.kernel.org/show_bug.cgi?id=49701
> 
> If the controller has problem, it should have problems for all kinds of
> disks attached to it. So possible to test with other disks, Jiri?

Yes, I tested a normal spinning disk and it does not happen with that.
This happens only with this Intel SSD: SSDSA2M080G2GC

So I will try to investigate how to upgrade the firmware and will report.

thakns,
-- 
js
suse labs

  reply	other threads:[~2013-01-08 11:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 11:56 ata1: COMRESET failed Jiri Slaby
2012-12-03 11:16 ` Jiri Slaby
2012-12-03 11:57   ` Borislav Petkov
2013-01-07 17:24     ` Borislav Petkov
2013-01-08  1:31       ` Aaron Lu
2013-01-08 11:46         ` Jiri Slaby [this message]
2013-01-08 19:57           ` Jiri Slaby
2013-01-08 20:08             ` Borislav Petkov

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=50EC070C.2090101@suse.cz \
    --to=jslaby@suse.cz \
    --cc=Shane.Huang@amd.com \
    --cc=aaron.lu@intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bp@alien8.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --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