mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Display glitching (and possibly related lockup) in 3.16-rc1?
Date: Thu, 19 Jun 2014 18:09:46 +0200	[thread overview]
Message-ID: <20140619160946.GX5821@phenom.ffwll.local> (raw)
In-Reply-To: <nsxppi6tcsg.fsf@closure.thunk.org>

On Wed, Jun 18, 2014 at 12:14:55PM -0400, Theodore Ts'o wrote:
> Is this a known problem?
> 
> On my T540p, occasionally the display will go black and then be
> completely locked.  One time when this happened, the display started
> glitching and tearing (like what you might see if an analog display had
> a loose connector and it was being wiggled) when the system locked up,
> but the at least 75% of the time when the bug manifests, the screen goes
> black instead.
> 
> This appears to only happen when the system is running on battery --- it
> doesn't seem to manifest if I'm plugged into the AC mains.  And I've
> been typing an e-mail message when the system locks up, so I don't think
> it's related to DPMS or the screen saver kicking in.
> 
> I can try to bisect this regression (3.15 didn't have this problem), but
> I thought I would ask first if this was a known problem.   I don't know
> for certain that it's an i915 bug, but the symptoms do somewhat point in
> that direction, especially the display glitches.

Doesn't ring a bell, but can you please boot with drm.debug=0xe and attach
dmesg here so we know what kind of hardware you have? Also any dying
breadths over netconsole or similar? Can't hurt to check that before doing
the bisect.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-06-19 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 16:14 Theodore Ts'o
2014-06-19 16:09 ` Daniel Vetter [this message]
2014-06-19 21:59   ` [Intel-gfx] " Dave Airlie

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=20140619160946.GX5821@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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

all inboxes | Powered by JetHome®