From: Pavel Machek <pavel@ucw.cz>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
linux-pm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
Michal Feix <michal@feix.cz>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: Kernel stability on baytrail machines
Date: Tue, 12 Jul 2016 23:24:48 +0200 [thread overview]
Message-ID: <20160712212448.GA19237@amd> (raw)
In-Reply-To: <20160712194158.GA4834@laptop>
On Tue 2016-07-12 16:41:58, Ezequiel Garcia wrote:
> Hi Alan,
>
> (Adding interested people to this thread)
>
> On 09 Apr 08:14 PM, One Thousand Gnomes wrote:
> > > > 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?
> > >
> > > If you did not get any replies... you might want to check MAINTAINERS file, and
> > > put Intel x86 maintainers on Cc list.
> > >
> > > I'm sure someone cares :-).
> >
> > Yes we care, and there are people looking at the various reports.
> >
>
> Are there any updates on the status of this issue?
>
> The current bugzilla report [1] marks this as a power management
> issue. However, many reports indicate that it would only freeze
> when running X, so it's not completely clear if it's related to
> the gfx driver too.
Does
"intel_idle.max_cstate=1"
fix it for you?
If you feel it is X-only problem, you may want to provide details
about your graphics subsystem (DRM enabled? framebuffer only?) and
probably cc.
...actually... you may want to verify if it happens in unaccelerated X.
INTEL DRM DRIVERS (excluding Poulsbo, Moorestown and derivative
chipsets)
M: Daniel Vetter <daniel.vetter@intel.com>
M: Jani Nikula <jani.nikula@linux.intel.com>
L: intel-gfx@lists.freedesktop.org
L: dri-devel@lists.freedesktop.org
W: https://01.org/linuxgraphics/
Q: http://patchwork.freedesktop.org/project/intel-gfx/
T: git git://anongit.freedesktop.org/drm-intel
S: Supported
F: drivers/gpu/drm/i915/
F: include/drm/i915*
F: include/uapi/drm/i915_drm.h
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-12 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <606d9b223f3c12775d108b98c4df72ae@feix.cz>
[not found] ` <20160409160119.GA19362@xo-6d-61-c0.localdomain>
[not found] ` <20160409201417.4436d4bd@lxorguk.ukuu.org.uk>
2016-07-12 19:41 ` Kernel stability on baytrail machines Ezequiel Garcia
2016-07-12 21:24 ` Pavel Machek [this message]
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=20160712212448.GA19237@amd \
--to=pavel@ucw.cz \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=michal@feix.cz \
/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;
as well as URLs for NNTP newsgroup(s).