From: "H. Peter Anvin" <hpa@zytor.com>
To: Jonas Heinrich <onny@project-insanity.org>,
rjw@sisk.pl, len.brown@intel.com, pavel@ucw.cz,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [Bisected] 3.7-rc1 can't resume
Date: Sun, 17 Feb 2013 12:52:30 -0800 [thread overview]
Message-ID: <1209aeb9-7d97-4444-9038-31d8fc588270@email.android.com> (raw)
In-Reply-To: <20130217174824.GA649@onny>
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.
Jonas Heinrich <onny@project-insanity.org> wrote:
>Hello,
>since kernel version 3.7-rc1 I can't resume my notebook (Thinkpad T43)
>from suspend2ram anymore.
>
>I started a kernel bisection (see bisection_log in attachement). Also
>see kernel conifg @ attachement.
>
>The culprit commit seems to be:
>- x86, smap: Do not abuse the [f][x]rstor_checking() functions for user
>space
>commit e139e95590dfebab81841bf7a3ac46500f51a47c
>
>Unfortunately, just reverting the commit did not resolved the issue.
>Maybe I did something wrong, I'm not so familiar with this kind of
>kernel bisection.
>
>Best regards,
>Jonas
>
>ps. I'm not yet subscribed to the mailing list so I hope you'll recieve
>this message.
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2013-02-17 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 17:48 [Bisected] 3.7-rc1 can't resume Jonas Heinrich
2013-02-17 20:40 ` Rafael J. Wysocki
2013-02-17 20:52 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-18 15:54 Jonas Heinrich
2013-02-18 16:21 ` H. Peter Anvin
2013-02-23 13:18 ` Jonas Heinrich
2013-02-23 21:54 ` H. Peter Anvin
2012-10-18 12:26 Cédric Godin
2012-10-18 14:17 ` H. Peter Anvin
2012-10-19 7:10 ` Cédric Godin
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=1209aeb9-7d97-4444-9038-31d8fc588270@email.android.com \
--to=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=onny@project-insanity.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).