linux-kernel - Re: [PATCH 8/8] x86: I/O APIC: Timer through 8259A second-chance

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.55.0806052002010.2875@cliff.in.clinika.pl>
Date:	Thu, 5 Jun 2008 20:47:44 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Cyrill Gorcunov <gorcunov@...il.com>
cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH 8/8] x86: I/O APIC: Timer through 8259A second-chance

On Thu, 5 Jun 2008, Cyrill Gorcunov wrote:

> Since I've got the same hang by using qemu - i think i could test ;)

 I can reproduce the hang, except with a slightly different options.  I
have spotted the places where the watchdog is set up incorrectly.  I shall
post fixes shortly, once I have got them polished and tested.  Feel free
to throw them at your qemu.

 Also it's worth noting there's more breakage of the NMI watchdog for this
configuration ("maxcpus=1 noapic") -- it fails to tick on the CPU #0 on my
system for some reason, but that's well beyond the scope of this series,
so I am not going to look into it.

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