public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soren Hansen <soren@ubuntu.com>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Airlie <airlied@linux.ie>
Subject: Re: [PATCH] don't suspend/resume 8xx chips
Date: Thu, 27 Mar 2008 09:38:36 +0100	[thread overview]
Message-ID: <20080327083835.GF30926@butch.linux2go.dk> (raw)
In-Reply-To: <200803261628.12336.jesse.barnes@intel.com>

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

On Wed, Mar 26, 2008 at 04:28:12PM -0700, Jesse Barnes wrote:
> Recent testing has turned up some bugs in the new Intel suspend/resume code 
> for old, 8xx chipsets.  So for 2.6.25 it probably makes sense to apply this 
> patch, which should prevent the new code from getting called on those 
> chipsets.  We should have this fixed soon, but not in time for 2.6.25 
> unfortunately.  Note that this patch (along with the suspend/resume code in 
> general) could use more testing.

I've tested this patch on two different laptops: A Uniwill 223 and an
IBM Thinkpad X40. Both have Intel 855 graphics. The former now suspends
and hibernates just fine (it fails without the patch). The latter works
both with and without the patch.

-- 
Soren Hansen               | 
Virtualisation specialist  | Ubuntu Server Team
Canonical Ltd.             | http://www.ubuntu.com/

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

  reply	other threads:[~2008-03-27  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 23:28 [PATCH] don't suspend/resume 8xx chips Jesse Barnes
2008-03-27  8:38 ` Soren Hansen [this message]
2008-05-05 22:07   ` Jesse Barnes
2008-03-28 14:40 ` Pavel Machek
2008-03-28 20:13   ` Jesse Barnes

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=20080327083835.GF30926@butch.linux2go.dk \
    --to=soren@ubuntu.com \
    --cc=airlied@linux.ie \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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