linux-kernel - Re: spontaneous reboots and hangs on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 16 May 2008 10:13:22 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Mariusz Kozlowski" <m.kozlowski@...land.pl>
Cc:	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	"Adrian Bunk" <bunk@...nel.org>, kernel-testers@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: spontaneous reboots and hangs on x86_64

On Fri, May 16, 2008 at 7:37 AM, Mariusz Kozlowski
<m.kozlowski@...land.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/