From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Pavel Machek <pavel@ucw.cz>, Michal Feix <michal@feix.cz>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: Kernel stability on baytrail machines
Date: Mon, 18 Jul 2016 14:30:03 +0100 [thread overview]
Message-ID: <20160718143003.3477c0bc@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20160712194158.GA4834@laptop>
On Tue, 12 Jul 2016 16:41:58 -0300
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> 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.
There are two things we are currently tracking. One of them was merged
which seems to have made my machine stable at least and fixes a problem
related to the MMC. The second one we may need is a power related changed
to SPI to hold the CPU in C0/C1 whenever the ACPI _SEM is held.
Graphics shows these problems up because of the way the GPU causes power
state changes.
Alan
next prev parent reply other threads:[~2016-07-18 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 16:16 Michal Feix
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 [this message]
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=20160718143003.3477c0bc@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=michal@feix.cz \
--cc=pavel@ucw.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
Powered by JetHome