Skip to contentSkip to conversation

git bisect not accepting -git kernels

DISCUSSION Amit Walambe 7 participants 11 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

Hi!
I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For which I get following error :
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
Bad rev input: v2.6.22-git6

The repository is obtained by :
root@amit:/usr/src # git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git

I am running following git version on Debian Sid, updated today.

# git --version
git version 0.99.8.GIT
'# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'

I tried searching man-pages/documentation/website but couldn't find any references to git bisect on -git kernels. I would be grateful if anyone can help me find what's going wrong.

As I am not subscribed to the mailing-list, please cc me to all the messages on the thread. Thanks and Regards,

Signature · 10 lines
Amit Walambe
Design Engineer, Arcom Control Systems Ltd.
http://www.arcom.com
Tel: +44-(0)1223 411200 ext. 3204
Direct: +44-(0)1223 403465

_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.

This message has been virus scanned by MessageLabs.
#1 lore raw
Quoted 6 lines · Amit Walambe

Hi!
I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For which I get following error :
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
Bad rev input: v2.6.22-git6

Quoted 7 lines

The repository is obtained by :
root@amit:/usr/src # git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git

I am running following git version on Debian Sid, updated today.

# git --version
git version 0.99.8.GIT

There is a very old GIT version in your PATH (version 0.99*), which takes preference over the version from sid.

Quoted 2 lines

'# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'

-Peter

#2 lore raw
In reply to Amit Walambe

Hello,

Quoted 2 lines
# git --version
git version 0.99.8.GIT

this doesn't match

Quoted 1 line

'# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'

that. Maybe you should build your own git packages. Lucky you that it is pretty easy with debian. Have a look at this thread:

	http://groups.google.com/group/linux.kernel/browse_thread/thread/b8509269407c0fdc/d05d0547e7dfcf03?lnk=st&q=author%3AThomas+author%3AGlanzmann+git+linux.kernel&rnum=1#d05d0547e7dfcf03

especially the first post (scroll up).

Thomas

#3 lore raw

Hi,
Thanks for both the replies.

Quoted 8 lines · Thomas Glanzmann

Hello,

Quoted 2 lines
# git --version
git version 0.99.8.GIT

this doesn't match

Quoted 1 line

'# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'

This struck me as being weird, but I thought 'git' utility version is different than the package. My mistake! :)

Quoted 2 lines

that. Maybe you should build your own git packages. Lucky you that it is pretty easy with debian. Have a look at this thread:

I didn't build my own git version. What I did do was to remove the old git and ensure I am using the Debian installed one.

Now I am getting a different error :
root@amit:/usr/src/linux-git # which git /usr/bin/git
root@amit:/usr/src/linux-git # git --version
git version 1.5.2.3
root@amit:/usr/src/linux-git # git bisect good v2.6.22-rc6 root@amit:/usr/src/linux-git # git bisect bad v2.6.22-rc8
fatal: Needed a single revision root@amit:/usr/src/linux-git #

A quick search on the net didn't yield anything. Please help me find out what's going wrong. Thanks and Regards,

Signature · 10 lines
Amit Walambe
Design Engineer, Arcom Control Systems Ltd.
http://www.arcom.com
Tel: +44-(0)1223 411200 ext. 3204
Direct: +44-(0)1223 403465

_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.

This message has been virus scanned by MessageLabs.
#4 lore raw
Quoted 11 lines · Amit Walambe

I didn't build my own git version. What I did do was to remove the old git and ensure I am using the Debian installed one.

Now I am getting a different error :
root@amit:/usr/src/linux-git # which git /usr/bin/git
root@amit:/usr/src/linux-git # git --version
git version 1.5.2.3
root@amit:/usr/src/linux-git # git bisect good v2.6.22-rc6 root@amit:/usr/src/linux-git # git bisect bad v2.6.22-rc8
fatal: Needed a single revision root@amit:/usr/src/linux-git #

I should call it a day. Above commands are wrong. I need to work on -git kernels and not -rc kernels (as the above commands are showing). I am still getting the same errors I started with :

root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6 Bad rev input: v2.6.22-git6 root@amit:/usr/src/linux-git # root@amit:/usr/src/linux-git # root@amit:/usr/src/linux-git # git bisect good v2.6.22-git8 Bad rev input: v2.6.22-git8

Quoted 2 lines

A quick search on the net didn't yield anything. Please help me find out what's going wrong. Thanks and Regards,

The above greatly applies :)

Signature · 10 lines
Amit Walambe
Design Engineer, Arcom Control Systems Ltd.
http://www.arcom.com
Tel: +44-(0)1223 411200 ext. 3204
Direct: +44-(0)1223 403465

_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.

This message has been virus scanned by MessageLabs.
#5 lore raw
In reply to Amit Walambe
Quoted 9 lines · Amit Walambe

Hi!
I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For which I get following error :
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6 Bad rev input: v2.6.22-git6

The repository is obtained by :
root@amit:/usr/src # git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git

The -git# is added by a script and does not exists as tags. The same place where you retreive the -git files has a file identifying the commit that is the latest - use the SHA of this and you should be happy.

Sam

#6 lore raw
In reply to Amit Walambe
Quoted 10 lines · Amit Walambe

Hi!
I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For which I get following error :
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6 Bad rev input: v2.6.22-git6

The repository is obtained by :
root@amit:/usr/src # git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git

Quoted 8 lines

I am running following git version on Debian Sid, updated today.

# git --version
git version 0.99.8.GIT
'# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'

I tried searching man-pages/documentation/website but couldn't find any references to git bisect on -git kernels. I would be grateful if anyone can help me find what's going wrong.

The -git snapshots are made automatically by kernel.org, and their name is not included in the git repository. You could create tags for them like this:

git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809 git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa

... and afterwards you can use those revision names with bisect (or other git commands). I've got the commit IDs (i.e. those mysterious 40 hex digits above) from the first line of the changelogs; their URLs are:

http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.log
http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.log

René

#7 lore raw

Thanks a ton everyone for all the replies.
Here is the current status :

Quoted 14 lines · René Scharfe
Quoted 5 lines · Amit Walambe

Hi!
I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For which I get following error :
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6 Bad rev input: v2.6.22-git6

The -git snapshots are made automatically by kernel.org, and their name is not included in the git repository. You could create tags for them like this:

git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809 git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa

Quoted 6 lines

... and afterwards you can use those revision names with bisect (or other git commands). I've got the commit IDs (i.e. those mysterious 40 hex digits above) from the first line of the changelogs; their URLs are:

http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.log
http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.log

I found the commit ids in following file as well :
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.id
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.id

But telling good/bad points to git bisect still fails, whether I pass the commit-id or the tags I created with commands given by René :

root@amit:/usr/src/linux-git # git bisect good 8f41958bdd577731f7411c9605cfaa9db6766809
cat: .git/BISECT_NAMES: No such file or directory root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809 root@amit:/usr/src/linux-git # git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
cat: .git/BISECT_NAMES: No such file or directory root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8
cat: .git/BISECT_NAMES: No such file or directory

Thanks and Regards,

Signature · 10 lines
Amit Walambe
Design Engineer, Arcom Control Systems Ltd.
http://www.arcom.com
Tel: +44-(0)1223 411200 ext. 3204
Direct: +44-(0)1223 403465

_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.

This message has been virus scanned by MessageLabs.
#8 lore raw
Quoted 46 lines · Amit Walambe

Thanks a ton everyone for all the replies.
Here is the current status :

Quoted 14 lines · René Scharfe
Quoted 5 lines · Amit Walambe

Hi!
I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For which I get following error :
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6 Bad rev input: v2.6.22-git6

The -git snapshots are made automatically by kernel.org, and their name is not included in the git repository. You could create tags for them like this:

git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809 git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa

Quoted 6 lines

... and afterwards you can use those revision names with bisect (or other git commands). I've got the commit IDs (i.e. those mysterious 40 hex digits above) from the first line of the changelogs; their URLs are:

http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.log
http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.log

I found the commit ids in following file as well :
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.id
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.id

But telling good/bad points to git bisect still fails, whether I pass the commit-id or the tags I created with commands given by René :

root@amit:/usr/src/linux-git # git bisect good 8f41958bdd577731f7411c9605cfaa9db6766809
cat: .git/BISECT_NAMES: No such file or directory root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809 root@amit:/usr/src/linux-git # git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
cat: .git/BISECT_NAMES: No such file or directory root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8
cat: .git/BISECT_NAMES: No such file or directory

Quoted 1 line

Thanks and Regards,

You need to start off by saying

$ git bisect start

to set up the necessary infrastructure.

Rogan

#9 lore raw
In reply to Amit Walambe
Quoted 18 lines · Amit Walambe

But telling good/bad points to git bisect still fails, whether I pass the commit-id or the tags I created with commands given by René :

root@amit:/usr/src/linux-git # git bisect good 8f41958bdd577731f7411c9605cfaa9db6766809
cat: .git/BISECT_NAMES: No such file or directory root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809 root@amit:/usr/src/linux-git # git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
cat: .git/BISECT_NAMES: No such file or directory root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8
cat: .git/BISECT_NAMES: No such file or directory

Quoted 2 lines

Thanks and Regards,

you seem to be missing a "git bisect start" from that sequence ... see the man page for more details.

Signature · 4 lines
Julian

 ---
Peter Griffin:  You wanna talk about awkward moments? Once, during sex, I called Lois "Frank". Your move, Sherlock.
#10 lore raw
Quoted 20 lines · Julian Phillips
Quoted 18 lines · Amit Walambe

But telling good/bad points to git bisect still fails, whether I pass the commit-id or the tags I created with commands given by René :

root@amit:/usr/src/linux-git # git bisect good 8f41958bdd577731f7411c9605cfaa9db6766809
cat: .git/BISECT_NAMES: No such file or directory root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809 root@amit:/usr/src/linux-git # git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
cat: .git/BISECT_NAMES: No such file or directory root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8
cat: .git/BISECT_NAMES: No such file or directory

Quoted 4 lines
Quoted 2 lines

Thanks and Regards,

you seem to be missing a "git bisect start" from that sequence ... see the man page for more details.

Yes indeed. Somehow the state was messed up due to different commands I had tried. Now it works ok. root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8
Bisecting: 362 revisions left to test after this
[02b2318e07f98a7cdf7089a4457a8d62424aa824] Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6 Thanks a lot for everyone for their help. _Much appreciated_!
Best Regards,

Signature · 10 lines
Amit Walambe
Design Engineer, Arcom Control Systems Ltd.
http://www.arcom.com
Tel: +44-(0)1223 411200 ext. 3204
Direct: +44-(0)1223 403465

_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.

This message has been virus scanned by MessageLabs.