All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Len Brown <lenb@kernel.org>
Cc: linux-pm <linux-pm@lists.linux-foundation.org>,
	"x86@kernel.org" <x86@kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jiri Slaby <jirislaby@gmail.com>
Subject: Why is max_cstate=1 still needed?
Date: Fri, 11 Mar 2011 13:18:42 +0100	[thread overview]
Message-ID: <4D7A1322.4050706@suse.cz> (raw)

Hello,

there are still reports against the latest kernels, that people need to
pass processor/intel_idle.max_cstate=1 to successfully boot the kernel.
The symptoms are always the same, until the parameter is specified OR
until the user presses a key, the system won't boot up.

This started to appear between 2.6.31 and 2.6.34 (possibly a 2.6.33
regression) and continues to be reported against the latest stable
2.6.37.3. For example:
https://bugzilla.kernel.org/show_bug.cgi?id=15289
https://bugzilla.novell.com/show_bug.cgi?id=579932
https://bugzilla.novell.com/show_bug.cgi?id=673589
https://bugzilla.novell.com/show_bug.cgi?id=675161

I see that there were some fixes in .38-rc in this bug report (they look
unrelated):
https://bugzilla.kernel.org/show_bug.cgi?id=29992

Should they give .38-rc a try?

Any help would be appreciated.

thanks,
-- 
js
suse labs

             reply	other threads:[~2011-03-11 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 12:18 Jiri Slaby [this message]
2011-03-11 14:02 ` Why is max_cstate=1 still needed? Thomas Gleixner
2011-03-11 14:02 ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2011-03-11 12:18 Jiri Slaby

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=4D7A1322.4050706@suse.cz \
    --to=jslaby@suse.cz \
    --cc=jirislaby@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 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.