public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Lex Hider <floss@lex.hider.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regression: monitor fails to sleep/suspend, forced to reboot to 	correct. 2.6.34-rc6
Date: Fri, 07 May 2010 01:47:16 -0700	[thread overview]
Message-ID: <4BE3D394.3030703@gmail.com> (raw)
In-Reply-To: <4BE3D03F.2010705@gmail.com>

On 05/07/2010 01:33 AM, Justin P. Mattock wrote:
>
>> Can you do a bisect?
>> (2.6.32 - HEAD shouldn't
>> take too long).
>>
>> Justin P. Mattock
>>
>>
>> I'm still a git newbie. What specific command should I run and what
>> output to post?
>> You want me to do it against HEAD vs "latest known working version"?
>>
>> Thanks,
>>
>> Lex.
>> --
> sure.. it's easy(just requires patience).
>
> do a:(in the source tree of kernel)
> gist bisect start (enter)
> git bisect bad (v2.6.*something, and/or enter for the current)
> then
> git bisect good v2.6.33
> (git bisect will think)
> then
> make menuconfig
> make (compile, reboot etc..)
> if it's a good kernel then
> (in source tree)
> git bisect bad(if the problem is still there git bisect bad).
Oops typo I should of said:
git bisect bad(if the problem is still there, and if it's good
git bisect good (then make(compiling), reboot, then:
> then
> keep going until git gives it's idea of the problem
> (then cry and complain to the authors that they fu*ked it up
> just messn);
>
> hope this help.
>
> Justin P. Mattock

was looking for the wiki for you, but Google
came up with a bunch of crap.
(will look for that in the morning etc..)

Justin P. Mattock

      reply	other threads:[~2010-05-07  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  2:30 Regression: monitor fails to sleep/suspend, forced to reboot to correct. 2.6.34-rc6 Lex Hider
2010-05-07  3:00 ` Justin P. Mattock
2010-05-07  8:14 ` Lex Hider
2010-05-07  8:33   ` Justin P. Mattock
2010-05-07  8:47     ` Justin P. Mattock [this message]

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=4BE3D394.3030703@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=floss@lex.hider.name \
    --cc=linux-kernel@vger.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