Rafał Bilski wrote:
>> Hi,
> Hello all
>> I found that setting the cpufreq governor to ondemand making the box
>> lock up solid in 2.6.20.2 and 2.6.21 after a few seconds.
>> [...]
>
> I can't explain this. Some motherboards are running fine, some don't.
> I'm running longhaul too. It is working fine. No lockups at all.
> So far I heard only about one Epia which had problems with longhaul.
> It was almost like my Epia but older.
> What is possible:
> - some chipsets revisions are broken and aren't blocking DMA,
> - special setup is required, some versions of BIOS are doing
> necessary things, some don't,
> - some chipsets revisions are broken and drivers are not aware. At
> the beginning Unichrome driver was causing lockups on my machine, but
> Openchrome was fine. Longhaul may trigger, somehow, other hardware bug.
>
The below is in the cpufreq git tree.
(Maybe also ondemand needs to be disabled for Longhaul?)
From: Rafal Bilski <[email protected]>
Date: Sun, 22 Apr 2007 10:26:04 +0000 (+0200)
Subject: [CPUFREQ] Longhaul - Revert Longhaul ver. 2
X-Git-Url: http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fdavej%2Fcpufreq.git;a=commitdiff_plain;h=07844252ffd81ec192a62014bada1016c9703765
[CPUFREQ] Longhaul - Revert Longhaul ver. 2
There is something wrong with this code. It needs more
testing. It is better to disable it for now because support
for some machines will be broken.
Signed-off-by: Rafal Bilski <[email protected]>
Signed-off-by: Dave Jones <[email protected]>
---
diff --git a/arch/i386/kernel/cpu/cpufreq/longhaul.c b/arch/i386/kernel/cpu/cpufreq/longhaul.c
index e5fee72..a3df9c0 100644
--- a/arch/i386/kernel/cpu/cpufreq/longhaul.c
+++ b/arch/i386/kernel/cpu/cpufreq/longhaul.c
@@ -683,7 +683,7 @@ static int __init longhaul_cpu_init(struct cpufreq_policy *policy)
sizeof(samuel2_eblcr));
break;
case 1 ... 15:
- longhaul_version = TYPE_LONGHAUL_V2;
+ longhaul_version = TYPE_LONGHAUL_V1;
if (c->x86_mask < 8) {
cpu_model = CPU_SAMUEL2;
cpuname = "C3 'Samuel 2' [C5B]";
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
