linux-kernel - Re: [Bisected] 3.7-rc1 can't resume

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]

Message-ID: <cfd96a3d-5834-4687-b9de-9f044f43b588@email.android.com>
Date:	Mon, 18 Feb 2013 08:21:03 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jonas Heinrich <onny@...ject-insanity.org>, len.brown@...el.com,
	pavel@....cz, tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
	rjw@...k.pl
CC:	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [Bisected] 3.7-rc1 can't resume

I might be able to get my hands on a T43 later this week and see if I can reproduce this.  This patch seems more plausible, at least... but still puzzling.

Jonas Heinrich <onny@...ject-insanity.org> wrote:

>On 02-17 21:40, Rafael J. Wysocki wrote:
>> Does the commit immediately preceding this one behave correctly?
>Strangely the preceding commit works well, so I bisected the kernel
>again, this time more carefully and I've got a different result!
>(see bisect_log attachement).
>It seems to be commit 73201dbec64aebf6b0dca855b523f437972dc7bb 
>(https://patchwork.kernel.org/patch/1511921/).
>Someone on LKML already reported an issue with this commit
>(https://lkml.org/lkml/2012/10/18/228) , but Peter
>Anvins patch got already applied in newer versions.
>Reverting this patch with the recent git clone seems to be difficult
>because it already has too much dependencies.
>
>Additionally I've included dmesg dumps of the last good and the bad
>kernel version.
>
>On 02-17 12:52, H. Peter Anvin wrote:
>> T43 is quite old... which might have exposed unique bugs.  How
>reliable is the failure?  Even one misidentified commit results in git
>bisect giving garbage.
>It affects really all versions after that commit and the failure
>happens
>every time I try to resume my notebook.
>
>Best regards,
>Jonas

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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/