From: Corentin Chary <corentin.chary@gmail.com>
To: "Andrea R." <7252d9@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [2.6.27.7] processor.ko messes up ACPI resume
Date: Fri, 17 Jul 2009 13:59:18 +0200 [thread overview]
Message-ID: <71cd59b00907170459q24e22ebbrc74702b34788a7b2@mail.gmail.com> (raw)
In-Reply-To: <20090717085023.GB2016@acerrimo>
On Fri, Jul 17, 2009 at 10:50 AM, Andrea R.<7252d9@gmail.com> wrote:
> Il 11/07/2009 alle 15:11, Andrea R. ha scritto:
>
>> Hi all,
>>
>> I was having problems resuming my Acer laptop from suspend-to-RAM, where
>> upon waking up the screen was flashing madly (think detuned TV). This
>> laptop had no problems waking up using previous kernel releases, the
>> latest I had tried before 2.6.27 being 2.6.18.
>>
>> After long trials, I traced the issue to the "processor.ko" kernel
>> module: if I unload it - even while the screen is being crazy - all goes
>> back to normal.
>>
>> Problem is, that module is needed to probe the CPU's temperature and - I
>> think - for clock frequency stepping.
>>
>> Does anyone know how do I get to keep it *and* get working resume
>> functionality?
>>
>> I'm using 32-bit Slackware 12.2 at the moment, but the exact same
>> symptoms were shown by Fedora 11 x86_64.
>>
>> My laptop has an AMD Turion64 processor and an ATI Radeon Xpress1100
>> graphics card driven by X.Org's "ati" driver. Please write if you need
>> lspci's output or more detailed info or tests.
>>
>> Thanks in advance for your comments.
>
>
> Good thing I thanked in advance...
>
Hi,
Can you try with the latest git version ?
Maybe this is already fixed.
Thanks,
--
Corentin Chary
http://xf.iksaif.net - http://uffs.org
prev parent reply other threads:[~2009-07-17 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 13:11 [2.6.27.7] processor.ko messes up ACPI resume Andrea R.
2009-07-17 8:50 ` Andrea R.
2009-07-17 11:59 ` Corentin Chary [this message]
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=71cd59b00907170459q24e22ebbrc74702b34788a7b2@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=7252d9@gmail.com \
--cc=linux-acpi@vger.kernel.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