From: Ondrej Zary <linux@rainbow-software.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] [RFC] Save/restore MISC_ENABLE register
Date: Mon, 7 Jun 2010 21:02:43 +0200 [thread overview]
Message-ID: <201006072102.46728.linux@rainbow-software.org> (raw)
In-Reply-To: <4C0D4032.6020907@zytor.com>
On Monday 07 June 2010 20:53:38 H. Peter Anvin wrote:
> On 06/07/2010 11:51 AM, Ondrej Zary wrote:
> > Something like this?
> >
> > Save/restore MISC_ENABLE register on suspend/resume.
> > This fixes OOPS (invalid opcode) on resume from STR on Asus P4P800-VM,
> > which wakes up with MWAIT disabled.
> >
> > Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
>
> Yes, that's a lot better.
>
> I presume you have tested it. Rafael, do you want to take this or should
> I?
Yes, it works on the P4P800-VM. Don't have any x86_64 machine to test.
--
Ondrej Zary
next prev parent reply other threads:[~2010-06-07 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 16:14 [PATCH] [RFC] Save/restore MISC_ENABLE register Ondrej Zary
2010-06-07 17:27 ` H. Peter Anvin
2010-06-07 17:27 ` H. Peter Anvin
2010-06-07 18:51 ` Ondrej Zary
2010-06-07 18:51 ` Ondrej Zary
2010-06-07 18:53 ` H. Peter Anvin
2010-06-07 18:53 ` H. Peter Anvin
2010-06-07 19:02 ` Ondrej Zary
2010-06-07 19:02 ` Ondrej Zary [this message]
2010-06-07 21:05 ` Rafael J. Wysocki
2010-06-07 21:06 ` H. Peter Anvin
2010-06-07 21:06 ` H. Peter Anvin
2010-06-07 21:09 ` Alan Stern
2010-06-07 21:09 ` Alan Stern
2010-06-07 21:05 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2010-06-07 16:14 Ondrej Zary
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=201006072102.46728.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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.