From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 62351] Marvell PCIe SSD controller 0x9183 suspend/resume problem
Date: Thu, 03 Oct 2013 01:40:10 +0000 [thread overview]
Message-ID: <bug-62351-11633-X1S1gy6QWM@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 #7 from Patrik Jakobsson <patrik.r.jakobsson@gmail.com> ---
> So, if you set "max_performance" explicitly, it works fine before suspending but after resuming it causes problems?
Yes, the only time I can set max_performance without getting errors is before
first suspend.
> What happens if you set "max_performance" explicitly instead of "min_power" after resume while the errors are happening? Does that resolve the issue too?
Setting max_performance explicitly after resume doesn't help. And if I first
set min_power after resume to stop the errors and then try max_performance
again, it will start spitting out errors again.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-03 1:40 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
2013-10-01 14:44 ` bugzilla-daemon
2013-10-03 1:40 ` bugzilla-daemon [this message]
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-X1S1gy6QWM@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.