From: Tarkan Erimer <tarkan@turknetserver.com>
To: linux-kernel@vger.kernel.org
Subject: [BISECTED] Re: [BUG] Linux-2.6.33 to 33-git9 intel_drm: drm_fb_helper panic
Date: Wed, 10 Mar 2010 17:25:12 +0200 [thread overview]
Message-ID: <4B97B9D8.6050103@turknetserver.com> (raw)
In-Reply-To: <4B950200.4000305@turknetserver.com>
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@linux-foundation.org>
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"
prev parent reply other threads:[~2010-03-10 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 14:34 [BUG] Linux-2.6.33 to 33-git9 intel_drm: drm_fb_helper panic Tarkan Erimer
2010-03-08 13:56 ` Tarkan Erimer
2010-03-10 15:25 ` Tarkan Erimer [this message]
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=4B97B9D8.6050103@turknetserver.com \
--to=tarkan@turknetserver.com \
--cc=linux-kernel@vger.kernel.org \
/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.