public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [regression] suspend/resume problemm
Date: Sat, 19 Mar 2011 17:16:05 +0100	[thread overview]
Message-ID: <1300551365.3561.1.camel@mini> (raw)
In-Reply-To: <1bdc18$jtvtq7@fmsmga002.fm.intel.com>

Am Samstag, den 19.03.2011, 10:28 +0000 schrieb Chris Wilson:
> On Sat, 19 Mar 2011 11:19:38 +0100, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> > Hi,
> > i have regression between 2.6.38 and 2.6.38-05646-g08351fc on 945GME.
> > It can suspend but on resume graphic will freeze.
> > I can access the netbook per ssh. Here is the interisting part of log:
> > [  388.392062] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
> > elapsed... GPU hung
> > [  388.392083] [drm] capturing error event; look for more information
> > in /debug/dri/0/i915_error_state
> > [  388.399567] [drm:i915_wait_request] *ERROR* i915_wait_request returns
> > -11 (awaiting 2 at 0, next 3)
> > [  388.399825] [drm:i915_reset] *ERROR* Failed to reset chip.
> > [  388.402142] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
> > 
> > 
> > i915_error_state is in attachment.
> > 
> > Is this regression known? Or should i bisect it?
> 
> No, that's no known. Looks like the GPU was processing commands as
> expected after resume, but the seqno was not updated.
> 
> Try reverting a7a75c8f70d6f6a2f16c9f627f938bbee2d32718 first.

reverting solves this problem. Only error i get is:
[drm:drm_mode_getfb] *ERROR* invalid framebuffer id

      reply	other threads:[~2011-03-19 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19 10:19 [regression] suspend/resume problemm Alexey Fisher
2011-03-19 10:28 ` Chris Wilson
2011-03-19 16:16   ` Alexey Fisher [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=1300551365.3561.1.camel@mini \
    --to=bug-track@fisher-privat.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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