lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 15 Jun 2012 14:15:51 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Cong Wang <xiyou.wangcong@...il.com>
Cc:	Cong Wang <amwang@...hat.com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Young <dyoung@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Yinghai Lu <yinghai.lu@...cle.com>
Subject: Re: [PATCH] x86: revert "x86: Fix S4 regression"

At Fri, 15 Jun 2012 19:11:12 +0800,
Cong Wang wrote:
> 
> On Tue, Jun 12, 2012 at 1:21 PM, Cong Wang <amwang@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ