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 23:02:29 +0000 [thread overview]
Message-ID: <bug-62351-11633-BHLQooxxCM@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 #5 from Patrik Jakobsson <patrik.r.jakobsson@gmail.com> ---
Here are all the test cases:
After boot: LPM policy reports max_performance and min_power and
max_performance can be switched back and forth without any errors.
Before suspend: If I don't touch LPM policy after boot (still reporting
max_performance) I can successfully suspend and LPM policy still reports
max_performance (though probably incorrect) after resume.
Before suspend: If I explicity set max_performance after boot and go into
suspend it fails. If I set min_power back in this state, the errors stop.
Before suspend: If I explicity set min_power after boot and go into suspend it
succeeds.
So I must either never touch the LPM policy or set it to min_power to not get
the errors on resume. min_power seems to be what the hardware is set to but
doesn't get reported correctly (as you say) until I've actually set it to
something.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-09-30 23:02 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
2013-09-30 23:02 ` bugzilla-daemon [this message]
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-BHLQooxxCM@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).