From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: Adrian Bunk <bunk@stusta.de>
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: Thu, 29 Mar 2007 12:35:42 +0100 [thread overview]
Message-ID: <460BA48E.4060407@blueyonder.co.uk> (raw)
In-Reply-To: <20070328041407.GM16477@stusta.de>
Adrian Bunk wrote:
> 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
>
>
If I boot up on 2.6.20-git10 and run "git bisect bad", "git bisect good
v2.6.20-git10" or "git bisect bad v2.6.20-git11", it says it's not a git
repo.
I am still no clearer what's required. If I do "cg-clone" I get
2.6.21-rc5. The previous one got me 2.6.21-rc4.
The manpages and the tutorials I've looked at are quite cryptic and the
commands do not produce the expected results.
As indicated above, I followed the instructions bullet by bullet without
any clear understanding of the tools.
1) Ran the commands as above,cg-clone; git start; git bisect bad
<checksum>;git bisect good <checksum of 2.6.20-git10 > I presume.
2) 2.6.20-git10 is the last good kernel.
3) 2.6.20-git11 and later are all bad.
4) I do cg-clone which gives a kernel whose Makefile is 2.6.21-rc4 (or
whatever is current).
5) I get a kernel named 2.6.20-g208367e after make - rebooted and it
fails the same way as 2.6.20-git11.
6) ran "git bisect bad".
Looking through the directories after cg-clone
barrabas:/ftp/mar07/GIT/linux-2.6 # ls .git/refs/tags/
v2.6.11 v2.6.12-rc5 v2.6.13-rc4 v2.6.14-rc2 v2.6.15-rc2
v2.6.16 v2.6.16-rc6 v2.6.17-rc5 v2.6.18-rc4 v2.6.19-rc2
v2.6.20-rc1 v2.6.20-rc7
v2.6.11-tree v2.6.12-rc6 v2.6.13-rc5 v2.6.14-rc3 v2.6.15-rc3
v2.6.16-rc1 v2.6.17 v2.6.17-rc6 v2.6.18-rc5 v2.6.19-rc3
v2.6.20-rc2 v2.6.21-rc1
v2.6.12 v2.6.13 v2.6.13-rc6 v2.6.14-rc4 v2.6.15-rc4
v2.6.16-rc2 v2.6.17-rc1 v2.6.18 v2.6.18-rc6 v2.6.19-rc4
v2.6.20-rc3 v2.6.21-rc2
v2.6.12-rc2 v2.6.13-rc1 v2.6.13-rc7 v2.6.14-rc5 v2.6.15-rc5
v2.6.16-rc3 v2.6.17-rc2 v2.6.18-rc1 v2.6.18-rc7 v2.6.19-rc5
v2.6.20-rc4 v2.6.21-rc3
v2.6.12-rc3 v2.6.13-rc2 v2.6.14 v2.6.15 v2.6.15-rc6
v2.6.16-rc4 v2.6.17-rc3 v2.6.18-rc2 v2.6.19 v2.6.19-rc6
v2.6.20-rc5 v2.6.21-rc4
v2.6.12-rc4 v2.6.13-rc3 v2.6.14-rc1 v2.6.15-rc1 v2.6.15-rc7
v2.6.16-rc5 v2.6.17-rc4 v2.6.18-rc3 v2.6.19-rc1 v2.6.20
v2.6.20-rc6 v2.6.21-rc5
barrabas:/ftp/mar07/GIT/linux-2.6 # ls .git/refs/bisect/
bad good-ac98695d6c1508b724f246f38ce57fb4e3cec356
barrabas:/ftp/mar07/GIT/linux-2.6 # ls .git/refs/heads/
bisect master origin
barrabas:/ftp/mar07/GIT/linux-2.6 # less .git/refs/heads/bisect
208367eeec8d6f6fcee1a0672af2149aeee7b658
barrabas:/ftp/mar07/GIT/linux-2.6 # ls .git/branches/
barrabas:/ftp/mar07/GIT/linux-2.6 # ls
arch COPYING crypto drivers .git include ipc
kernel .mailmap Makefile net REPORTING-BUGS security usr
block CREDITS Documentation fs .gitignore init Kbuild
lib MAINTAINERS mm README scripts sound
# less BISECT_LOG
git-bisect start
# bad: [86a71dbd3e81e8870d0f0e56b87875f57e58222b] sysctl: hide the
sysctl proc inodes from selinux
git-bisect bad 86a71dbd3e81e8870d0f0e56b87875f57e58222b
# good: [ac98695d6c1508b724f246f38ce57fb4e3cec356] Merge branch 'master'
of /home/trondmy/kernel/linux-2.6/
git-bisect good ac98695d6c1508b724f246f38ce57fb4e3cec356
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-29 11:36 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
2007-03-28 13:17 ` Eric W. Biederman
2007-03-29 11:35 ` Sid Boyce [this message]
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=460BA48E.4060407@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.