linux-kernel - Re: 2.6.23-rc7-mm1

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: <1190665512.4035.247.camel@chaos>
Date:	Mon, 24 Sep 2007 22:25:12 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Torsten Kaiser <just.for.lkml@...glemail.com>,
	linux-kernel@...r.kernel.org, Len Brown <lenb@...nel.org>
Subject: Re: 2.6.23-rc7-mm1

On Mon, 2007-09-24 at 12:34 -0700, Andrew Morton wrote:
> > It prints twice 'System halted' and blinks the keyboard leds, but does
> > not switch off. On all other kernel version I only see one keyboard
> > blink before the power goes out.
> 
> ok...
> 
> > I compared its dmesg to vanilla-rc7 and -rc4-mm1, but expect that rc-4
> > assigns different IRQs I can't see any differences except the normal
> > variation in BogoMips etc.

Can your check whether 2.6.23-rc7 +
http://tglx.de/projects/hrtimers/2.6.23-rc7/patch-2.6.23-rc7-hrt1.patch

works for you ?

> hm, dunno.  The only substantial patch which touches
> arch/x86_64/kernel/process.c (which is where cpu_idle lives) is
> x86_64-prep-idle-loop-for-dynticks.patch.
> 
> The problem is, 2.6.23-rc6-mm1's git-acpi patch had all the new cpuidle
> code in it.  Len dropped all that code over the weekend (which is when I
> picked this copy of his tree), so 2.6.23-rc7-mm1 doesn't have the cpuidle
> code.  Len will be reapplying the cpuidle patches today(ish) so next -mm
> _will_ have the cpuidle code.
> 
> So what we have in rc7-mm1 is this transient no-cpuidle state.  It could be
> that the x86_64 dynticks code (which was developed previously tested in
> conjunction with the cpuidle patches) has some dependency on cpuidle.

It should not. cpuidle makes use of dynticks not the other way round.

	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/