All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10564] Randomly sets max freq equal to min freq
Date: Wed, 30 Apr 2008 03:29:35 -0700 (PDT)	[thread overview]
Message-ID: <20080430102935.BA3EF108061@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-10564-3570@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=10564





------- Comment #8 from trenn@suse.de  2008-04-30 03:29 -------
commit e56a727b023d40d1adf660168883f30f2e6abe0a
Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Date:   Mon Apr 28 15:13:43 2008 -0400

    [CPUFREQ] Make acpi-cpufreq more robust against BIOS freq changes behind
our back.

If this does not help, I wonder whether ignore_ppc=1 as processor module
parameter helps?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-04-30 10:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 16:11 [Bug 10564] New: Randomly sets max freq equal to min freq bugme-daemon
2008-04-27 16:35 ` [Bug 10564] " bugme-daemon
2008-04-27 17:10 ` bugme-daemon
2008-04-27 17:14 ` bugme-daemon
2008-04-27 17:30 ` bugme-daemon
2008-04-27 17:39 ` bugme-daemon
2008-04-27 18:35 ` bugme-daemon
2008-04-27 18:38 ` bugme-daemon
2008-04-28 15:26 ` bugme-daemon
2008-04-28 18:54 ` bugme-daemon
2008-04-30 10:29 ` bugme-daemon [this message]
2008-05-03 14:41 ` bugme-daemon
2008-05-03 15:13 ` bugme-daemon
2008-05-03 16:50 ` bugme-daemon

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=20080430102935.BA3EF108061@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=cpufreq@www.linux.org.uk \
    /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.