From: Michal Feix <michal@feix.cz>
To: linux-kernel@vger.kernel.org
Subject: Kernel stability on baytrail machines
Date: Thu, 03 Mar 2016 17:16:27 +0100 [thread overview]
Message-ID: <606d9b223f3c12775d108b98c4df72ae@feix.cz> (raw)
Hello everyone,
aprox. 6 months ago I started facing random freezes on my baytrail based
computers I manage. It took me a while before I found a bug report in
freedesktop bugzilla named "complete freeze after: drm/i915/vlv: WA for
Turbo and RC6 to work together" -
https://bugs.freedesktop.org/show_bug.cgi?id=88012. It took a few more
months for this bug to escalate into MAJOR importance and was later
moved into kernel bugzilla as "intel_idle.max_cstate=1 required on
baytrail to prevent crashes" -
https://bugzilla.kernel.org/show_bug.cgi?id=109051.
Based on the ammount of comments in both bugtickets and probably
connected observations on different linux distros forums, this seems to
be a showstopper on mainstream Baytrail based machines for many users.
I'm trying to understand, how visible (and thus important) is this
instability across baytrail machines on linux kernel across population.
I do feel that the importance of the mentioned bug is currently
underestimated. Can anyone here give a note, how much current linux
kernel is supposed to be stable on general baytrail machines?
Cheers,
--
Michael
next reply other threads:[~2016-03-03 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 16:16 Michal Feix [this message]
2016-04-09 16:01 ` Pavel Machek
2016-04-09 19:14 ` One Thousand Gnomes
2016-07-12 19:41 ` Ezequiel Garcia
2016-07-12 21:24 ` Pavel Machek
2016-07-13 10:05 ` Michal Feix
2016-07-13 10:48 ` Pavel Machek
2016-07-19 4:51 ` Michal Feix
2016-07-18 13:30 ` One Thousand Gnomes
2016-09-20 13:27 ` Michal Feix
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=606d9b223f3c12775d108b98c4df72ae@feix.cz \
--to=michal@feix.cz \
--cc=linux-kernel@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
Powered by JetHome