From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 62351] Marvell PCIe SSD controller 0x9183 suspend/resume problem
Date: Mon, 30 Sep 2013 21:47:14 +0000 [thread overview]
Message-ID: <bug-62351-11633-po8hTZ5ziT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62351-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=62351
--- Comment #4 from Tejun Heo <tj@kernel.org> ---
So, when the machine boots up libata doesn't touch the LPM setting and just
considers it "max_performance", which may or may not be true. I think it'd work
the same if you just set the lpm knob to max_performance explicitly. The
problem is that your BIOS is most likely configuring DIPM on both the device
and host sides during boot; however, after coming back from suspend, the device
side seems to be configured but the host side isn't, so the device's LPM
operations register as link events to the controller leading to the spurious
failures.
Maybe we should set max_performance mode explicitly during boot requiring the
user to explicitly set min_power mode if [s]he wants to but then we might cause
power regression on some setups.
Anyways, can you please verify echoing max_performance also makes the issue go
away?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-09-30 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-62351-11633@https.bugzilla.kernel.org/>
2013-09-30 10:33 ` [Bug 62351] Marvell PCIe SSD controller 0x9183 suspend/resume problem bugzilla-daemon
2013-09-30 19:14 ` bugzilla-daemon
2013-09-30 21:38 ` bugzilla-daemon
2013-09-30 21:47 ` bugzilla-daemon [this message]
2013-09-30 23:02 ` bugzilla-daemon
2013-10-01 14:44 ` bugzilla-daemon
2013-10-03 1:40 ` bugzilla-daemon
2013-12-26 14:29 ` bugzilla-daemon
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=bug-62351-11633-po8hTZ5ziT@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@vger.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).