From: Thomas Renninger <mail@renninger.de>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Mobile Celeron with Speedstep ? - speedstep-centrino freezes machine
Date: Tue, 21 Sep 2004 17:55:21 +0200 [thread overview]
Message-ID: <41504EE9.6000403@renninger.de> (raw)
In-Reply-To: <20040920170957.GC7952@dominikbrodowski.de>
Dominik Brodowski wrote:
> On Mon, Sep 20, 2004 at 03:41:05PM +0200, Thomas Renninger wrote:
>
>>I thought Celeron CPUs are not speedstep capable, seems as if I was
>>wrong (ss flag indicates speedstep, right?)...
>
>
> no, ss flag indicates something else, enhanced speedstep is indicated by
> "est".
>
>
>>On this machine speedstep-centrino freezes machine (shouldn't it already
>>go out at the model name check, or has this been changed?):
>
>
> It should reaturn -ENODEV in centrino_init().
>
> if (!cpu_has(cpu, X86_FEATURE_EST))
> return -ENODEV;
>
Freezes before or inside this function.
This machine seems totally broken:
modprobe cpufreq_acpi_pdump
FATAL: Error inserting cpufreq_acpi_pdump
(/lib/modules/2.6.8-7-default/kernel/drivers/acpi/cpufreq-acpi_pdump.ko):
Input/output error
ibm9:/usr/src/linux/arch/i386/kernel/cpu/cpufreq #
-> Freeze.
Anyone an idea what exactly could cause the freeze, or how to analyse it?
If someone is interested, email me and you can have remote access on the
machine.
The guys who own this machine have about ten of those (IBM R40e - Mobile
Celeron). Tested on three machines and it was the same problem on each.
Thomas
next prev parent reply other threads:[~2004-09-21 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 13:41 Mobile Celeron with Speedstep ? - speedstep-centrino freezes machine Thomas Renninger
2004-09-20 17:09 ` Dominik Brodowski
2004-09-21 15:55 ` Thomas Renninger [this message]
2004-09-21 16:33 ` Dominik Brodowski
2004-09-22 23:50 ` Stefan Seyfried
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=41504EE9.6000403@renninger.de \
--to=mail@renninger.de \
--cc=cpufreq@www.linux.org.uk \
--cc=linux@dominikbrodowski.de \
/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.