public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Sid Boyce <g3vbv@blueyonder.co.uk>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel@vger.kernel.org, auxsvr@gmail.com
Subject: Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
Date: Wed, 28 Mar 2007 06:14:07 +0200	[thread overview]
Message-ID: <20070328041407.GM16477@stusta.de> (raw)
In-Reply-To: <4609E04D.408@blueyonder.co.uk>

On Wed, Mar 28, 2007 at 04:26:05AM +0100, Sid Boyce wrote:
> Eric W. Biederman wrote:
> >Sid Boyce <g3vbv@blueyonder.co.uk> writes:
> >
> >  
> >>This is what I've got so far on the first boot, I shall have to check the
> >>manpage for git-bisect again to see if there is anything else to be added,
> >>nothing enlightening seen so far - further reboots to be done.
> >>    
> >
> >I'm a little confused at what I am seeing below.
> >Normally what happens is that after a kernel compile and test.  You call
> >"git-bisect bad" or "git-bisect good" and then git-bisect picks the next
> >kernel to test.  Then you compile and test that one.  It looks like
> >you called git-bisect bad several times in a row without testing....
> >
> >
> >Eric
> >
> >  
> This is the procedure I followed.
> <--  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]
> ========================================================
> I built and installed the kernel downloaded using "cg-clone", booted it 
> up  and ran "git bisect bad".  I'm also somewhat confused as the first 
> failing kernel is 2.6.20-git11, the Makefile says the kernel got with 
> cg-clone is actually 2.6.21-rc4 and it built as  2.6.20-g208367ee.
> Regards
> Sid.
> 
> >>barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
> >>Bisecting: 22 revisions left to test after this
> >>[3fc605a2aa38899c12180ca311f1eeb61a6d867e] knfsd: allow the server to 
> >>provide a
> >>gid list when using AUTH_UNIX authentication
> >>rrabas:/usr/src/GIT/linux-2.6 # git bisect bad
>...

I think I got your problem:

After rebooting, you do "git bisect [bad|good]"  *once*.

Then recompile the kernel from the current tree, reboot, and again
*once* "git bisect [bad|good]".

etc.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-03-28  4:14 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
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 [this message]
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=20070328041407.GM16477@stusta.de \
    --to=bunk@stusta.de \
    --cc=auxsvr@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=g3vbv@blueyonder.co.uk \
    --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