| 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
| ||
|
Message-ID: <CPSMTPM-CMT106gqGng00022093@CPSMTPM-CMT106.kpnxchange.com> Date: Mon, 13 Feb 2012 17:45:34 +0100 From: "N. Coesel" <nico@...dev.nl> To: Dave Jones <davej@...hat.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Cpufreq shutdown patch (kernel 2.6.35.3) Dave, At 17:28 13-2-2012, Dave Jones wrote: >On Thu, Jan 19, 2012 at 10:18:10PM +0100, N. Coesel wrote: > > > I've found a problem in drivers/cpufreq/cpufreq.c. The driver does > > not execute the exit member of the low level driver when shutting > > down for a reboot (reset). This potentially leaves the power supply > > at a too low voltage to boot the system properly. The patch below > > adds a shutdown function which executes the exit member of the low > > level driver which allows a system to be properly prepared for a reset. > >I'm curious what hardware you saw this problem on ? This was on an IMX51 embedded platform but I'm quite sure the same problem can occur on other platforms as well. There has to be some way to allow an orderly shutdown of the low level cpufreq system without a cold reset. Nico Coesel o---------------------------------------------------------------o | N C T Developments | |Innovative embedded solutions | o---------------------------------------------------------------o -- 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