From: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Adrian Bunk <bunk@kernel.org>,
kernel-testers@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: spontaneous reboots and hangs on x86_64
Date: Fri, 16 May 2008 07:17:31 +0200 [thread overview]
Message-ID: <200805160717.31618.m.kozlowski@tuxland.pl> (raw)
In-Reply-To: <20080516140625.25fac6a2.sfr@canb.auug.org.au>
Hello Stephen,
> On Thu, 15 May 2008 23:31:21 +0300 Adrian Bunk <bunk@kernel.org> 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://git.kernel.org/pub/scm/linux/kernel/git/sfr/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://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next
old..new: b26fb88..75f1411
* refs/remotes/linux-next/master: forcing update to non-fast forward branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next
old...new: 703d73f...f1d3dea
* refs/remotes/linux-next/stable: fast forward to branch 'stable' of git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next
old..new: dd28642..7371fd1
Auto-following refs/tags/next-20080516
* refs/tags/next-20080516: storing tag 'next-20080516' of git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next
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
next prev parent reply other threads:[~2008-05-16 5:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200805152201.49154.m.kozlowski@tuxland.pl>
2008-05-15 20:31 ` spontaneous reboots and hangs on x86_64 Adrian Bunk
2008-05-16 4:06 ` Stephen Rothwell
2008-05-16 5:17 ` Mariusz Kozlowski [this message]
2008-05-16 5:37 ` Mariusz Kozlowski
2008-05-16 7:44 ` Stephen Rothwell
2008-05-16 18:53 ` Mariusz Kozlowski
2008-05-16 20:11 ` Dan Noé
2008-05-17 3:23 ` Stephen Rothwell
2008-05-24 16:11 ` Mariusz Kozlowski
2008-05-16 8:13 ` Vegard Nossum
2008-05-16 18:46 ` Mariusz Kozlowski
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=200805160717.31618.m.kozlowski@tuxland.pl \
--to=m.kozlowski@tuxland.pl \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).