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: <4D96F945.3030101@ahsoftware.de>
Date:	Sat, 02 Apr 2011 12:24:05 +0200
From:	Alexander Holler <holler@...oftware.de>
To:	Carsten Emde <C.Emde@...dl.org>
CC:	Mike Galbraith <efault@....de>, Greg KH <gregkh@...e.de>,
	linux-kernel@...r.kernel.org,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Len Brown <lenb@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Asit Mallick <asit.k.mallick@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Linux 2.6.33.8

Hello,

Am 02.04.2011 11:14, schrieb Carsten Emde:
> model name : Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz
> stepping : 2
>
> This is the situation:
>
> 1. Without commit ea53069231f9317062910d6e772cca4ce93de8c8:
> Everyting is fine. The system correctly powers off.
>
> 2. With commit ea53069231f9317062910d6e772cca4ce93de8c8:
> a) Frequency scaling never enabled (acpi_cpufreq not loaded,
> cpufreq_ondemand not loaded):
> Everything is fine. The system correctly powers off.
> b) Frequency scaling enabled (acpi_cpufreq loaded, cpufreq_ondemand
> loaded) or
> c) Frequency scaling enabled and disabled (acpi_cpufreq still loaded
> since it cannot be removed easily, cpufreq_ondemand no longer
> loaded) or
> d) Frequency scaling enabled and disabled (acpi_cpufreq unloaded
> with force, cpufreq_ondemand no longer loaded):
> Not powering off, message:
> ACPI: Preparing to enter system sleep state S5
> Disabling non-boot CPUs ...

I'm using a

model name      : Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz

and can confirm some problem with power down, at least in 2.6.38.2. 
Sometimes I only see the powerdown message but the machine will stay on 
(and the fan starts getting louder).

But in contrast to the above description (that commit seems to have been 
already included in 2.6.37), I never had a problem with powerdown with a 
kernel <2.6.38.
I have CONFIG_X86_ACPI_CPUFREQ enabled, but I currently can't offer much 
more insights, because I haven't tried to analyze that problem. The 
problem doesn't appear with any shutdown, and I don't know (and can't 
remember) if that already happened with 2.6.38.

Besides switching from BKL to non-BKL, I haven't changed the config when 
I've switched from 2.6.37.x to 2.6.38 (other than what make oldconfig does).

Maybe it's a totally unrelated problem, but I thought it might be good 
to mention that I'm having a problem with powerdown in 2.6.38 too.

Regards,

Alexander Holler
--
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