mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Hugo Mills <hugo-lkml@carfax.org.uk>,
	linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: i915 problems with suspend to disk
Date: Thu, 4 Oct 2012 22:09:59 +0100	[thread overview]
Message-ID: <20121004210959.GJ25498@carfax.org.uk> (raw)
In-Reply-To: <20121004193139.GJ5661@phenom.ffwll.local>

[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]

On Thu, Oct 04, 2012 at 09:31:39PM +0200, Daniel Vetter wrote:
> On Thu, Oct 04, 2012 at 08:20:17PM +0100, Hugo Mills wrote:
> >    On 3.6, I've got a problem with my video driver after resuming from
> > suspend-to-disk: the lower part of the display flickers, rapidly but
> > irregularly (think of a neon sign in a bad film noir), flicking
> > between the correct display and... something else, it's hard to see
> > what.
> > 
> >    Shutting the lid of the machine (to trigger a suspend-to-ram) and
> > waking it up again fixes the flicker.
> > 
> >    In syslogs, I have nothing obvious on suspend, and this warning on
> > resume:
[snip]
> >    Hardware is a Lenovo Thinkpad Edge13, lspci says:
> > 
> > 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
> > 
> > aka
> > 
> > 00:02.0 0300: 8086:2a42 (rev 07)
> > 
> >    Let me know if you need more information. I can probably manage a
> > bisect if necessary -- it's easily repeatable as a bug.
> 
> Before you do a bisect, can you try the drm-intel-fixes branch from
> http://cgit.freedesktop.org/~danvet/drm-intel or a bit more risky, latest
> upstream git? That contains a completely rewritten modeset code, which
> might fix this already. To fix the breakage on 3.6 I guess we need a
> bisect - at least I don't have any idea off-hand what could have gone
> wrong here.

   Thank you for the quick response.

   The drm-intel-fixes branch seems to have done the trick. No more
flickering. I think we can call this one fixed.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
             --- I always felt that as a C programmer, I ---             
                         was becoming typecast.                          

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2012-10-04 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 19:20 Hugo Mills
2012-10-04 19:31 ` Daniel Vetter
2012-10-04 21:09   ` Hugo Mills [this message]

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=20121004210959.GJ25498@carfax.org.uk \
    --to=hugo-lkml@carfax.org.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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

all inboxes | Powered by JetHome®