From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@gmail.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PULL] drm-intel-fixes
Date: Fri, 8 Aug 2014 13:30:38 -0700 [thread overview]
Message-ID: <CA+55aFyXXyJ1subAWjwv3-yFndRNpUSWLFVb8Aq=NWAS+PXsJQ@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFxb1q9bwdM6_H=ctFHc+4rP4rBuzWMDNXVZwpwf0cN-Bw@mail.gmail.com>
On Fri, Aug 8, 2014 at 12:37 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> The problem seems to exist already with just the plain drm pull from
> Dave. I thought I had tested that, but apparently not.
Still busy bisecting (and it's going into the i915 part of Dave's drm
pull, so the bisect looks sane so far), but in case some i915 person
is trying to think about what it might be, it doesn't seem to be the
backlight per se.
Sometimes it resumes with the backlight on and something showing on
the screen, but no reaction to mouse or keyboard. And in fact, I have
now gotten an X lockup twice *without* doing resume/suspend, so it
seems like the whole resume/suspend thing is just a way to trigger it,
not the fundamental problem.
The machine is alive (the printscreen button takes a screenshot, for
example - I can tell by the sound), but the graphics side is hung.
This is a Sony Vaio Pro 11, so it's bog-standard intel graphics (Haswell ULT).
Linus
next prev parent reply other threads:[~2014-08-08 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 14:34 [PULL] drm-intel-fixes Daniel Vetter
2014-08-08 19:19 ` Linus Torvalds
2014-08-08 19:37 ` Linus Torvalds
2014-08-08 20:30 ` Linus Torvalds [this message]
2014-08-08 20:52 ` Linus Torvalds
2014-08-08 22:07 ` Linus Torvalds
2014-08-09 8:44 ` Daniel Vetter
2014-08-17 14:08 ` Jiri Kosina
[not found] <20120605191853.GD4704@phenom.ffwll.local>
2012-06-05 19:18 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2012-05-07 8:43 Daniel Vetter
2012-05-03 15:44 Daniel Vetter
2012-03-14 18:30 Keith Packard
2012-02-09 21:30 Keith Packard
2012-01-25 20:12 Keith Packard
2011-11-19 6:54 Keith Packard
2011-06-05 5:48 Keith Packard
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='CA+55aFyXXyJ1subAWjwv3-yFndRNpUSWLFVb8Aq=NWAS+PXsJQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).