Bug#594952: linux-image doesn't work properly with Pentium M CPU
 

Package: linux-image-2.6-686
Version: 2.6.32+28
Computer: Fujitsu-Siemens AMILO L7300

The fact that acpi-cpufreq is not working properly with Dothan CPU's.

FATAL: Error inserting acpi_cpufreq:
No such device

cpuinfo:

processor : 0

vendor_id : GenuineIntel

cpu family : 6

model : 13

model name : Intel(R) Pentium(R) M processor 1.73GHz (Dothan)

stepping : 8

cpu MHz : 598.000

cache size : 2048 KB

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 2

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov
clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up bts est tm2

bogomips : 1197.07

clflush size : 64

On Ubuntu Karmic/Jaunty all works fine. It uses speedstep_centrino driver, which is deprecated, but works with BIOS which have broken voltage tables..

Link to Ubuntu Patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=blobdiff;f=arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c;h=ee4e9f8050752923f9671f61ffbea662bc9ad 12a;hp=9b1ff37de46ae6a729f48d2d94ad30548806884d;hb =23120eb5ae5a12924565e8af3d946a015e1caaf9;hpb=215c c71ef0b26b9434404f387681d9bd173d2434


Discussion: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/132271

Please attach it to main kernel, otherwise many users have to stay with Ubuntu :(

Bug#594952: linux-image doesn't work properly with Pentium M CPU
 

On Tue, 2010-08-31 at 12:11 +0700, Alexey wrote:
> Package: linux-image-2.6-686
> Version: 2.6.32+28
> Computer: Fujitsu-Siemens AMILO L7300
>
> The fact that acpi-cpufreq is not working properly with Dothan CPU's.

I don't think that's true. It really depends on whether the BIOS
provides correct information about the available frequencies.

> FATAL: Error inserting acpi_cpufreq: No such device

Please try creating the file /etc/modprobe.d/processor-ppc.conf
containing the text:

options processor ignore_ppc=1

and then reboot.

[...]
> On Ubuntu Karmic/Jaunty all works fine. It uses speedstep_centrino
> driver, which is deprecated, but works with BIOS which have broken
> voltage tables..
>
> Link to Ubuntu Patch:
> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=blobdiff;f=arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c;h=ee4e9f8050752923f9671f61ffbea662bc9ad 12a;hp=9b1ff37de46ae6a729f48d2d94ad30548806884d;hb =23120eb5ae5a12924565e8af3d946a015e1caaf9;hpb=215c c71ef0b26b9434404f387681d9bd173d2434
[...]

This doesn't seem like a good idea, and it has not been accepted by the
upstream developers.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Bug#594952: linux-image doesn't work properly with Pentium M CPU
 

-------- Forwarded Message --------
From: Alexey <nikvart@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Bug#594952: linux-image doesn't work properly with Pentium M CPU
Date: Mon, 6 Sep 2010 14:13:53 +0700

Thanks for suggesting this, but after searching the web I don't think this
applies to my situation: my processor isn't stuck at the lowest frequency
when using acpi-cpufreq, but rather it refuses to load with the error
message "no such device"...

On Sun, Sep 5, 2010 at 8:40 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
On Tue, 2010-08-31 at 12:11 +0700, Alexey wrote:
> Package: linux-image-2.6-686
> Version: 2.6.32+28
> Computer: Fujitsu-Siemens AMILO L7300
>
> The fact that acpi-cpufreq is not working properly with Dothan CPU's.

I don't think that's true. It really depends on whether the BIOS
provides correct information about the available frequencies.

> FATAL: Error inserting acpi_cpufreq: No such device

Please try creating the file /etc/modprobe.d/processor-ppc.conf
containing the text:

options processor ignore_ppc=1

and then reboot.

[...]
> On Ubuntu Karmic/Jaunty all works fine. It uses speedstep_centrino
> driver, which is deprecated, but works with BIOS which have broken
> voltage tables..
>
> Link to Ubuntu Patch:
> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=blobdiff;f=arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c;h=ee4e9f8050752923f9671f61ffbea662bc9ad 12a;hp=9b1ff37de46ae6a729f48d2d94ad30548806884d;hb =23120eb5ae5a12924565e8af3d946a015e1caaf9;hpb=215c c71ef0b26b9434404f387681d9bd173d2434
[...]

This doesn't seem like a good idea, and it has not been accepted by the
upstream developers.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.






--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1284331724.5323.718.camel@localhost">http://lists.debian.org/1284331724.5323.718.camel@localhost

Bug#594952: linux-image doesn't work properly with Pentium M CPU
 

retitle 594952 [AMILO L7300] no frequency scaling support (BIOS has broken voltage tables and speedstep-centrino doesn't support Dothan)
# guessing
found 594952 linux-2.6/2.6.32-21
tags 594952 + upstream
quit

Hi Alexey,

Alexey wrote:

> Computer: Fujitsu-Siemens AMILO L7300
[...]
> FATAL: Error inserting acpi_cpufreq: No such device
[...]
> model name : Intel(R) Pentium(R) M processor 1.73GHz (Dothan)
> stepping : 8
[...]
> On Ubuntu Karmic/Jaunty all works fine. It uses speedstep_centrino driver,
> which is deprecated, but works with BIOS which have broken voltage tables..

See http://bugs.debian.org/638913 for some discussion.

Basically, as you've said, this is a bug in your BIOS. That does not mean
the problem is hopeless --- it is possible for the kernel to work
around well understood BIOS bugs in the worst cases.

So, to move forward on this:

- Please attach output from "dmesg" and from "acpidump" from immediately
after booting.

- The next step would be to contact linux-acpi@vger.kernel.org and your
BIOS vendor, to get the bug well documented. If there is information
about the bug already online somewhere, that could be helpful.

- Work with the linux-acpi@ people to come up with corrected ACPI tables.
Make them available.

- Finally, if the BIOS vendor is uncooperative, come up with a patch to
add a "quirk" to use an appropriate hard-coded table to match the
detected (through DMI, I guess) system. Or add a kernel command line
argument to switch between tables, and a tool to detect the right
table at run time.

Hope that helps,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111124062515.GA22652@elie.hsd1.il.comcast.net">h ttp://lists.debian.org/20111124062515.GA22652@elie.hsd1.il.comcast.net