| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 5 May 2008 15:07:55 -0700 From: Jesse Barnes <jesse.barnes@...el.com> To: Soren Hansen <soren@...ntu.com> Cc: lkml <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] don't suspend/resume 8xx chips 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists