From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15469] [Intel Graphics HD] Kernel panic on boot with certain BIOS options
Date: Wed, 21 Apr 2010 09:59:48 GMT [thread overview]
Message-ID: <201004210959.o3L9xmwI010064@demeter.kernel.org> (raw)
In-Reply-To: <bug-15469-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=15469
Artem S. Tashkinov <t.artem@mailcity.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |akpm@linux-foundation.org
--- Comment #3 from Artem S. Tashkinov <t.artem@mailcity.com> 2010-04-21 09:59:42 ---
Who else I should subscribe this bug to, so that it was noticed by kernel
developers?
I'm now manually transcribing those screenshots:
EIP: 0060:[<f845ff1b>] EFLAGS: 00010206 CPU: 1
EIP us at drm_mm_search_free+0x6b/0x90 [drm]
EAX: 00002000 EBX: f6798de0 ECX: 00000000 EDX: 00001000
ESI: f76a86c0 EDI: f6d93300 EBP: f6739cec ESP: f6739cc4
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
...
Call Trace:
[<f87519ab>] ? i915_gem_object_bind_to_gtt+0x6b/0x1e0 [i915]
[<f8751ba4>] ? i915_gem_object_pin+0x84/0x90 [i915]
[<f8751c00>] ? i915_gem_init_ringbuffer+0x50/0x460 [i915]
[<f845fe0e>] ? drm_mm_create_tail_node+0x1e/0x70 [drm]
...
Kernel 2.6.34-rc5 is also affected.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
------------------------------------------------------------------------------
--
next prev parent reply other threads:[~2010-04-21 9:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15469-2300@https.bugzilla.kernel.org/>
2010-04-18 11:41 ` [Bug 15469] [Intel Graphics HD] Kernel panic on boot with certain BIOS options bugzilla-daemon
2010-04-21 9:59 ` bugzilla-daemon [this message]
2010-05-05 19:20 ` bugzilla-daemon
2010-05-05 19:47 ` bugzilla-daemon
2010-05-05 20:39 ` bugzilla-daemon
2010-05-08 13:10 ` bugzilla-daemon
2010-05-08 13:40 ` bugzilla-daemon
2010-05-08 21:03 ` bugzilla-daemon
2010-05-09 7:55 ` bugzilla-daemon
2010-05-09 8:49 ` bugzilla-daemon
2010-05-09 21:34 ` bugzilla-daemon
2010-05-10 10:06 ` bugzilla-daemon
2010-05-17 8:29 ` bugzilla-daemon
2010-05-17 14:54 ` bugzilla-daemon
2010-05-17 16:13 ` bugzilla-daemon
2010-05-17 17:27 ` bugzilla-daemon
2010-06-26 22:29 ` bugzilla-daemon
2010-07-05 20:43 ` bugzilla-daemon
2010-07-05 21:01 ` bugzilla-daemon
2010-07-07 21:43 ` bugzilla-daemon
2010-07-08 9:36 ` bugzilla-daemon
2010-07-08 15:59 ` bugzilla-daemon
2010-07-09 5:27 ` bugzilla-daemon
2010-07-09 7:24 ` bugzilla-daemon
2010-07-13 8:33 ` bugzilla-daemon
2010-07-13 15:52 ` bugzilla-daemon
2010-07-23 9:09 ` bugzilla-daemon
2010-07-23 19:36 ` bugzilla-daemon
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=201004210959.o3L9xmwI010064@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox