From: Jesse Barnes <jesse.barnes@intel.com>
To: Soren Hansen <soren@ubuntu.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] don't suspend/resume 8xx chips
Date: Mon, 5 May 2008 15:07:55 -0700 [thread overview]
Message-ID: <200805051507.55375.jesse.barnes@intel.com> (raw)
In-Reply-To: <20080327083835.GF30926@butch.linux2go.dk>
On Thursday, March 27, 2008 1:38 am Soren Hansen wrote:
> 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, can you give the current DRM tree a try or apply the patch in
http://cgit.freedesktop.org/mesa/drm/commit/?id=cb33133ef354b77a8cf06b16ce95a0babbe8bc6f?
I'm hoping it'll fix the one machine that had a problem and not break the
other. :) I tested it on my new 855 machine and it fixes things here...
Thanks,
Jesse
next prev parent reply other threads:[~2008-05-05 22:08 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
2008-05-05 22:07 ` Jesse Barnes [this message]
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=200805051507.55375.jesse.barnes@intel.com \
--to=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=soren@ubuntu.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 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.