linux-kernel - RE: Linux 2.6.27-rc3

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Aug 2008 15:23:09 -0500
From:	"Langsdorf, Mark" <mark.langsdorf@....com>
To:	"Torsten Kaiser" <just.for.lkml@...glemail.com>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
CC:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: RE: Linux 2.6.27-rc3

> On Wed, Aug 13, 2008 at 4:33 AM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> > Things really _have_ calmed down, and hopefully we've also 
> resolved a lot
> > of the regressions in -rc3.
> 
> I found a new one in -rc3 vs. -rc2.
> Only one of my cpus seems to powered down by cpufreq, because the
> topology gets filled out wrong:
> 
> correct with -rc2:
> #grep . /sys/devices/system/cpu/cpu*/cpufreq/affected_cpus
> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0 1
> /sys/devices/system/cpu/cpu1/cpufreq/affected_cpus:0 1
> /sys/devices/system/cpu/cpu2/cpufreq/affected_cpus:2 3
> /sys/devices/system/cpu/cpu3/cpufreq/affected_cpus:2 3
> (The system has 2 dual core Opterons)
> 
> wrong with -rc3:
> #grep . /sys/devices/system/cpu/cpu*/cpufreq/affected_cpus
> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0 1
> /sys/devices/system/cpu/cpu1/cpufreq/affected_cpus:0 1
> /sys/devices/system/cpu/cpu2/cpufreq/affected_cpus:0 1
> /sys/devices/system/cpu/cpu3/cpufreq/affected_cpus:0 1
> 
> I bisected this bug down to these commits:
> > Mark Langsdorf (2):
> >      [CPUFREQ][1/2] whitespace fix for powernow-k8
> >      [CPUFREQ][2/2] preregister support for powernow-k8

Well, that patch is likely going to get reverted because
it's causing a crash on Rafael's test box.

But before that happens, could you send me the disassembled
dump of your ACPI objects?  Iti's possible the code is wrong,
but it's also possible that your BIOS is passing a broken
_PSD.

-Mark Langsdorf
Operating System Research Center
AMD

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