From: Voluspa <lista1-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
To: Roman I Khimov <rik-MdmE8JOsREphl2p70BpVqQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
akpm-3NddpPZAyC0@public.gmane.org,
mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
Subject: Re: Fw: Re: 2.6.15-rc5-mm1
Date: Wed, 14 Dec 2005 05:04:28 +0100 [thread overview]
Message-ID: <20051214050428.21d3f224.lista1@telia.com> (raw)
In-Reply-To: <200512101320.18779.rik-MdmE8JOsREphl2p70BpVqQ@public.gmane.org>
On Sat, 10 Dec 2005 13:20:15 +0300 Roman I Khimov wrote:
> | Voluspa:
> > Nope, neither "nocst" nor "acpi=nocst" gave me back the C1
> > functionality...
>
> Yep, same here, just tried.
Sorry about the red herring. I've patched 2.6.14 with the two acpi
suggestions for this stable series that Greg KH posted (both single and
combined):
[patch 10/26] ACPI: Prefer _CST over FADT for C-state capabilities
http://marc.theaimsgroup.com/?l=linux-kernel&m=113446277408937&w=2
[patch 12/26] ACPI: Add support for FADT P_LVL2_UP flag
http://marc.theaimsgroup.com/?l=linux-kernel&m=113446277427267&w=2
I thought nr 10 was the cause for the C-state regression, but neither
effected my machine. C1 was used as it should. Now, I don't have the
stomach for an un-cheerleaded "git bisect" of approximately four hours
to find the real culprit. So unless someone waves the pompoms I'll slip
quietly into the shadows, hoping the issue will disappear by itself
before 2.6.15 is finalized.
Mvh
Mats Johannesson
--
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-14 4:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 10:15 Fw: Re: 2.6.15-rc5-mm1 Voluspa
[not found] ` <20051210111557.18ba5fc8.lista1-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
2005-12-10 10:20 ` Roman I Khimov
[not found] ` <200512101320.18779.rik-MdmE8JOsREphl2p70BpVqQ@public.gmane.org>
2005-12-14 4:04 ` Voluspa [this message]
[not found] ` <20051214050428.21d3f224.lista1-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
2005-12-22 13:35 ` Thomas Renninger
[not found] ` <43AAABA7.7080303-l3A5Bk7waGM@public.gmane.org>
2005-12-22 15:07 ` Voluspa
-- strict thread matches above, loose matches on Subject: below --
2005-12-10 9:50 Voluspa
2005-12-06 3:08 Andrew Morton
[not found] ` <20051206140841.2c3d7c52.akpm-3NddpPZAyC0@public.gmane.org>
2005-12-06 3:41 ` Matthew Garrett
[not found] ` <20051206034145.GA10975-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2005-12-06 7:17 ` Roman I Khimov
[not found] ` <200512061017.43247.rik-MdmE8JOsREphl2p70BpVqQ@public.gmane.org>
2005-12-06 15:12 ` Matthew Garrett
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=20051214050428.21d3f224.lista1@telia.com \
--to=lista1-zq6ireyz3ykavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
--cc=rik-MdmE8JOsREphl2p70BpVqQ@public.gmane.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