From: Matthew Harrell <mharrell-dated-1105374160.f5a808@bittwiddlers.com>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: found unsupported CPU with Enhanced SpeedStep
Date: Wed, 5 Jan 2005 11:22:34 -0500 [thread overview]
Message-ID: <20050105162234.GA18703@bittwiddlers.com> (raw)
In-Reply-To: <20050105160622.GE19199@poupinou.org>
:
: Could you please send me those files as well?
: I would like much the full acpi dump, since it may be in a SSDT table
: instead.
:
Dominik was pretty helpful. It looks like the _PSD entries are missing from
the SSDT table. Many of my errors (and bootup instability) seem to go away
when I don't run with hyperthreading on. The processor does seem to scale
down the cpu speed but it just doesn't appear to like the interaction between
hpyerthreading and speedstep
Here are a bunch of the files I made available to him
http://alecto.bittwiddlers.com/files/inspiron-5160/dmesg
http://alecto.bittwiddlers.com/files/inspiron-5160/dmesg-noht
http://alecto.bittwiddlers.com/files/inspiron-5160/dsdt.dat
http://alecto.bittwiddlers.com/files/inspiron-5160/dsdt.dsl
http://alecto.bittwiddlers.com/files/inspiron-5160/ssdt.dat
http://alecto.bittwiddlers.com/files/inspiron-5160/ssdt.dsl
Does this contain the ACPI dump you were looking for?
--
Matthew Harrell Another Month's End:
Bit Twiddlers, Inc. All Targets Met
mharrell@bittwiddlers.com All Systems Working
All Customers Satisfied
All Staff Enthusiastic
All Pigs Fed And Ready To Fly
next prev parent reply other threads:[~2005-01-05 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041230014005.GA16358@bittwiddlers.com>
2004-12-30 22:38 ` found unsupported CPU with Enhanced SpeedStep Jeremy Fitzhardinge
2005-01-02 12:07 ` Dominik Brodowski
2005-01-05 16:06 ` Bruno Ducrot
2005-01-05 16:22 ` Matthew Harrell [this message]
2005-01-05 17:24 ` Bruno Ducrot
2005-01-05 18:02 ` Matthew Harrell
2005-01-06 10:00 ` Bruno Ducrot
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=20050105162234.GA18703@bittwiddlers.com \
--to=mharrell-dated-1105374160.f5a808@bittwiddlers.com \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox