linux-kernel - Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

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: <200611061643.14217.christiand59@web.de>
Date:	Mon, 6 Nov 2006 16:43:13 +0100
From:	Christian <christiand59@....de>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Dave Jones <davej@...hat.com>,
	Alexey Starikovskiy <alexey_y_starikovskiy@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org
Subject: Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)

Am Montag, 6. November 2006 07:00 schrieb Adrian Bunk:
> On Sun, Nov 05, 2006 at 06:32:12PM +0100, Christian wrote:
> > Am Freitag, 3. November 2006 16:56 schrieb Dave Jones:
> > > On Fri, Nov 03, 2006 at 11:25:37AM +0300, Alexey Starikovskiy wrote:
> > >  > Could this be a problem?
> > >  > --------------------
> > >  > ...
> > >  > CONFIG_ACPI_PROCESSOR=m
> > >  > ...
> > >  > CONFIG_X86_POWERNOW_K8=y
> > >
> > > Hmm, possibly.  Christian, does it work again if you set them both to
> > > =y ?
> >
> > Yes, it works now! Only the change to CONFIG_ACPI_PROCESSOR=y made it
> > work again!
>
> You said 2.6.18 worked for you.
>
> Did you have CONFIG_ACPI_PROCESSOR=y in 2.6.18, or did
> CONFIG_ACPI_PROCESSOR=m, CONFIG_X86_POWERNOW_K8=y work for you in 2.6.18?

It worked with CONFIG_ACPI_PROCESSOR=m in 2.6.18-rc7. Since 2.6.19-rc1 it 
doesn't work anymore with CONFIG_ACPI_PROCESSOR=m.

user@...ntu:~/Projekte/linux-2.6.18-rc7$ uname -a
Linux ubuntu.localnet 2.6.18-rc7 #2 SMP Wed Sep 13 11:28:41 CEST 2006 x86_64 
GNU/Linux

user@...ntu:~/Projekte/linux-2.6.18-rc7$ lsmod | grep -Ei "processor|acpi|
power"
powernow_k8            16096  1
freq_table              6848  2 powernow_k8,cpufreq_stats
cpufreq_powersave       3584  0
asus_acpi              20644  0
processor              36872  2 powernow_k8,thermal


user@...ntu:~/Projekte/linux-2.6.18-rc7$ grep -i 
ACPI_PROCESSOR /boot/config-2.6.18-rc7
CONFIG_ACPI_PROCESSOR=m

user@...ntu:~/Projekte/linux-2.6.18-rc7$ 
grep -Ei "POWERNOW_K8" /boot/config-2.6.18-rc7
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_POWERNOW_K8_ACPI=y

+++ There's a difference in 2.6.19! CONFIG_X86_POWERNOW_K8_ACPI is gone +++

user@...ntu:~/Projekte/linux-2.6.18-rc7$ 
grep -Ei "POWERNOW_K8" /boot/config-2.6.19-rc1
CONFIG_X86_POWERNOW_K8=y

user@...ntu:~/Projekte/linux-2.6.18-rc7$ grep -Ei "CPUFREQ|
CPU_FREQ" /boot/config-2.6.18-rc7
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
# CPUFreq processor drivers
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set

-Christian

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