linux-kernel - Re: 2.6.22-rc3 nmi watchdog hang

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:	Mon, 18 Jun 2007 16:31:25 +0200
From:	Björn Steinbrink <B.Steinbrink@....de>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: 2.6.22-rc3 nmi watchdog hang

On 2007.06.18 14:11:22 +0200, Ingo Molnar wrote:
> 
> * Björn Steinbrink <B.Steinbrink@....de> wrote:
> 
> > >      [PATCH] i386: Clean up NMI watchdog code
> > > 
> > > Andi - just boot with nmi_watchdog=2 on a dual-core Athlon64 CPU.
> > 
> > I still fail to reproduce this, could you send me your config?
> 
> attached below. nmi_watchdog=2 still hangs as of -rc5, using the 32-bit 
> kernel (at various places during bootup - a typical place is somewhere 
> after cfq_init()). Changing it to nmi_watchdog=0 makes the kernel boot 
> again.

Still no hang here. Just to make sure that I didn't mess the test up,
here's what I did:

Get pristine 2.6.22-rc5 kernel sources.
Put your config in place as .config
Run: make ARCH=i386 CFLAGS_KERNEL="-m32" AFLAGS_KERNEL="-m32"
Install the kernel.
Reboot, pass "nmi_watchdog=2" as kernel parameter.

As your config is for a 64bit kernel, several config items had to be set
manually. In one run, I accepted the default values, in the second run,
I tried to adjust those items to match your 64bit config as good as I
could.

Anything wrong with that?

Björn
-
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/