From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, auxsvr@gmail.com
Subject: Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
Date: Thu, 22 Mar 2007 19:49:16 +0000 [thread overview]
Message-ID: <4602DDBC.5000106@blueyonder.co.uk> (raw)
In-Reply-To: <20070322105908.GS752@stusta.de>
Adrian Bunk wrote:
> On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
>
>> On Thu, 22 Mar 2007 01:32:36 +0000 Sid Boyce wrote:
>>
>>
>>> ...
>>>
>> There's not a lot of docs out there.
>>
>> The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
>>
>> Linus's email doc:
>> http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
>>
>> I worked on something over last weekend, but it doesn't really add
>> much to the references above.
>> ...
>>
>
>
> FWIW:
> My standard instructions for users who are asked to bisect are [1]:
>
>
> <-- snip -->
>
> # install git and cogito on your computer
>
> # clone Linus' tree:
> cg-clone \
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>
> # start bisecting:
> cd linux-2.6
> git bisect start
> git bisect bad 86a71dbd3e81e8870d0f0e56b87875f57e58222b
> git bisect good ac98695d6c1508b724f246f38ce57fb4e3cec356
>
> # start round
> cp /path/to/.config .
> make oldconfig
> make
> # install kernel, check whether it's good or bad, then:
> git bisect [bad|good]
> # start next round
>
>
> After at about 8 reboots, you'll have found the guilty commit
> ("... is first bad commit").
>
>
> More information on git bisecting:
> man git-bisect
>
> <-- snip -->
>
>
>
>> ~Randy
>>
>
> cu
> Adrian
>
> [1] the start and end commits and the number of reboots are variable,
> but the rest of the text is generic
>
>
Kernel built and installed, so I shall have something to report in the
next couple of days.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next prev parent reply other threads:[~2007-03-22 19:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 15:19 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently Sid Boyce
2007-02-28 16:05 ` auxsvr
2007-03-08 5:47 ` Andrew Morton
2007-03-08 7:34 ` Sid Boyce
2007-03-21 17:43 ` Sid Boyce
2007-03-21 19:34 ` Adrian Bunk
2007-03-21 20:17 ` Eric W. Biederman
2007-03-22 1:32 ` Sid Boyce
2007-03-22 1:42 ` Randy Dunlap
2007-03-22 10:59 ` Adrian Bunk
2007-03-22 19:49 ` Sid Boyce [this message]
2007-03-26 12:02 ` boris
2007-03-27 3:38 ` Sid Boyce
2007-03-27 13:48 ` Eric W. Biederman
2007-03-28 3:26 ` Sid Boyce
2007-03-28 4:14 ` Adrian Bunk
2007-03-28 13:17 ` Eric W. Biederman
2007-03-29 11:35 ` Sid Boyce
2007-03-30 18:00 ` Adrian Bunk
2007-03-29 4:04 ` Eric W. Biederman
2007-03-29 11:37 ` Sid Boyce
2007-03-29 16:16 ` Sid Boyce
-- strict thread matches above, loose matches on Subject: below --
2007-02-28 16:24 Sid Boyce
[not found] <45E5DE32.2070902@argo.co.il>
2007-03-01 13:52 ` Sid Boyce
2007-03-01 15:11 ` Avi Kivity
2007-03-02 4:22 ` Sid Boyce
[not found] <45E939E1.8050501@argo.co.il>
2007-03-03 20:30 ` Sid Boyce
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=4602DDBC.5000106@blueyonder.co.uk \
--to=g3vbv@blueyonder.co.uk \
--cc=auxsvr@gmail.com \
--cc=bunk@stusta.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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