public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>, dri-devel@lists.freedesktop.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Airlie <airlied@linux.ie>,
	rjw@sisk.pl, davej@redhat.com
Subject: Re: hibernate random memory corruption, workaround i915.modeset=0
Date: Mon, 19 Mar 2012 10:21:28 -0700	[thread overview]
Message-ID: <86r4wobj6v.fsf@sumi.keithp.com> (raw)
In-Reply-To: <20120319145349.GG6169@redhat.com>

<#part sign=pgpmime>
On Mon, 19 Mar 2012 15:53:54 +0100, Stanislaw Gruszka <sgruszka@redhat.com> wrote:

> Keith, is there a chance that this bug can be fixed by i915 team?

Yes, I'm working on figuring out how to actually reproduce this and then
work on a few work-arounds.

> If not, can we disable hibernate on i915 with modeset=1 and add
> module option, which enable it for those who want to risk?

I'd love to know if disabling modeset on just the booting kernel helps;
leaving the resuming kernel with modeset=1. I haven't been able to
reproduce this locally yet to test this theory though.

-- 
keith.packard@intel.com

  reply	other threads:[~2012-03-19 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 12:42 hibernate random memory corruption, workaround i915.modeset=0 Stanislaw Gruszka
2012-03-19 14:53 ` Stanislaw Gruszka
2012-03-19 17:21   ` Keith Packard [this message]
2012-03-21 15:14     ` Stanislaw Gruszka
2012-03-21 15:43       ` Dave Airlie
     [not found] <iz8bE-3ij-7@gated-at.bofh.it>
     [not found] ` <iGMdX-6N4-9@gated-at.bofh.it>
     [not found]   ` <iGOz9-2vm-19@gated-at.bofh.it>
     [not found]     ` <iHvuq-7MF-25@gated-at.bofh.it>
2012-03-21 18:15       ` Andreas Hartmann

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=86r4wobj6v.fsf@sumi.keithp.com \
    --to=keithp@keithp.com \
    --cc=airlied@linux.ie \
    --cc=davej@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=sgruszka@redhat.com \
    /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