From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9558] AE_AML_PACKAGE_LIMIT, Evaluating _PSS - Frequency scaling not working after BIOS upgrade on Asus F3jc
Date: Fri, 14 Dec 2007 14:49:34 -0800 (PST) [thread overview]
Message-ID: <20071214224934.68CBA11D108@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-9558-3570@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=9558
len.brown@intel.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acpi-
| |bugzilla@lists.sourceforge.n
| |et
AssignedTo|cpufreq@www.linux.org.uk |venkatesh.pallipadi@intel.co
| |m
Status|NEEDINFO |NEW
Component|cpufreq |Power-Processor
Product|Power Management |ACPI
Summary|Frequency scaling not |AE_AML_PACKAGE_LIMIT,
|working after BIOS upgrade |Evaluating _PSS - Frequency
|on Asus F3jc |scaling not working after
| |BIOS upgrade on Asus F3jc
------- Comment #6 from len.brown@intel.com 2007-12-14 14:49 -------
please attach the output from acpidump.
if possible, it would be great to get it when running
both the new broken BIOS, and again with the old working BIOS.
--
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.
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2007-12-14 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 6:58 [Bug 9558] New: Frequency scaling not working after BIOS upgrade on Asus F3jc bugme-daemon
2007-12-14 7:00 ` [Bug 9558] " bugme-daemon
2007-12-14 7:00 ` bugme-daemon
2007-12-14 7:01 ` bugme-daemon
2007-12-14 8:19 ` bugme-daemon
2007-12-14 8:22 ` bugme-daemon
2007-12-14 9:44 ` bugme-daemon
2007-12-14 22:49 ` bugme-daemon [this message]
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=20071214224934.68CBA11D108@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.