linux-kernel - Re: cpufreq longhaul locks up

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]

Date:	Sat, 5 May 2007 20:42:18 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Rafał Bilski <rafalbilski@...eria.pl>
cc:	Wander Winkelhorst <w.winkelhorst@...il.com>,
	David Johnson <dj@...id-web.co.uk>,
	linux-kernel@...r.kernel.org, cpufreq@...ts.linux.org.uk
Subject: Re: cpufreq longhaul locks up


On May 5 2007 19:48, Rafał Bilski wrote:
>
>I found one line which wasn't were it should be. Probably this will not 
>fix Your problem with powersave governor, but it is a bit related. 
>Looks like Longhaul isn't skipping frequency transtition when it is asked 
>to set f which is already set. Now after first transition it will not 
>try to set same frequency again. Second part contains some magic 
>because I don't have CN400 datasheet. It is NDA protected :-( Should 
>print You one byte in hex and will try to set one register. I don't 
>know if anything will change but it is worth testing.

Did not help unfortunately. The output the printk line generated was
  longhaul: 0x0

(Strangely enough, %#02x with glibc outputs "00", not "0x0".
And I would have expected "0x00". Subtleties of the kernel 
printk/glibc?)



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