linux-kernel - Re: [1/6] 2.6.21-rc4: known regressions

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: <1174650969.10840.274.camel@localhost.localdomain>
Date:	Fri, 23 Mar 2007 12:56:08 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Mingming Cao <cmm@...ibm.com>, Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Mariusz Kozlowski <m.kozlowski@...land.pl>,
	Oliver Pinter <oliver.pntr@...il.com>,
	Sid Boyce <g3vbv@...eyonder.co.uk>,
	Nick Piggin <npiggin@...e.de>,
	Jens Axboe <jens.axboe@...cle.com>,
	Thomas Renninger <trenn@...e.de>,
	Len Brown <len.brown@...el.com>
Subject: Re: [1/6] 2.6.21-rc4: known regressions

On Fri, 2007-03-23 at 12:42 +0100, Ingo Molnar wrote:
> there's a new post-rc4 regression: my T60 hangs during early bootup. I 
> bisected the hang down to this recent commit:
> 
> | commit 25496caec111481161e7f06bbfa12a533c43cc6f
> | Author: Thomas Renninger <trenn@...e.de>
> | Date:   Tue Feb 27 12:13:00 2007 -0500
> |
> |    ACPI: Only use IPI on known broken machines (AMD, Dothan/BaniasPentium M)
> 
> undoing this change fixes my T60 so it correctly boots again.
> 
> the commit has this confidence-raising comment:
> 
> |   However, I am not sure about the naming of the parameter and how it 
> |   could/should get integrated into the dyntick part 
> |   (CONFIG_GENERIC_CLOCKEVENTS). There, a more fine grained check (TSC 
> |   still running?, ..) is needed?
> 
> could we please revert this commit until it's done correctly?
> 
> and did this end up being a 'fix'? The change weakens the scope of a 
> hardware workaround, which IMO has no place so late in the cycle. At a 
> minimum the clockevents maintainer (Thomas) should have been Cc:-ed on 
> it.

Ingo, 

I had seen it before, and I had no objections under the premise, that it
does not break things and especially survives on Andrews VAIO. I
expected that to come in via -mm so it gets enough testing.

We should revert that patch and add a "trust_lapic_timer_in_c2"
commandline option instead. So we are on the safe side.

	tglx


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