All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Feix <michal@feix.cz>
To: linux-pm@vger.kernel.org
Subject: intel_idle.max_cstate=1 required on baytrail to prevent crashes
Date: Thu, 17 Mar 2016 08:05:25 +0100	[thread overview]
Message-ID: <56EA5735.1060109@feix.cz> (raw)

Hello everyone,

for the past few months, I'm fighting random hard lock-ups on my
Baytrail machine with different linux kernels. Freezes are quite
frequent, between few minutes to few hours of uptime. According to other
reporters, this was pinpointed as an intel_idle problem on Baytrail. The
bug report originally started as i915 regression at
https://bugs.freedesktop.org/show_bug.cgi?id=88012 and was moved to
kernel Bugzilla few months ago -
https://bugzilla.kernel.org/show_bug.cgi?id=109051

This bug seems to be a serious showstopper for Baytrail users and was
already confirmed by many, but there is no obvious progress on this bug
report for last few months. Meny reporters have confirmed
intel_idle.max_cstate=1 or intel_idle.max_cstate=2 as a half-working
workaround, which makes the interval between freezes on Baytrail longer.

Could someone here please confirm if this is in or out of anyone's
current focus? I strongly believe this is not a minority issue and maybe
this just slipped through meny other important bug reports.

Thank you,

--
Michael

             reply	other threads:[~2016-03-17  7:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17  7:05 Michal Feix [this message]
2016-03-17 14:18 ` intel_idle.max_cstate=1 required on baytrail to prevent crashes Rafael J. Wysocki
2016-03-18 20:32   ` Michal Feix
2016-03-18 21:17     ` 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=56EA5735.1060109@feix.cz \
    --to=michal@feix.cz \
    --cc=linux-pm@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 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.