[lkml]   [2013]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [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 <> 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
>Someone on LKML already reported an issue with this commit
>( , 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
>every time I try to resume my notebook.
>Best regards,

Sent from my mobile phone. Please excuse brevity and lack of formatting.

 \ /
  Last update: 2013-02-18 18:01    [W:0.093 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site