From: Stelian Pop <stelian.pop-A5NNTvo2L0pl57MIdRCFDg@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Crash with fs corruption on 2.4.23-rc1 + CONFIG_ACPI_PROCESSOR
Date: Sat, 15 Nov 2003 14:48:11 +0100 [thread overview]
Message-ID: <20031115134811.GA2630@hottah.alcove-fr> (raw)
In-Reply-To: <20031115065020.GO32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
On Sat, Nov 15, 2003 at 07:50:20AM +0100, Ducrot Bruno wrote:
> I think the trouble come from C3, just need to check some values. If you
> can, it may be usefull that you disable C3, with something like that:
>
> + acpi_fadt.plvl3_lat = 1234;
And the patch works, your assumption was correct.
Now, C3 seem to be reported as supported, 2.6 (correctly) doesn't
promote to it, but 2.4 does. I can't find an obvious reason by reading
the processor.c code (almost identical between 2.4/2.6...)
The only 'strange' thing I see in /proc/acpi/processor/CPU0/power
(different wrt the 2.6 data I posted earlier) is the 'bus mastering
activity' field:
active state: C2
default state: C1
bus master activity: 00000000
states:
C1: promotion[C2] demotion[--] latency[000] usage[00000340]
*C2: promotion[--] demotion[C1] latency[003] usage[00034161]
C3: <not supported>
Any ideas ?
Stelian.
--
Stelian Pop <stelian.pop-A5NNTvo2L0pl57MIdRCFDg@public.gmane.org>
Alcove - http://www.alcove.com
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
next prev parent reply other threads:[~2003-11-15 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 16:18 Crash with fs corruption on 2.4.23-rc1 + CONFIG_ACPI_PROCESSOR Stelian Pop
[not found] ` <20031113161857.GM26911-sxQ6dllMCJFOpCWnugOeNx8pCrqmY5it@public.gmane.org>
2003-11-14 12:47 ` Ducrot Bruno
[not found] ` <20031114124713.GK32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-14 15:24 ` Stelian Pop
[not found] ` <20031114152403.GK29316-sxQ6dllMCJFOpCWnugOeNx8pCrqmY5it@public.gmane.org>
2003-11-15 6:50 ` Ducrot Bruno
[not found] ` <20031115065020.GO32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-15 12:54 ` Stelian Pop
2003-11-15 13:48 ` Stelian Pop [this message]
[not found] ` <20031115134811.GA2630-Snhs3Gxj9njPHUqn3ntIkQ@public.gmane.org>
2003-11-17 13:18 ` Ducrot Bruno
[not found] ` <20031117131800.GQ32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-17 18:31 ` Nate Lawson
[not found] ` <20031117102931.B60721-Y6VGUYTwhu0@public.gmane.org>
2003-11-17 19:51 ` Ducrot Bruno
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=20031115134811.GA2630@hottah.alcove-fr \
--to=stelian.pop-a5nntvo2l0pl57midrcfdg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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