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]

Message-ID: <alpine.LNX.2.00.0908282345150.18588@fgnss.gnfx.tqn.cy>
Date:	Fri, 28 Aug 2009 23:46:35 +0200 (CEST)
From:	Pawel Golaszewski <blues@....pl>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Dhaval Giani <dhaval.giani@...il.com>
Subject: Re: PROBLEM: oops

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?

-- 
pozdr.  Paweł Gołaszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.