From: John Belmonte <john@neggie.net>
To: cpufreq@lists.linux.org.uk
Subject: powernow-k8 and stuck change-pending bit
Date: Sat, 04 Jun 2005 16:32:15 -0400 [thread overview]
Message-ID: <42A20FCF.4070904@neggie.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
I'm having a problem with powernow-k8 intermittent failures and would
appreciate some help.
system:
* Athlon 64 2800+, stepping 10
* Chaintech K8M800 socket 754 (no Cool'n'Quiet support)
* linux-2.6.12-rc5 (+ powernow-k8 1.40.2 patch)
symptoms:
After working fine for a while (several minutes to several hours),
cpufreq seems to get into a bad state where:
* change pending bit set / stuck kernel messages appear
* cat of /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
hangs for a few seconds and finally returns "<unknown>". However a cat
of /proc/cpuinfo works and seems to show the correct cpu MHz.
* reloading powernow-k8 module fails, with "change pending bit stuck"
* the problem can sometimes be provoked by stopping and starting
powernowd
Attached is some kernel output with "cpufreq.debug=3". The debug output
doesn't seem to provide much information at the point of failure.
--John
[-- Attachment #2: powernow-k8_stuck_bit.log --]
[-- Type: text/x-log, Size: 4208 bytes --]
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.40.2)
cpufreq-core: trying to register driver powernow-k8
cpufreq-core: adding CPU 0
powernow-k8: 0 : fid 0xa, vid 0x2
powernow-k8: 1 : fid 0x2, vid 0x12
powernow-k8: 2 : fid 0x3f, vid 0x1f
powernow-k8: invalid freq 7100000 kHz, ignoring
powernow-k8: 3 : fid 0x3f, vid 0x1f
powernow-k8: invalid freq 7100000 kHz, ignoring
powernow-k8: 4 : fid 0x3f, vid 0x1f
powernow-k8: invalid freq 7100000 kHz, ignoring
powernow-k8: 0 : fid 0xa (1800 MHz), vid 0x2 (1500 mV)
powernow-k8: 1 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
powernow-k8: cpu0, init lo 0x20a, hi 0x1
powernow-k8: policy current frequency 1800000 kHz
freq-table: table entry 0: 1800000 kHz, 522 index
freq-table: table entry 1: 1000000 kHz, 4610 index
freq-table: table entry 2 is invalid, skipping
freq-table: table entry 3 is invalid, skipping
freq-table: table entry 4 is invalid, skipping
freq-table: setting show_table for cpu 0 to ffff81002b7cef40
cpu_init done, current fid 0xa, vid 0x2
cpufreq-core: setting new policy for CPU 0: 1000000 - 1800000 kHz
freq-table: request for verification of policy (1000000 - 1800000 kHz) for cpu 0
freq-table: verification lead to (1000000 - 1800000 kHz) for cpu 0
freq-table: request for verification of policy (1000000 - 1800000 kHz) for cpu 0
freq-table: verification lead to (1000000 - 1800000 kHz) for cpu 0
cpufreq-core: new min and max freqs are 1000000 - 1800000 kHz
cpufreq-core: governor switch
cpufreq-core: __cpufreq_governor for CPU 0, event 1
cpufreq-core: target for CPU 0: 1800000 kHz, relation 1
powernow-k8: targ: cpu 0, 1800000 kHz, min 1000000, max 1800000, relation 1
powernow-k8: targ: curr fid 0xa, vid 0x2
freq-table: request for target 1800000 kHz (relation: 1) for cpu 0
freq-table: target is 0 (1800000 kHz, 522)
powernow-k8: cpu 0 transition to index 0
powernow-k8: table matched fid 0xa, giving vid 0x2
powernow-k8: target matches current values (fid 0xa, vid 0x2)
cpufreq-core: governor: change or update limits
cpufreq-core: __cpufreq_governor for CPU 0, event 3
cpufreq-core: target for CPU 0: 1800000 kHz, relation 1
powernow-k8: targ: cpu 0, 1800000 kHz, min 1000000, max 1800000, relation 1
powernow-k8: targ: curr fid 0xa, vid 0x2
freq-table: request for target 1800000 kHz (relation: 1) for cpu 0
freq-table: target is 0 (1800000 kHz, 522)
powernow-k8: cpu 0 transition to index 0
powernow-k8: table matched fid 0xa, giving vid 0x2
powernow-k8: target matches current values (fid 0xa, vid 0x2)
cpufreq-core: initialization complete
cpufreq-core: driver powernow-k8 up and running
cpufreq-core: updating policy for CPU 0
cpufreq-core: setting new policy for CPU 0: 1000000 - 1800000 kHz
freq-table: request for verification of policy (1000000 - 1800000 kHz) for cpu 0
freq-table: verification lead to (1000000 - 1800000 kHz) for cpu 0
freq-table: request for verification of policy (1000000 - 1800000 kHz) for cpu 0
freq-table: verification lead to (1000000 - 1800000 kHz) for cpu 0
cpufreq-core: new min and max freqs are 1000000 - 1800000 kHz
cpufreq-core: governor: change or update limits
cpufreq-core: __cpufreq_governor for CPU 0, event 3
cpufreq-core: target for CPU 0: 1800000 kHz, relation 1
powernow-k8: targ: cpu 0, 1800000 kHz, min 1000000, max 1800000, relation 1
powernow-k8: targ: curr fid 0xa, vid 0x2
freq-table: request for target 1800000 kHz (relation: 1) for cpu 0
freq-table: target is 0 (1800000 kHz, 522)
powernow-k8: cpu 0 transition to index 0
powernow-k8: table matched fid 0xa, giving vid 0x2
powernow-k8: target matches current values (fid 0xa, vid 0x2)
.
.
.
powernow-k8: targ: cpu 0, 1800000 kHz, min 1000000, max 1800000, relation 0
powernow-k8: targ: curr fid 0x2, vid 0x12
freq-table: request for target 1800000 kHz (relation: 0) for cpu 0
freq-table: target is 0 (1800000 kHz, 522)
powernow-k8: cpu 0 transition to index 0
powernow-k8: table matched fid 0xa, giving vid 0x2
powernow-k8: cpu 0, changing to fid 0xa, vid 0x2
cpufreq-core: notification 0 of frequency transition to 1800000 kHz
cpufreq-core: scaling loops_per_jiffy to 1765376 for frequency 1800000 kHz
powernow-k8: detected change pending stuck
powernow-k8: transition frequency failed
[-- Attachment #3: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
next reply other threads:[~2005-06-04 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 20:32 John Belmonte [this message]
2005-06-04 22:50 ` speedstep_smi module loads randomly Fredrik Eriksson
2005-06-05 16:56 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 5:07 powernow-k8 and stuck change-pending bit Devriendt, Paul
2005-07-09 14:29 ` John Belmonte
2005-07-26 4:34 ` John Belmonte
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=42A20FCF.4070904@neggie.net \
--to=john@neggie.net \
--cc=cpufreq@lists.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.