From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Alex <ambroxa@yahoo.it>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Avoid C2/C3 idle state
Date: Tue, 24 Nov 2009 23:29:53 +0100 [thread overview]
Message-ID: <20091124222953.GA5983@isilmar.linta.de> (raw)
In-Reply-To: <642590.96306.qm@web26502.mail.ukl.yahoo.com>
Hey,
you can set the maximum C-state to use using the
"processor.max_cstate=<value>" parameter. No need to recompile.
Best,
Dominik
On Tue, Nov 24, 2009 at 09:50:01PM +0000, Alex wrote:
> I run Ubuntu 8.04.3 LTS server 32bit in a small low power motherboard (VIA LN10000EG) equipped with VIA C7 1GHz CPU.
> Kernel 2.6.24
>
> I've some problems with serial device: sometimes I've overrun errors when receive data through /dev/ttyS0
>
> After some days of hard work I've discovered that when CPU enter in C2 or C3 state and data come in from serial line, I've the overrun.
>
> I've searched for a solution and I've found that kernel parameter "idle=halt" can avoid CPU enter C2/C3 state, but this parameter is now not supported anymore (it was in the past).
> So I've completely disabled the ACPI support ("acpi=off" kernel parameter).
> But I lack support for power button, poweroff command and so on.
> I wish to re-enable ACPI.
>
> The question is: Howto avoid CPU enter C2/C3 state and re-activate ACPI so CPU can go in C1 state ? C1 is better than nothing at all ....
>
> I have no problem to modify kernel source and recompile it.
>
> Thanks fo suggestions
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-24 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 21:50 Avoid C2/C3 idle state Alex
2009-11-24 22:29 ` Dominik Brodowski [this message]
2009-11-25 6:53 ` Alex
2009-11-25 8:05 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2009-11-25 12:05 Alex
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=20091124222953.GA5983@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=ambroxa@yahoo.it \
--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