[BISECTED] Re: [BUG] Linux-2.6.33 to 33-git9 intel_drm: drm_fb_helperpanic

From: Tarkan Erimer
Date: Wed Mar 10 2010 - 10:25:24 EST


On 03/08/2010 03:56 PM, Tarkan Erimer wrote:
On 03/04/2010 04:34 PM, Tarkan Erimer wrote:
When I booted into 2.6.33, hard lock up occurs via the following error
message at boot time :

[drm:drm_fb_helper_panic] *ERROR* panic occured, switching back to text
console
BUG: scheduling while atomic: init/1/0x00000002

This is a KMS enabled kernel on i945 VGA. Also, I tried (I found after
googling a bit.) with "i915.modeset=0 enable_mtrr_cleanup" and
"enable_mtrr_cleanup" kernel boot options. But, still the same error
occurs.

This bug occurs on kernels from 2.6.33 to 2.6.33-git9. 2.6.33-rc8 works
fine. My .config attached.

Tarkan

Anybody care to look at this issue ? BTW; it, still, exist (tested few
mins ago.) on .33-git14, too.

Tarkan


Today, I bisected to find out the bad commit. Here is what I found :

83d90addc829ab56ace49b10fd7d5d415448aac4 is the first bad commit

commit 83d90addc829ab56ace49b10fd7d5d415448aac4
Merge: 75ef7cd 79da064
Author: Linus Torvalds<torvalds@xxxxxxxxxxxxxxxxxxxx>
Date: Wed Feb 24 07:42:42 2010 -0800

Merge branch 'for-linus' of git://git.kernel.dk/linux-2.6-block

* 'for-linus' of git://git.kernel.dk/linux-2.6-block:
Revert "block: improve queue_should_plug() by looking at IO depths"



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/