All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: S K <nospamnoham@gmail.com>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	Zhao Yakui <yakui.zhao@intel.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Sat, 9 Aug 2008 21:30:14 +0200	[thread overview]
Message-ID: <200808092130.14719.trenn@suse.de> (raw)
In-Reply-To: <200808092059.47863.trenn@suse.de>

Hi,

just that in case you try out kernels...

On Saturday 09 August 2008 08:59:47 pm Thomas Renninger wrote:
> On Friday 08 August 2008 08:23:25 pm S K wrote:

> Mark Langsdorf reported some acpi breakage in .27-rc1, this could also be
> the reason.
---------
> I got a regression when updated from 2.6.27-rc1 ro
> 2.6.27-rc2.  The noticeable symptom is the powernow-k8
> driver stopped working because the call to 
> acpi_processor_register_performance() is returning
> -EINVAL.
----------

So it's rc2 not rc1, but AFAIK your report should be older than rc2.

There also was a similar report from Laurence Darby <ldarby@tuffmail.com>.
He still posted on the old cpufreq list.
Subject: Core 2 Duo E8400 stepping 6 not recognised

A BIOS update helped.
You may be able to google this out and compare his CPU_FREQ_DEBUG logs.

      Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Renninger <trenn@suse.de>
To: "S K" <nospamnoham@gmail.com>
Cc: "Alan Jenkins" <alan-jenkins@tuffmail.co.uk>,
	"Zhao Yakui" <yakui.zhao@intel.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Sat, 9 Aug 2008 21:30:14 +0200	[thread overview]
Message-ID: <200808092130.14719.trenn@suse.de> (raw)
In-Reply-To: <200808092059.47863.trenn@suse.de>

Hi,

just that in case you try out kernels...

On Saturday 09 August 2008 08:59:47 pm Thomas Renninger wrote:
> On Friday 08 August 2008 08:23:25 pm S K wrote:

> Mark Langsdorf reported some acpi breakage in .27-rc1, this could also be
> the reason.
---------
> I got a regression when updated from 2.6.27-rc1 ro
> 2.6.27-rc2.  The noticeable symptom is the powernow-k8
> driver stopped working because the call to 
> acpi_processor_register_performance() is returning
> -EINVAL.
----------

So it's rc2 not rc1, but AFAIK your report should be older than rc2.

There also was a similar report from Laurence Darby <ldarby@tuffmail.com>.
He still posted on the old cpufreq list.
Subject: Core 2 Duo E8400 stepping 6 not recognised

A BIOS update helped.
You may be able to google this out and compare his CPU_FREQ_DEBUG logs.

      Thomas

  reply	other threads:[~2008-08-09 19:13 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 10:00 cpufreq doesn't seem to work in Intel Q9300 S K
2008-08-03 10:31 ` none
2008-08-04  5:06   ` S K
2008-08-07  9:35     ` S K
2008-08-07 19:24       ` Alan Jenkins
2008-08-08  1:32       ` Zhao Yakui
2008-08-08  4:53         ` S K
2008-08-08  8:41           ` Alan Jenkins
2008-08-08 10:10             ` S K
2008-08-08 10:43               ` S K
2008-08-08 12:30                 ` Thomas Renninger
2008-08-08 18:23                   ` S K
2008-08-09 18:59                     ` Thomas Renninger
2008-08-09 18:59                       ` Thomas Renninger
2008-08-09 19:30                       ` Thomas Renninger [this message]
2008-08-09 19:30                         ` Thomas Renninger
2008-08-10  8:28                       ` S K
2008-08-11  1:33                         ` Zhao Yakui
2008-08-11  4:44                           ` S K
2008-08-11  5:24                             ` Zhao Yakui
2008-08-11  5:24                               ` S K
2008-08-11  7:00                                 ` Alan Cox
2008-08-11 10:55                               ` Andi Kleen
2008-08-11 13:15                                 ` S K
2008-08-11 13:23                                   ` Andi Kleen
2008-08-12  5:43                                     ` S K
2008-08-11 11:22                             ` Arjan van de Ven
2008-08-11 11:38                               ` Alexey Dobriyan
2008-08-11 11:53                                 ` Matthew Garrett
2008-08-11 14:02                               ` Adrian Bunk
2008-08-11 14:07                                 ` Matthew Garrett
2008-08-11 14:12                                   ` Arjan van de Ven
2008-08-11 14:11                                 ` Arjan van de Ven
2008-08-11 16:03                                   ` Adrian Bunk
2008-08-11 16:20                                     ` Arjan van de Ven
2008-08-11 16:28                                       ` Adrian Bunk
2008-08-11 16:44                                         ` Arjan van de Ven
2008-08-12 19:27                                           ` Adrian Bunk
2008-08-11 19:33                                   ` Dominik Brodowski
2008-08-11 23:58                                     ` Arjan van de Ven
2008-08-12 19:03                                       ` Dominik Brodowski
2008-08-12 19:59                                         ` Arjan van de Ven

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=200808092130.14719.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nospamnoham@gmail.com \
    --cc=yakui.zhao@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.