linux-kernel - Re: How to go about debuging a system lockup?

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: <m3irhda74j.fsf@defiant.localdomain>
Date:	Sat, 18 Nov 2006 02:14:20 +0100
From:	Krzysztof Halasa <khc@...waw.pl>
To:	"Jesper Juhl" <jesper.juhl@...il.com>
Cc:	"Lennart Sorensen" <lsorense@...lub.uwaterloo.ca>,
	linux-kernel@...r.kernel.org
Subject: Re: How to go about debuging a system lockup?

"Jesper Juhl" <jesper.juhl@...il.com> writes:

> Or just try a few random older 2.6 kernels like 2.6.14, 2.6.9,
> 2.6.whatever (of course it needs to be a version that git knows
> about).

One can also do "bisect" manually, works with all kernels.
-- 
Krzysztof Halasa
-
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/