linux-kernel - Re: speedstep-centrino broke

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: <Pine.LNX.4.62.0609142105010.11604@diedas.soften.ktu.lt>
Date:	Thu, 14 Sep 2006 22:42:44 +0300 (EEST)
From:	Almonas Petrasevicius <draugaz@...das.soften.ktu.lt>
To:	Ben B <kernel@...cactii.net>
Cc:	linux-kernel@...r.kernel.org, venkatesh.pallipadi@...el.com,
	davej@...emonkey.org.uk
Subject: Re: speedstep-centrino broke

On Thu, 14 Sep 2006, Ben B wrote:

>> I did verify both kernels 2.6.16 and 2.6.17 (both vanilla), there is
>> _no_ difference, both have the same speedstep problem.
>
> At the suggestion of Venki, I opened a bugzilla ticket on it:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=7157
>
> And the lowdown is that it seems the newer BIOS no longer exports the
> correct ACPI symbols which are required for speedstep, thus no longer
> supporting it (at least via the official methods). Hence it seems not a
> Linux kernel bug.

Could be. But I am still somehow puzzled, since neither of the 
previous versions (F04 & F06 in my case) contain any reference to the 
mentioned methods (_PSS & _PCT). But those versions were speedsteping just 
fine. 
Or maybe I don't know how to look.
Could You dump your "working" ACPI table and look for those two methods?

Regretfully I don't know much about the ACPI and ASL. It seems like a 
perfect occasion to get myself familiar with it.

> I opened a support ticket with HP, hopefully they address the issue. In

I am not holding my breath unless You know some magic word :)
Btw, that another OS is speedsteping just fine (or pretends doing so).

> the meantime I rolled back my bios and have cpufreq working again.
> Interesting that you also see the problem on an nc6320, it could be that
> they use the same BIOS codebase for various models.

But of course. I suspect, that aside from the physical layout it is 
basically the same hardware.

Regards,
Almonas
-
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/