linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Dave Jones <davej@codemonkey.org.uk>,
	cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: cpufreq longhaul locks up
Date: Fri, 04 May 2007 13:42:47 -0400	[thread overview]
Message-ID: <463B7097.7070300@redhat.com> (raw)
In-Reply-To: <463B687D.1020600@interia.pl>

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 <rafalbilski@interia.pl>
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 <rafalbilski@interia.pl>
Signed-off-by: Dave Jones <davej@redhat.com>
---

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]";


  reply	other threads:[~2007-05-04 17:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 10:16 cpufreq longhaul locks up Jan Engelhardt
     [not found] ` <5699f8f00705040436u63c5ab38g1054001eccc596e7@mail.gmail.com>
2007-05-04 11:51   ` Jan Engelhardt
2007-05-04 17:08 ` Rafał Bilski
2007-05-04 17:42   ` Chuck Ebbert [this message]
2007-05-04 18:40     ` Rafał Bilski
2007-05-04 18:48   ` Jan Engelhardt
2007-05-04 20:11     ` Rafał Bilski
2007-05-04 21:03       ` Jan Engelhardt
     [not found]   ` <5699f8f00705041108t67425997w42e6268f9076abc9@mail.gmail.com>
2007-05-04 19:00     ` Rafał Bilski
2007-05-04 20:37 ` john stultz
2007-05-04 21:02   ` Jan Engelhardt
2007-05-04 22:49     ` john stultz
2007-05-04 23:32       ` Jan Engelhardt
2007-05-05  4:03         ` Rafał Bilski
2007-05-05  8:00           ` Jan Engelhardt
2007-05-05 13:58             ` Rafał Bilski
2007-05-05 18:13               ` Jan Engelhardt
2007-05-04 22:20 ` David Johnson
2007-05-04 23:37   ` Jan Engelhardt
2007-05-05  5:40     ` Rafał Bilski
2007-05-05  9:37       ` Jan Engelhardt
2007-05-05 14:10         ` Rafał Bilski
2007-05-05 17:38           ` Jan Engelhardt
2007-05-05 18:04             ` Rafał Bilski
2007-05-05 18:23               ` Jan Engelhardt
     [not found]       ` <5699f8f00705050144s5c00a455s8f7dba9258d83986@mail.gmail.com>
2007-05-05 14:02         ` Rafał Bilski
2007-05-05 17:48         ` Rafał Bilski
2007-05-05 18:42           ` Jan Engelhardt
2007-05-05 19:58             ` Rafał Bilski
2007-05-05 20:30               ` Jan Engelhardt
2007-05-05 20:50               ` Jan Engelhardt
2007-05-05 21:32                 ` Rafał Bilski
2007-05-06  7:53                   ` Jan Engelhardt
2007-05-06  5:12                 ` Rafał Bilski
2007-05-06  8:03                   ` Jan Engelhardt
2007-05-06  9:23                     ` Rafał Bilski
2007-05-06  9:32                       ` Jan Engelhardt
2007-05-06 10:25                         ` Rafał Bilski
2007-05-06 11:33                           ` Jan Engelhardt
2007-05-06 12:20                             ` Rafał Bilski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=463B7097.7070300@redhat.com \
    --to=cebbert@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafalbilski@interia.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).