All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Schütz" <r.schtz@t-online.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Ozan Çağlayan" <ozan@pardus.org.tr>,
	"Lionel Debroux" <lionel_debroux@yahoo.fr>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, colin.king@canonical.com
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)
Date: Mon, 31 Jan 2011 11:29:51 +0100	[thread overview]
Message-ID: <4D468F1F.8030704@t-online.de> (raw)
In-Reply-To: <201101311123.14704.rjw@sisk.pl>

>>>> I'll compile a kernel with CONFIG_NO_HZ to see what happens but how do I
>>>> disable cpuidle during boot? I've checked the kernel-parameters.txt but
>>>> there's no cpuidle related boot parameter there.
>>>
>>> Booting with intel_idle.max_cstate=0 should do the trick.
>>
>> intel_idle.max_cstate=0 causes a fallback to the acpi_idle driver. So it
>> does not disable the C-states directly.
>
> What about not building the acpi_idle driver, then?

Or just use the processor.max_cstate parameter then.

-- 
Regards,
Richard Schütz
--
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

WARNING: multiple messages have this Message-ID (diff)
From: "Richard Schütz" <r.schtz@t-online.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Ozan Çağlayan" <ozan@pardus.org.tr>,
	"Lionel Debroux" <lionel_debroux@yahoo.fr>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, colin.king@canonical.com
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)
Date: Mon, 31 Jan 2011 11:29:51 +0100	[thread overview]
Message-ID: <4D468F1F.8030704@t-online.de> (raw)
In-Reply-To: <201101311123.14704.rjw@sisk.pl>

>>>> I'll compile a kernel with CONFIG_NO_HZ to see what happens but how do I
>>>> disable cpuidle during boot? I've checked the kernel-parameters.txt but
>>>> there's no cpuidle related boot parameter there.
>>>
>>> Booting with intel_idle.max_cstate=0 should do the trick.
>>
>> intel_idle.max_cstate=0 causes a fallback to the acpi_idle driver. So it
>> does not disable the C-states directly.
>
> What about not building the acpi_idle driver, then?

Or just use the processor.max_cstate parameter then.

-- 
Regards,
Richard Schütz

  reply	other threads:[~2011-01-31 10:30 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 14:28 Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) Ozan Çağlayan
2011-01-23 15:00 ` Richard Schütz
2011-01-23 15:11   ` Gene Heskett
2011-01-23 16:49   ` Ozan Çağlayan
2011-01-23 16:56 ` Ozan Çağlayan
2011-01-23 20:24 ` Ozan Çağlayan
2011-01-23 20:24   ` Ozan Çağlayan
2011-01-24  9:00   ` Ozan Çağlayan
2011-01-24  9:04   ` Lionel Debroux
2011-01-24  9:04     ` Lionel Debroux
2011-01-24  9:21     ` Ozan Çağlayan
2011-01-24  9:47       ` Lionel Debroux
2011-01-24  9:47         ` Lionel Debroux
2011-01-24 20:14         ` Lionel Debroux
2011-01-25  2:56           ` Len Brown
2011-01-26  7:41             ` Lionel Debroux
2011-01-27  7:59               ` Lionel Debroux
2011-01-25  6:22           ` Ozan Çağlayan
2011-01-25 19:38             ` Rafael J. Wysocki
2011-01-25 19:38               ` Rafael J. Wysocki
2011-01-25 19:45               ` Ozan Çağlayan
2011-01-25 19:54                 ` Rafael J. Wysocki
2011-01-25 19:54                   ` Rafael J. Wysocki
2011-01-25 20:00                   ` Ozan Çağlayan
2011-01-29 17:49                   ` Ozan Çağlayan
2011-01-30 20:30                     ` Ozan Çağlayan
2011-01-30 20:30                       ` Ozan Çağlayan
2011-01-30 22:48                       ` Rafael J. Wysocki
2011-01-31  8:53                         ` Ozan Çağlayan
2011-01-31  9:50                           ` Rafael J. Wysocki
2011-01-31  9:50                             ` Rafael J. Wysocki
2011-01-31 10:03                             ` Ozan Çağlayan
2011-01-31 10:14                               ` Rafael J. Wysocki
2011-01-31 10:14                                 ` Rafael J. Wysocki
2011-01-31 10:20                             ` Richard Schütz
2011-01-31 10:23                               ` Rafael J. Wysocki
2011-01-31 10:29                                 ` Richard Schütz [this message]
2011-01-31 10:29                                   ` Richard Schütz
2011-01-31 18:24                                   ` Rafael J. Wysocki
2011-01-31 18:24                                     ` Rafael J. Wysocki
2011-01-31 18:29                                     ` Ozan Çağlayan
2011-01-31 18:33                                       ` Rafael J. Wysocki
2011-01-31 18:38                                         ` Ozan Çağlayan
2011-01-31 19:12                                           ` Rafael J. Wysocki
2011-01-31 19:12                                             ` Rafael J. Wysocki
2011-01-31 20:35                                             ` Ozan Çağlayan
2011-01-31 20:42                                               ` Rafael J. Wysocki
2011-01-31 20:42                                               ` Ozan Çağlayan
2011-01-31 20:42                                                 ` Ozan Çağlayan
2011-01-31 21:04                                                 ` Ozan Çağlayan
2011-01-31 22:52                                                   ` Rafael J. Wysocki
2011-02-03 21:10                                                     ` Ozan Çağlayan
2011-02-03 22:04                                                       ` Rafael J. Wysocki
2011-02-03 22:13                                                         ` Ozan Çağlayan
2011-02-03 22:51                                                           ` Rafael J. Wysocki
2011-02-04  6:44                                                             ` Ozan Çağlayan
2011-02-04  6:44                                                               ` Ozan Çağlayan
2011-02-04 20:36                                                               ` Rafael J. Wysocki
2011-02-05 13:21                                                                 ` Ozan Çağlayan
2011-02-05 18:16                                                                   ` Rafael J. Wysocki
2011-02-05 18:16                                                                     ` Rafael J. Wysocki

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=4D468F1F.8030704@t-online.de \
    --to=r.schtz@t-online.de \
    --cc=colin.king@canonical.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lionel_debroux@yahoo.fr \
    --cc=ozan@pardus.org.tr \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.