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, 6 Oct 2008 22:39:25 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Len Brown <lenb@...nel.org>,
	Jason Vas Dias <jason.vas.dias@...il.com>
Subject: Re: [PATCH] x86 ACPI: Blacklist two HP machines with buggy BIOSes
 (Re: 2.6.27-rc8+ - first impressions)

On Mon, 6 Oct 2008, Andi Kleen wrote:

> The real reason is actually a workaround in the BIOS for problems
> in the older Linux code that caused duplicated timer interrupts. The
> old Linux would fall into "enable both IO-APIC and 8259" fallback mode
> and the resulted in duplicated timer events, which made everything unhappy.
> They instead configured the northbridge in a way that one of the inputs
> is ignored.

 Hmm, working around Linux problems in the BIOS is a new and truly odd 
concept to me.  It's not that we are unresponsive or do not take 
responsibility for our bugs, is it?

> You won't be able to DMI list it, that workaround is widely used
> in lots of different systems.

 Well, perhaps, but the thermal trip point phenomenon seems unique to this 
family of systems.  The other aspects of the problem do not really matter 
anymore as we seem to have addressed them robustly enough now.

  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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ