From: Daniel Vetter <daniel@ffwll.ch>
To: Nils Radtke <lkml@Think-Future.de>
Cc: linux-kernel@vger.kernel.org,
"Jan Evert van Grootheest (SDG)" <j.e.van.grootheest@caiway.nl>,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference, i915_gem_object_move_to_active
Date: Sat, 8 May 2010 20:04:35 +0200 [thread overview]
Message-ID: <20100508180435.GB17682@viiv.ffwll.ch> (raw)
In-Reply-To: <20100508143213.GB30514@localhost>
On Sat, May 08, 2010 at 04:32:13PM +0200, Nils Radtke wrote:
> This report might actually be related (in fact, same notebook):
>
> http://permalink.gmane.org/gmane.linux.kernel/981318
May be or may not be related. Given that your problem (and the bz entry
I've linked to) are clear kernel bugs, hw (besides the fact that both are
using intel graphics) shouldn't really matter.
> Daniel, I'm not sure I got what you intended to tell me w/:
> > There's a test patch in that bz entry (the one that adds two BUG_ONs).
> > If you're hitting these, is rather likely that it's the same bug.
> bz entry?
> I can't tell whether it's this exact bug. And I'm unfortunately a bit limited
> in using the notebook to test and crash it, it's not mine and therefore not always
> there to play with, if you intended me to apply some patch and test whether the
> notebook will crash at the BUG_ON()s.
I've link the bz entry in my original reply. Anyway, here it is again:
https://bugzilla.kernel.org/show_bug.cgi?id=15664
There's a kernel patch there (the one adding two BUG_ONs, the others are
crap). I've you could apply this and test, that would be great - if you
hit one of these BUG_ONs you've got the same issue with very high
probability. If this is the case, please add yourself to the cc list of
this bug with a "me too" containing some details 'bout your hw + links to
all other preexisting bugs/discussion concerning your problem.
Thanks, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2010-05-08 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 14:32 Nils Radtke
2010-05-08 18:04 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-04 22:22 Nils Radtke
2010-05-05 9:46 ` Jan Evert van Grootheest (SDG)
2010-05-05 13:20 ` Nils Radtke
2010-05-06 22:07 ` Andrew Morton
2010-05-08 13:27 ` Daniel Vetter
2010-05-04 22:51 ` BUG: unable to handle kernel NULL ptr Xorg, scheduling while atomic: Xorg/drm Nils Radtke
2010-05-06 22:07 ` Andrew Morton
2010-05-14 10:27 ` BUG: unable to handle kernel NULL pointer dereference, i915_gem_object_move_to_active Nils Radtke
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=20100508180435.GB17682@viiv.ffwll.ch \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.e.van.grootheest@caiway.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@Think-Future.de \
/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
all inboxes | Powered by JetHome®