From: Tejun Heo <tj@kernel.org>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] libata updates for 2.6.37
Date: Tue, 30 Nov 2010 15:13:58 +0100 [thread overview]
Message-ID: <4CF506A6.4020200@kernel.org> (raw)
In-Reply-To: <20101129180755.GK15818@bombadil.infradead.org>
Hello,
On 11/29/2010 07:07 PM, Kyle McMartin wrote:
> On Thu, Oct 21, 2010 at 09:23:02PM -0400, Jeff Garzik wrote:
>> 1) Link Power Management (LPM) rewrite
>>
>
> Hrm, this is causing issues for me... When I resume from suspend on my
> thinkpad X201s I get:
>
> [ 2454.478673] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 2454.487736] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES)
> succeeded
> [ 2454.487742] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE
> filtered out
> [repeated a few times]
> [ 2454.492688] ata1.00: configured for UDMA/100
> [ 2454.506690] ata1.00: configured for UDMA/100
> [ 2454.506696] ata1: EH complete
> [...]
> [ 2455.097874] ata1.00: configured for UDMA/100
> [ 2455.097882] ata1: EH complete
> [...]
> [ 2455.386756] ata1.00: failed to enable DIPM, Emask 0x100
> [ 2455.386768] ata1: hard resetting link
> [...]
> [ 2455.847925] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 2455.849372] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES)
> succeeded
> [ 2455.849380] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE
> LOCK) filtered out
> [ditto]
> [ 2455.854171] ata1.00: configured for UDMA/100
> [ 2455.854480] ata1.00: failed to enable DIPM, Emask 0x100
> [ 2455.854484] ata1: disabling LPM on the link
> [ 2455.854489] ata1: limiting SATA link speed to 1.5 Gbps
> [ 2455.854494] ata1.00: limiting speed to UDMA/100:PIO3
>
> Tejun, any ideas how I can debug this?
Hmm... DIPM commands are failing with AC_ERR_OTHER. Other than DIPM
not being configured and speed capped at 1.5Gbps, the machine works
fine afterwards, right? Are you up for applying debug patches?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-11-30 14:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 1:23 [git patches] libata updates for 2.6.37 Jeff Garzik
2010-11-29 18:07 ` Kyle McMartin
2010-11-30 14:13 ` Tejun Heo [this message]
2010-11-30 15:38 ` Kyle McMartin
2010-11-30 16:29 ` Tejun Heo
2010-11-30 16:31 ` Kyle McMartin
2010-11-30 17:53 ` Kyle McMartin
2010-11-30 21:09 ` Kyle McMartin
2010-12-01 11:17 ` Tejun Heo
2010-12-01 12:44 ` Kyle McMartin
2010-12-01 14:19 ` Tejun Heo
2010-12-01 15:50 ` Kyle McMartin
2010-12-01 20:09 ` Kyle McMartin
2010-12-02 10:17 ` Tejun Heo
2010-12-02 21:23 ` Kyle McMartin
2010-12-03 10:10 ` Tejun Heo
2010-12-03 11:59 ` Kyle McMartin
2010-12-06 16:07 ` Kyle McMartin
2010-12-06 17:46 ` Tejun Heo
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=4CF506A6.4020200@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=kyle@mcmartin.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).