linux-kernel - Re: [BUG] Linux-2.6.33 to 33-git9 intel_drm: drm_fb

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 08 Mar 2010 15:56:16 +0200
From:	Tarkan Erimer <tarkan@...knetserver.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: [BUG] Linux-2.6.33 to 33-git9 intel_drm: drm_fb_helper panic

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
--
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/