From: Matt Wright <matt@consultmatt.co.uk>
To: cpufreq@www.linux.org.uk
Subject: Re: Cpufreq and AMD mobile Athlon 4
Date: 03 Sep 2003 22:55:02 +0100 [thread overview]
Message-ID: <1062626101.4840.0.camel@riogrande> (raw)
In-Reply-To: <20030902201722.GD1225@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
Hi guys,
See attached the decoded sys oops from my encounters with powernow-k7.
Regards,
Matt
On Tue, 2003-09-02 at 21:17, Dave Jones wrote:
> On Tue, Sep 02, 2003 at 10:03:56PM +0200, V?lgyi Zolt?n wrote:
>
> > I've got the same problem with my notebook. This is a
> > Fujitsu-Siemens Amilo A7600.
>
> noted. Can you mail me the dmidecode output too please ?
> (See http://people.redhat.com/arjanv/dmidecode.c)
>
> > Nothing else.
> > But what to do?
>
> Is there a BIOS update available you can try ?
>
> I really wish I had the time to get sysfs overrides written..
>
> Dave
[-- Attachment #2: result --]
[-- Type: text/plain, Size: 2125 bytes --]
Unable to handle kernel NULL pointer dereference at virtual address 00000004
c019423c
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c019423c>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: c3c5df10 ecx: 00000000 edx: 00000000
esi: 00000000 edi: ffffffff ebp: 00000000 esp: c3c5debc
ds: 0018 es: 0018 ss: 0018
Process bash (pid: 4857, stackpage=c3c5d000)
Stack: 00000000 c02a2ee0 c3c5df10 c3c5df40 c3c5df10 ccd007e8 c3c5df10 00000000
c012860e c3c5df10 c2194898 0000000c c3c5df84 0000001b 00000000 c3c5df40
c3c5df10 c0194838 c3c5df10 c3c5df10 0000001b 00000000 00000000 00000000
Call Trace: [<ccd007e8>] [<c012860e>] [<c0194838>] [<c015dce0>] [<c013c1d3>]
[<c0108dc7>]
Code: 8b 45 04 31 c9 83 f8 fe 74 1b 83 f8 ff 74 0c 3b 43 04 72 5a
>>EIP; c019423c <cpufreq_frequency_table_verify+5c/f0> <=====
Trace; ccd007e8 <[powernow-k7]powernow_verify+18/20>
Trace; c012860e <cpufreq_set_policy+8e/270>
Trace; c0194838 <cpufreq_proc_write+f8/140>
Trace; c015dce0 <proc_file_write+40/50>
Trace; c013c1d3 <sys_write+a3/130>
Trace; c0108dc7 <system_call+33/38>
Code; c019423c <cpufreq_frequency_table_verify+5c/f0>
00000000 <_EIP>:
Code; c019423c <cpufreq_frequency_table_verify+5c/f0> <=====
0: 8b 45 04 mov 0x4(%ebp),%eax <=====
Code; c019423f <cpufreq_frequency_table_verify+5f/f0>
3: 31 c9 xor %ecx,%ecx
Code; c0194241 <cpufreq_frequency_table_verify+61/f0>
5: 83 f8 fe cmp $0xfffffffe,%eax
Code; c0194244 <cpufreq_frequency_table_verify+64/f0>
8: 74 1b je 25 <_EIP+0x25>
Code; c0194246 <cpufreq_frequency_table_verify+66/f0>
a: 83 f8 ff cmp $0xffffffff,%eax
Code; c0194249 <cpufreq_frequency_table_verify+69/f0>
d: 74 0c je 1b <_EIP+0x1b>
Code; c019424b <cpufreq_frequency_table_verify+6b/f0>
f: 3b 43 04 cmp 0x4(%ebx),%eax
Code; c019424e <cpufreq_frequency_table_verify+6e/f0>
12: 72 5a jb 6e <_EIP+0x6e>
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2003-09-03 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 11:02 Cpufreq and AMD mobile Athlon 4 Matt Wright
2003-09-02 12:59 ` Dave Jones
2003-09-02 20:03 ` Völgyi Zoltán
2003-09-02 20:17 ` Dave Jones
2003-09-03 16:15 ` Stefan Gehn
2003-09-03 21:55 ` Matt Wright [this message]
2003-09-05 16:12 ` Matt Wright
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=1062626101.4840.0.camel@riogrande \
--to=matt@consultmatt.co.uk \
--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.