From: Takashi Iwai <tiwai@suse.de>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Cong Wang <amwang@redhat.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Dave Young <dyoung@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Yinghai Lu <yinghai.lu@oracle.com>
Subject: Re: [PATCH] x86: revert "x86: Fix S4 regression"
Date: Fri, 15 Jun 2012 14:15:51 +0200 [thread overview]
Message-ID: <s5h8vfoojns.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAM_iQpUq39+VQMU6rq78iqpy2m-PnSwWUW4M3WYjpecVVv4jhw@mail.gmail.com>
At Fri, 15 Jun 2012 19:11:12 +0800,
Cong Wang wrote:
>
> On Tue, Jun 12, 2012 at 1:21 PM, Cong Wang <amwang@redhat.com> wrote:
> >
> > Takashi, could you help to test if the S4 regression is still
> > there after this patch?
>
> Hello,
>
> Any comments?
>
> I have tested this revert on my laptop, with running simple
> "suspend and resume" test for several times, I didn't see any
> problem.
Sorry for the late response.
The problem happens only on certain laptops. I've tested the recent
IvyBridge laptops and these were OK with the reverted patch. But a
SandyBridge laptop, the one I tested in the last year, still hits the
S4 problem with the reverted kernel.
But, the recent kernels seem to have other S4 problems on this
machine, so it's not 100% clear whether it's triggered by that.
At least, it jumpts to the boot at S4 resume more frequently when the
patch is reverted.
So, I need to start from 2.6.32 again to see what regressions have
been introduced. It'll take time, since I'd have to S4 20 cycles
for reproducing the bug.
Takashi
next prev parent reply other threads:[~2012-06-15 12:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 5:21 [PATCH] x86: revert "x86: Fix S4 regression" Cong Wang
2012-06-15 11:11 ` Cong Wang
2012-06-15 12:15 ` Takashi Iwai [this message]
2012-06-15 19:09 ` Rafael J. Wysocki
2012-06-18 3:10 ` Cong Wang
2012-07-17 3:15 ` Takao Indoh
2012-07-23 10:00 ` Dave Young
2012-07-23 11:22 ` Takao Indoh
2012-07-23 12:51 ` Dave Young
2012-07-24 15:55 ` Cong Wang
2012-07-25 0:19 ` Takao Indoh
2012-08-06 20:42 ` Vivek Goyal
2012-08-06 21:55 ` Yinghai Lu
2012-08-11 17:57 ` Jerry Snitselaar
2012-08-11 18:26 ` Jerry Snitselaar
2012-08-11 18:34 ` H. Peter Anvin
2012-08-11 18:39 ` H. Peter Anvin
2012-08-11 19:33 ` Tejun Heo
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=s5h8vfoojns.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=xiyou.wangcong@gmail.com \
--cc=yinghai.lu@oracle.com \
/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