linux-kernel - Re: system gets stuck in a lock during boot

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: <20090825085919.GB14003@elte.hu>
Date:	Tue, 25 Aug 2009 10:59:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Justin Mattock <justinmattock@...il.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Li Zefan <lizf@...fujitsu.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: system gets stuck in a lock during boot

* Justin Mattock <justinmattock@...il.com> wrote:

> O.K. I feel better, deleted
> my system, and threw in a minimal built system
> with only the bare essentials to boot.
> (just to make sure things are correct).
> 
> unfortunately after building rc6 I'm still hitting
> this. really am not sure why this is happening.

Could you please double-check the bisection result by doing this:

 git revert af6af30c0f

on the latest kernel and seeing whether that fixes the lockup?

Bisections are very efficient and hence very sensitive as well to 
minimal errors. Just one small mistake near the end of a bisection 
can blame the wrong commit.

So the best way to double-check such 100%-triggerable crashes is to 
do the revert. I tried the revert and it can be done fine here.

[ _If_ that does not fix the bug then to save time you can 
   'backtrack' the bisection, instead of re-doing it completely. 
   I.e. you have your bisection log, re-check the final steps going 
   backwards. Once you find a discrepancy (i.e. a 'bad' point that 
   is 'good' or the other way around), redo the bisection log 
   commands up to that point and continue it up to the end. ]

	Ingo
--
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/