linux-kernel - Re: PROBLEM: oops

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:	Sat, 29 Aug 2009 09:11:32 -0400
From:	Eric Paris <eparis@...isplace.org>
To:	Pawel Golaszewski <blues@....pl>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Dhaval Giani <dhaval.giani@...il.com>
Subject: Re: PROBLEM: oops

On Fri, Aug 28, 2009 at 5:46 PM, Pawel Golaszewski<blues@....pl> wrote:
> On Thu, 27 Aug 2009, Peter Zijlstra wrote:
>> > > > # git log --format=oneline v2.6.27.13..v2.6.27.31 kernel/sched*
>> > > > 2b46f3769896dc04e1e49144d282e4655677105a wait: prevent exclusive waiter starvation
>> > > >
>> > > > Nothing changed anywhere near the code that is falling apart..
>> > > I have 2 machines with the same hardware and similar software. On
>> > > one .13 is stable - I will test it on the second one. Should be too.
>> > I've checked it - 2.6.27.13 is stable for me. Conclusion: there is
>> > something wrong between 2.6.27.13 and 2.6.27.31 What can I do about
>> > that? I'm not kernel-hacker...
>> Unless any of the memory debugging options yield a clue the best you can
>> do is a bisection I'm afraid.
>>
>> # git log --format=oneline v2.6.27.13..v2.6.27.31 | wc -l
>> 630
>
> Ok, I checked:
>
> 2.6.27.15 works fine
> 2.6.27.17 crashes (log was sent).
>
> What now?

Have you ever used git, and especially git-bisect?  That's what would
really help to run it down.  Try this operation.

git clone git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-allstable.git
stable-tree
cd stable-tree
git bisect start
git bisect bad v2.6.27.17
git bisect good v2.6.27.15

(a)
[git will do some work and will leave you with a message that says
something like "Bisecting: 675 revisions left to test after this"]
build the kernel tree.
test your build.

if it works go back to the stable-tree directory and enter:
git bisect good

if that kernel fails enter:
git bisect bad

goto (a)

Eventually there will be no more revisions left to bisect, and you
will have been left with the first bad kernel revision in
"refs/bisect/bad".

Let us know what this patch is that broke it for you.

Thanks!
--
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/