* [Oops] ACPI problem with 2.6.0-test11 on Asus L3800C
@ 2003-12-04 13:34 David Gümbel
2003-12-04 13:50 ` Måns Rullgård
0 siblings, 1 reply; 2+ messages in thread
From: David Gümbel @ 2003-12-04 13:34 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]
[Please CC me, as I am not subscribed to this list]
I have recently installed 2.6.0-test11 on my Asus L3800C laptop. One thing I
stumbled across was that it is no longer possible to set the CPU
performance via ACPI. It worked fine with 2.4.21 with acpi-patch applied.
The behaviour is reproducible, i.e. it happens every time I try to set the
performance. Symptoms are as follows:
When executing 'echo 1 > /proc/acpi/processor/CPU0/performance', I got the
following (visible via dmesg):
-------------------------------------------------------------------------
Unable to handle kernel NULL pointer dereference at virtual address 00000030
printing eip:
c0115b3d
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c0115b3d>] Not tainted
EFLAGS: 00210202
EIP is at acpi_processor_write_performance+0x12d/0x17f
eax: 00000020 ebx: cf62d2a0 ecx: dfd4d3a4 edx: dfd4d3c4
esi: 00000000 edi: 00000002 ebp: c734bec4 esp: c734beb0
ds: 007b es: 007b ss: 0068
Process bash (pid: 10637, threadinfo=c734a000 task=d1cb26a0)
Stack: c734bec4 00000000 00000000 c13d3038 c01452e0 00000000 001e8480
00124f80
000000fa 00124f80 001e8480 000007d0 00000000 c042cd40 00000000
00000000
dfd4d3ac dfd4d3ac 00124f80 001e8480 00000000 c042cd40 dfd4d3c8
66757063
Call Trace:
[<c01452e0>] do_anonymous_page+0x138/0x21f
[<c0152d6e>] vfs_write+0xbc/0x127
[<c0152e7e>] sys_write+0x42/0x63
[<c010b31b>] syscall_call+0x7/0xb
Code: 8b 48 10 b8 e8 03 00 00 89 2c 24 f7 e1 89 44 24 28 e8 42 a8
-----------------------------------------------------------------------
I attached my $(grep ^C .config) and the output of dmesg and lsmod. The
Cisco Modules that taint the kernel (see dmesg file) do not change the
behaviour. dmesg output contains the described error twice, the first time
triggered by the KDE laptop daemon, and the second time by a cat as
described. Above output was taken from a untainted kernel instance (but I
need those Cisco modules for internet connectivity ;)
If any information or tests are needed, I will be happy to provide / run
them ;)
Greetings
David
[-- Attachment #2: dmesg-2.6.0-test11-L3800C.txt.gz --]
[-- Type: application/x-gzip, Size: 5970 bytes --]
[-- Attachment #3: lsmod-2.6.0-test11-L3800C.gz --]
[-- Type: application/x-gzip, Size: 651 bytes --]
[-- Attachment #4: config.gz --]
[-- Type: application/x-gzip, Size: 6724 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Oops] ACPI problem with 2.6.0-test11 on Asus L3800C
2003-12-04 13:34 [Oops] ACPI problem with 2.6.0-test11 on Asus L3800C David Gümbel
@ 2003-12-04 13:50 ` Måns Rullgård
0 siblings, 0 replies; 2+ messages in thread
From: Måns Rullgård @ 2003-12-04 13:50 UTC (permalink / raw)
To: linux-kernel
David Gümbel <david.guembel@gmx.de> writes:
> [Please CC me, as I am not subscribed to this list]
>
> I have recently installed 2.6.0-test11 on my Asus L3800C laptop. One thing I
> stumbled across was that it is no longer possible to set the CPU
> performance via ACPI. It worked fine with 2.4.21 with acpi-patch applied.
> The behaviour is reproducible, i.e. it happens every time I try to set the
> performance. Symptoms are as follows:
>
> When executing 'echo 1 > /proc/acpi/processor/CPU0/performance', I got the
> following (visible via dmesg):
The standard method of changing CPU frequency in Linux 2.6 is the
cpufreq interface in /sys/devices/system/cpu/cpu0/cpufreq/*. This may
not solve your problem, of course.
--
Måns Rullgård
mru@kth.se
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-12-04 13:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-04 13:34 [Oops] ACPI problem with 2.6.0-test11 on Asus L3800C David Gümbel
2003-12-04 13:50 ` Måns Rullgård
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).