cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9151] Something broke cpufreq on laptop with lid behavior
Date: Sat, 13 Oct 2007 13:06:50 -0700 (PDT)	[thread overview]
Message-ID: <20071013200650.78E8B108010@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-9151-3570@http.bugzilla.kernel.org/>

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





------- Comment #2 from stevenm@umd.edu  2007-10-13 13:06 -------
Created an attachment (id=13148)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=13148&action=view)
Dmesg output with odd behavior and cpufreq.debug=7

There is the debug info. Messages starting with ** are echoed by me into kmsg
so that you can see what I tried to do then. The system was booted up using
battery power and then an AC adapter was attached when indicated. This time it
didn't do any odd things with throttling, but it definitely magically shot up
to 2GHz and wouldn't go to 600MHz unless I set it to 800MHz first. The test was
done in a console environment without any windowing stuff or KDE battery
monitor running. ACPID and laptop_mode were removed from rc.d before the system
was booted with this kernel.


-- 
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:[~2007-10-13 20:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9151-3570@http.bugzilla.kernel.org/>
2007-10-12 18:00 ` [Bug 9151] Something broke cpufreq on laptop with lid behavior bugme-daemon
2007-10-12 18:00 ` bugme-daemon
2007-10-13 20:06 ` bugme-daemon [this message]
2007-11-22 23:41 ` bugme-daemon
2007-12-13 19:03 ` bugme-daemon
2007-12-13 23:10 ` bugme-daemon
2007-12-15  3:38 ` bugme-daemon
2007-12-15  4:51 ` [Bug 9151] Something broke cpufreq on laptop with lid behavior between 2.6.17 and 2.6.23 bugme-daemon
2007-12-15  6:37 ` bugme-daemon
2007-12-15 16:44 ` bugme-daemon
2007-12-18  5:11 ` bugme-daemon
2008-01-23  0:43 ` 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=20071013200650.78E8B108010@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox