From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Matthew Garrett <mjg@redhat.com>, Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
linux-pm@lists.osdl.org
Subject: Re: [Bugme-new] [Bug 16396] New: [bisected] resume from suspend freezes system
Date: Mon, 19 Jul 2010 03:25:41 +0300 [thread overview]
Message-ID: <1279499141.17672.10.camel@localhost.localdomain> (raw)
In-Reply-To: <201007151045.47302.rjw@sisk.pl>
On Thu, 2010-07-15 at 10:45 +0200, Rafael J. Wysocki wrote:
> On Thursday, July 15, 2010, Andrew Morton wrote:
> > On Thu, 15 Jul 2010 02:32:43 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
> >
> > > https://bugzilla.kernel.org/show_bug.cgi?id=16396
> >
> > post-2.6.34 regression, bisected to an ACPi commit from Matthew.
>
> Well, that's something I was afraid of.
>
> So, the theory that we'll be fine if we do what Windows does really doesn't
> match reality.
>
> Matthew, Len, any ideas?
One idea would be to see when exactly windows saves the NVS.
Maybe it does that earlier (that it relative to _PTS, device suspend,
etc...)
Maybe this system run Win7, and MS fixed that bug?
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2010-07-19 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16396-10286@https.bugzilla.kernel.org/>
[not found] ` <20100714194555.2b23d803.akpm@linux-foundation.org>
2010-07-15 8:45 ` [Bugme-new] [Bug 16396] New: [bisected] resume from suspend freezes system Rafael J. Wysocki
2010-07-19 0:25 ` Maxim Levitsky [this message]
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=1279499141.17672.10.camel@localhost.localdomain \
--to=maximlevitsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=macro@ds2.pg.gda.pl \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
/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