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]

Date:	Tue, 26 Sep 2006 15:50:57 -0700
From:	john stultz <johnstul@...ibm.com>
To:	caglar@...dus.org.tr
Cc:	Greg Schafer <gschafer@....com.au>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.18 Nasty Lockup

On Wed, 2006-09-27 at 00:15 +0300, S.Çağlar Onur wrote:
> 26 Eyl 2006 Sal 15:36 tarihinde, Greg Schafer şunları yazmıştı: 
> > 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).
> 
> Same symptoms here and its reproducible after starting the irqbalance (0.12 or 
> 0.13), if i disable irqbalance then everything is going fine.

Hmm.. Not sure about the connection to irqbalance. You're using the TSC
clocksource, so I'm curious if your cpu TSC's are out of sync. Can you
boot w/ "clocksource=acpi_pm" to see if that resolves it?

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/