public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Aaron Lu <aaron.lu@intel.com>, Shane Huang <Shane.Huang@amd.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
	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: Mon, 7 Jan 2013 18:24:25 +0100	[thread overview]
Message-ID: <20130107172425.GD5954@liondog.tnic> (raw)
In-Reply-To: <20121203115734.GA32243@liondog.tnic>

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.

Here's Jiri's original mail with more info: http://lkml.org/lkml/2012/10/26/208

Thanks.

On Mon, Dec 03, 2012 at 12:57:34PM +0100, Borislav Petkov wrote:
> On Mon, Dec 03, 2012 at 12:16:44PM +0100, Jiri Slaby wrote:
> > On 10/26/2012 01:56 PM, Jiri Slaby wrote:
> > > Hello,
> > > 
> > > at every boot I'm seeing:
> > > 
> > > At 5th second:
> > > ata1: link is slow to respond, please be patient (ready=0)
> > > 
> > > At 10th second:
> > > ata1: COMRESET failed (errno=-16)
> > > ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> > > ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
> > > ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
> > > ata1.00: ATA-7: INTEL SSDSA2M080G2GC, 2CV102HD, max UDMA/133
> > > ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32)
> > > ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
> > > ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
> > > ata1.00: configured for UDMA/133
> > > scsi 0:0:0:0: Direct-Access     ATA      INTEL SSDSA2M080 2CV1 PQ: 0 ANSI: 5
> > > 
> > > 
> > > So that I have to wait 5 s for the disk to come up. I tried 3.4.15 and
> > > 3.6.3, both with the same result.
> > > 
> > > 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset
> > > Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
> > > 
> > > Any ideas what is going on?
> > 
> > Anybody? I also tried 3.0, it's there too. And libahci.skip_host_reset=1
> > works around the issue.
> 
> FWIW, I had the same issue on an AMD chipset at the old job. It needs to
> reset SATA link for some reason, probably BIOS programs it wrongly...
> 
> + Alan.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-01-07 17:24 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 [this message]
2013-01-08  1:31       ` Aaron Lu
2013-01-08 11:46         ` Jiri Slaby
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=20130107172425.GD5954@liondog.tnic \
    --to=bp@alien8.de \
    --cc=Shane.Huang@amd.com \
    --cc=aaron.lu@intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=jslaby@suse.cz \
    --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