Bug 10784 - AMD64 laptop hangs after logging powernow-k8 error while on battery.
Summary: AMD64 laptop hangs after logging powernow-k8 error while on battery.
Status: RESOLVED OBSOLETE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-23 19:24 UTC by Jason White
Modified: 2012-08-29 17:06 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.28
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Jason White 2008-05-23 19:24:53 UTC
Earliest failing kernel version: not known, first noticed on 2.6.22
Distribution: Debian
Hardware environment: AMD Athlon64 laptop
Problem Description: When this laptop is run on battery, the following error
is logged:

May 23 15:55:41 jpc kernel: [   38.255997] powernow-k8: error - out of sync,
fix 0x8 0x0, vid 0x6 0x12

Under kernel versions 2.6.22 and 2.6.24, the system eventually hangs,
displaying the above error on the console. Under kernel 2.6.25, the hang has
so far occurred only during shutdown (prior to unmounting file systems). I can
carry out more testing if necessary.

Since I don't run this laptop frequently on battery, I don't know when the
problem was introduced; it was probably after the 2.6.18 kernel at some point,
and definitely before 2.6.22. The laptop has worked on battery in the past
with the 2.6 kernel series and powernow-k8 loaded.

Steps to reproduce:

1. Load the powernow-k8 module (in my case, this happens during boot as I have
selected the ondemand CPU frequency governor).

2. Run the machine on battery rather than from AC power.

History of bug: detected and tested with Debian kernels, reported as Debian
bug 464664:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464664
Debian kernel maintainers requested that it be reported upstream (see the Web
page cited above) after it was found to occur with the latest Debian 2.6.25
kernel release.

/proc/cpuinfo:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 4
model name      : AMD Athlon(tm) 64 Processor 3000+
stepping        : 10
cpu MHz         : 800.000
cache size      : 1024 KB
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 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up rep_good
bogomips        : 1597.95
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp

I also notice the following, which may or may not be related:
modprobe acpi
Error inserting acpi_cpufreq (/lib/modules/2.6.25-2-amd64/kernel/arch/x86
/cpu/cpufreq/acpi-cpufreq.ko): Device or resource busy
Comment 1 Mark Langsdorf 2008-06-02 12:24:30 UTC
Would it be possible for you to test kernels from 2.6.18 to 2.6.23 to see when the error was introduced?

The error code you're seeing has been in the driver since the 1st version and has not changed in years.  Getting a clearer idea of what caused the problem could be
useful.
Comment 2 Jeremy Harmon 2009-11-18 05:50:12 UTC
I'm also experiencing a similar issue with my desktop running the same processor.

uname:
Linux A64 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 i686 GNU/Linux


cpuinfo:
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 15
model		: 4
model name	: AMD Athlon(tm) 64 Processor 3000+
stepping	: 10
cpu MHz		: 1800.000
cache size	: 512 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 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up
bogomips	: 3618.31
clflush size	: 64
power management: ts fid vid ttp
Comment 3 Alan 2012-08-29 17:06:32 UTC
Closing as obsolete, if this is incorrect please reopen and update giving a modern kernel showing the problem, thanks

Note You need to log in before you can comment on or make changes to this bug.