Kernel Bug Tracker – Bug 27672
[BUG] 2.6.38-rc1-git1: hard lockup related to i915 / automated cgroup scheduling
Last modified: 2011-02-01 10:44:54 UTC
Subject : [BUG] 2.6.38-rc1-git1: hard lockup related to i915 / automated cgroup scheduling
Submitter : Knut Petersen <Knut_Petersen@t-online.de>
Date : 2011-01-20 17:29
Message-ID : 4D387109.firstname.lastname@example.org
References : http://marc.info/?l=linux-kernel&m=129554559122704&w=2
This entry is being used for tracking a regression from 2.6.37. Please don't
close it until the problem is fixed in the mainline.
Ah, I thought there was another issue with X left unresolved.
Indeed. The original report was about a hard freeze and the issue solved by the above Patch was only _thought_ to be related.
Ignore-Patch : http://git.kernel.org/?p=linux/kernel/git/ickle/drm-intel.git;a=commit;h=d121a5d2a098ba6dd033dd195f5ccbf7558c37b6
I think this is related to bug 27862 and the same 3 patches (drm-intel-fixes 9334ef755f060e251f3f395caeda1a58b6834ea3 and ddx 3e28a0c0b43823d3104fe8fc50b5994b41fc0cc1 c6dc27562abbc8ca9e873ad502ca49ae010461d2).
Author: Chris Wilson <email@example.com>
Date: Fri Jan 28 11:53:03 2011 +0000
drm: Don't switch fb when disabling an output
In drm_crtc_helper_set_config, we call drm_crtc_helper_set_mode which
may return early and do no operation if the crtc is to be disabled. In
this case we merrily swap to the new fb, discarding the old_fb believing
that it has been cleaned up. However, due to the early return, the
old_fb was not presented to the backend for correct reaping, and nor was
the new one - which is about to be reaped via the
drm_helper_disable_unused_functions(), leading to incorrect refcounting
of the pinned objects.
Tested-by: Takashi Iwai <firstname.lastname@example.org>
Signed-off-by: Chris Wilson <email@example.com>
*** This bug has been marked as a duplicate of bug 27862 ***