Kernel Bug Tracker – Bug 15585
[Bisected Regression in 184.108.40.206] i915 with KMS enabled causes memorycorruption when resuming from suspend-to-disk
Last modified: 2010-10-28 23:31:35 UTC
Subject : [Bisected Regression in 220.127.116.11] i915 with KMS enabled causes memorycorruption when resuming from suspend-to-disk
Submitter : "M. Vefa Bicakci" <firstname.lastname@example.org>
Date : 2010-03-13 5:11
Message-ID : 4B9B1E8F.email@example.com
References : http://marc.info/?l=linux-kernel&m=126845754409543&w=2
This entry is being used for tracking a regression from 2.6.32. Please don't
close it until the problem is fixed in the mainline.
Author: Chris Wilson <firstname.lastname@example.org>
Date: Wed Jan 27 13:36:32 2010 +0000
drm/i915: Selectively enable self-reclaim
First-Bad-Commit : d8e0902806c0bd2ccc4f6a267ff52565a3ec933b
On Sunday 11 April 2010, M. Vefa Bicakci wrote:
> On 08/04/10 07:04 PM, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.32 and 2.6.33.
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.32 and 2.6.33. Please verify if it still should
> > be listed and let the tracking team know (either way).
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15585
> > Subject : [Bisected Regression in 18.104.22.168] i915 with KMS enabled causes memorycorruption when resuming from suspend-to-disk
> > Submitter : M. Vefa Bicakci <email@example.com>
> > Date : 2010-03-13 5:11 (27 days old)
> I tested vanilla 22.214.171.124 and 2.6.34-rc3-git10, and unfortunately
> both of them *have* this issue. So it looks like the issue has not
> been resolved yet. Please keep this regression in the list of known
> Just to let you know: I am currently running 126.96.36.199 with the above-
> mentioned commit reverted, and hibernate-thaw cycles work properly.
Chris, this one is fixed now, right?
Yes after Linus' second patch the storm has quietened down but we nobody has yet managed to explain why...
With great power, comes great responsibility...
Yes, this is fixed with the following two commits by Linus:
Sorry for not updating the bug report.
M. Vefa Bicakci