mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniele Venzano <webvenza@libero.it>
To: davej@codemonkey.org.uk
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	cpufreq@www.linux.org.uk
Subject: Athlon XP-M and cpufreq freezing Asus laptop to death
Date: Sun, 24 Aug 2003 18:48:29 +0200	[thread overview]
Message-ID: <20030824164828.GA922@renditai.milesteg.arr> (raw)

I don't know if I'm hunting a bug or I have to add support for my
hardware somewhere.
I succeded in making C2 work adjusting the DSDT table, I'm uploading the 
new one on acpi.sf.net under Asus/L3100D

Now for cpufreq: I'm using the powernow-k7 driver, since the acpi 
P-state is not supported.
Whenever I try to change the governor by echoing "powersave" in
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor everything stops
and a hard reset is required. It seemes to fall in some tight loop since
after a few seconds the fan goes on as if there is heavy processor
usage.

With some printk I have verified that it halts inside wrmsrl() at line
199, file powernow-k7.c (2.6.0-test4).
The call trace is:
powernow_target/change_speed/change_FID/wrmsrl

For what is my knowledge (very, very little) the frequency passed to
powernow_target is right, but I can't say nothing on all other
parameters...

Full dmesg and .config available here[2] and here[3], /proc/cpuinfo 
and /proc/acpi/processor/CPU0/{power,info} follows.

/proc/cpuinfo
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 6
model		: 8
model name	: mobile AMD Athlon(tm) XP-M 2000+
stepping	: 1
cpu MHz		: 1673.782
cache size	: 256 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
bogomips	: 3309.56

/proc/acpi/processor/CPU0/power
active state:            C2
default state:           C1
bus master activity:     00000000
states:
    C1:                  promotion[C2] demotion[--] latency[000] usage[00653320]
   *C2:                  promotion[--] demotion[C1] latency[090] usage[04958506]
    C3:                  <not supported>

/proc/acpi/processor/CPU0/info
processor id:            0
acpi id:                 1
bus mastering control:   no
power management:        yes
throttling control:      yes
performance management:  no
limit interface:         yes

Using the acpi p state driver I get a message saying something about
'unsupported address space' (see [1] for details) and the machine
stops working also by echoing 'performance' (that is already there) in
sysfs.

I don't know what to do next, someone here can give me any hint ?

Thanks for any help on this matter.

[1] http://www.ussg.lu.edu/hypermail/linux/kernel/0308.2/1892.html
[2] http://digilander.libero.it/webvenza/download/kpatches/dmesg-cpufreq
[3] http://digilander.libero.it/webvenza/download/kpatches/config-cpufreq


-- 
----------------------------------------
Daniele Venzano
Web: http://digilander.iol.it/webvenza/


             reply	other threads:[~2003-08-24 16:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-24 16:48 Daniele Venzano [this message]
2003-08-25  7:10 ` Ducrot Bruno
2003-09-01 20:09   ` Pavel Machek
2003-09-02 12:56     ` Dave Jones
2003-09-05  9:23       ` Ducrot Bruno

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=20030824164828.GA922@renditai.milesteg.arr \
    --to=webvenza@libero.it \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®