public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [Regression + patch] i915 / PM: System resume broken on 945GM
Date: Wed, 11 Apr 2012 16:01:06 -0700	[thread overview]
Message-ID: <20120411230106.GA4694@kroah.com> (raw)
In-Reply-To: <201204120056.49066.rjw@sisk.pl>

On Thu, Apr 12, 2012 at 12:56:48AM +0200, Rafael J. Wysocki wrote:
> Hi,
> 
> On Thursday, April 12, 2012, Greg Kroah-Hartman wrote:
> > On Thu, Apr 12, 2012 at 12:12:46AM +0200, Rafael J. Wysocki wrote:
> > > Hi Chris,
> > > 
> > > Unfortunately, your commit
> > > 
> > > commit 7dd4906586274f3945f2aeaaa5a33b451c3b4bba
> > > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > > Date:   Wed Mar 21 10:48:18 2012 +0000
> > > 
> > >     drm/i915: Mark untiled BLT commands as fenced on gen2/3
> > > 
> > > breaks system resume on my Toshiba Portege R500 (945GM) which hangs hard
> > > during or right after returning to X.
> > 
> > Luckily this patch didn't apply properly to the 3.3-stable tree :)
> 
> Your box hanged during resume from suspend with it IIRC, though, or was that
> a different issue?

Different issue, that was fixed by
dba69d1092e291e257fb5673a3ad0e4c87878ebc (x86, kvm: Call
restore_sched_clock_state() only after %gs is initialized), which went
into Linus's tree right after 3.4-rc1 was out.  All is good in 3.4-rc2
for me, thankfully.

thanks,

greg k-h

  reply	other threads:[~2012-04-11 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 22:12 [Regression + patch] i915 / PM: System resume broken on 945GM Rafael J. Wysocki
2012-04-11 22:20 ` Greg Kroah-Hartman
2012-04-11 22:56   ` Rafael J. Wysocki
2012-04-11 23:01     ` Greg Kroah-Hartman [this message]
2012-04-11 22:33 ` Woody Suwalski

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=20120411230106.GA4694@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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