mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Mariusz Kozlowski" <m.kozlowski@tuxland.pl>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"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 10:13:22 +0200	[thread overview]
Message-ID: <19f34abd0805160113i17eea98aub287f2d1be8f05d9@mail.gmail.com> (raw)
In-Reply-To: <200805160737.50373.m.kozlowski@tuxland.pl>

On Fri, May 16, 2008 at 7:37 AM, Mariusz Kozlowski
<m.kozlowski@tuxland.pl> wrote:
> Hello,
>
>> > > > ~/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 ...
>
> and I did :/ I think I just started this repo in wrong way - according to linux-next FAQ.
> I'll just start from scratch then.

You need to be on a branch. If git-branch says this:

$ git branch
* (no branch)

then git will not allow you to bisect:

$ git bisect start v2.6.24 v2.6.25
fatal: ref HEAD is not a symbolic ref
Bad HEAD - I need a symbolic ref

Try first checkout out a new branch:

$ git checkout -b bisect
Switched to a new branch "bisect"

$ git bisect start v2.6.24 v2.6.25
Switched to branch "master"

Good luck!

Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  parent reply	other threads:[~2008-05-16  8:13 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 ` Adrian Bunk
2008-05-16  4:06   ` Stephen Rothwell
2008-05-16  5:17     ` Mariusz Kozlowski
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 [this message]
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=19f34abd0805160113i17eea98aub287f2d1be8f05d9@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.kozlowski@tuxland.pl \
    --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

all inboxes | Powered by JetHome®