linux-kernel - Re: 2.6.18 Nasty 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: <1159301752.17071.0.camel@localhost>
Date:	Tue, 26 Sep 2006 13:15:51 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Greg Schafer <gschafer@....com.au>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.18 Nasty Lockup

On Tue, 2006-09-26 at 22:36 +1000, Greg Schafer wrote:
> Hi
> 
> This is a _hard_ lockup. No oops, no magic sysrq, no nuthin, just a
> completely dead machine with only option the reset button. Usually happens
> within a couple of minutes of desktop use but is 100% reproducible. Problem
> is still there in a fresh checkout of current Linus git tree (post 2.6.18).
> 
> Dual Athlon-MP 2200's on a Tyan S2466 Tiger MPX. Config attached.
> 
> I used git-bisect and arrived at the apparent culprit below. Anything else I
> should do to gather more info?

Quick test: Does enabling CONFIG_ACPI change the behavior?

thanks
-john


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