Re: spontaneous reboots and hangs on x86_64

From: Mariusz Kozlowski
Date: Fri May 16 2008 - 01:18:18 EST

Hello Stephen,

> On Thu, 15 May 2008 23:31:21 +0300 Adrian Bunk <bunk@xxxxxxxxxx> wrote:
> >
> > > ~/linux/linux-next $ git bisect start
> > > fatal: ref HEAD is not a symbolic ref
> > > Bad HEAD - I need a symbolic ref
> This would indicate something wrong with your clone of linux-next. How
> did you create the repository?
> > > - how does one bisect on linux-next?
> Any day's linux-next tree is a git tree like any other ...

Hm it can be that I did something wrong but I simply followed advice seen
in one of threads on lkml:

Dmitry: you cannot just "git pull" on linux-next, because each version of
linux-next is independent of the next one. What you should do is basically

# Set this up just once..
git remote add linux-next git://

and then after that, you keep on just doing

git fetch linux-next
git checkout linux-next/master

This is from today:

$ git fetch linux-next
remote: Counting objects: 3749, done.
remote: Compressing objects: 100% (748/748), done.
Indexing 2309 objects...
remote: Total 2309 (delta 1918), reused 1951 (delta 1560)
100% (2309/2309) done
Resolving 1918 deltas...
100% (1918/1918) done
496 objects were added to complete this thin pack.
* refs/remotes/linux-next/history: fast forward to branch 'history' of git:// b26fb88..75f1411
* refs/remotes/linux-next/master: forcing update to non-fast forward branch 'master' of git:// 703d73f...f1d3dea
* refs/remotes/linux-next/stable: fast forward to branch 'stable' of git:// dd28642..7371fd1
Auto-following refs/tags/next-20080516
* refs/tags/next-20080516: storing tag 'next-20080516' of git://
commit: f1d3dea

$ git checkout linux-next/master
HEAD is now at f1d3dea... Add linux-next specific files

$ git bisect start
fatal: ref HEAD is not a symbolic ref
Bad HEAD - I need a symbolic ref
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at