linux-kernel - Re: 2.6.18-rt1

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: <20061013221624.GD7477@in.ibm.com>
Date:	Sat, 14 Oct 2006 03:46:24 +0530
From:	Dipankar Sarma <dipankar@...ibm.com>
To:	Lee Revell <rlrevell@...-job.com>
Cc:	Karsten Wiese <annabellesgarden@...oo.de>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	John Stultz <johnstul@...ibm.com>,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: 2.6.18-rt1

On Fri, Oct 13, 2006 at 06:12:16PM -0400, Lee Revell wrote:
> On Sat, 2006-10-14 at 02:54 +0530, Dipankar Sarma wrote:
> > Can you try with nmi_watchdog=0 in the kernel command line ?
> > 
> > Paul has an NMI-safe patch for rcupreempt which I am adopting
> > and testing at the moment. If this works well, I will publish
> > a new patchset.
> > 
> 
> The bug is too hard to hit for me to provide useful feedback.  I've only
> seen it once since my original report.
> 
> FWIW, I am also seeing hard lockups every 12-24 hours but the box is
> headless and I don't have the bandwidth to debug these further.  It was
> stable with 2.6.17-rt*.

Can you try whatever you were doing with nmi_watchdog=0 ? If it is
stable, then that would explain the problem. I believe Andi enabled
nmi watchdog on x86_64 by default recently, that might be why
we are seeing it now.

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