All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bojan Smojver <bojan@rexursive.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Memory corruption on hibernate/thaw with KMS
Date: Mon, 03 Oct 2011 17:44:26 +1100	[thread overview]
Message-ID: <1317624267.1959.13.camel@shrek.rexursive.com> (raw)
In-Reply-To: <1317103928.1981.5.camel@shrek.rexursive.com>

On Tue, 2011-09-27 at 16:12 +1000, Bojan Smojver wrote:
> This problem is covered by various bugs, one of them being:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=37142
> 
> At some point there was a "solution" to essentially the same bug (I
> believe http://bugzilla.kernel.org/show_bug.cgi?id=13811), but the
> problem quickly resurfaced.
> 
> There are also similar bugs in the Free Desktop bug database. For
> instance:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=40241
> 
> Does anyone have any idea what's causing this? Or better, how to fix it?
> I can confirm that as of kernel 3.1.0-rc7 this is still a problem.

OK, given that nobody knows what the cause/fix is for this, can anyone
confirm that they can reproduce this on their system with Intel
graphics?

For me, this occurs after several hibernate/thaw cycles on my ThinkPad
T510 when KMS is in use.

-- 
Bojan

  parent reply	other threads:[~2011-10-03  6:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27  6:12 Memory corruption on hibernate/thaw with KMS Bojan Smojver
2011-09-29 23:38 ` Bojan Smojver
2011-10-03  6:44 ` Bojan Smojver [this message]
2011-10-04  2:32   ` Eugeni Dodonov
2011-10-04  2:46     ` Bojan Smojver
2011-10-04  3:21       ` Bojan Smojver
2011-10-10  7:15 ` Bojan Smojver
2011-10-10  7:53   ` Daniel Vetter
2011-10-10  8:18     ` Bojan Smojver
2011-10-10 10:05       ` Bojan Smojver
2011-10-10 10:12         ` Bojan Smojver
2011-10-10 10:37           ` Bojan Smojver
2011-10-10 11:23             ` Bojan Smojver
2011-10-11  9:29               ` Daniel Vetter
2011-10-11  9:42                 ` Bojan Smojver
2011-10-11 11:02                   ` Bojan Smojver
2011-10-11 11:22                     ` Daniel Vetter
2011-10-11 11:31                       ` Daniel Vetter
2011-10-11 12:25                         ` Bojan Smojver
2011-10-12  1:38                         ` Bojan Smojver
2011-10-14  1:14                         ` Bojan Smojver
2011-10-14  1:29                         ` Bojan Smojver
2011-10-11 12:24                       ` Bojan Smojver
2011-10-11 15:51                         ` Eugeni Dodonov
2011-10-11 16:13                           ` Daniel Vetter
2011-10-12  3:09                       ` Bojan Smojver
2011-10-12 22:16                         ` Bojan Smojver
2011-10-26  3:44                         ` Bojan Smojver
2011-10-11  9:55                 ` Bojan Smojver
2011-10-11 10:39                   ` Daniel Vetter
2011-10-11 10:41                     ` Bojan Smojver
2011-10-10  8:01 ` Bojan Smojver
2011-10-14  1:02 ` Bojan Smojver
2011-10-14  1:39   ` Bojan Smojver
2011-10-14  2:01     ` Bojan Smojver

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=1317624267.1959.13.camel@shrek.rexursive.com \
    --to=bojan@rexursive.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.