linux-kernel - Re: BUG: unable to handle kernel NULL pointer dereference, i915_gem_object_move_to

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20100508180435.GB17682@viiv.ffwll.ch>
Date:	Sat, 8 May 2010 20:04:35 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	Nils Radtke <lkml@...nk-Future.de>
Cc:	linux-kernel@...r.kernel.org,
	"Jan Evert van Grootheest (SDG)" <j.e.van.grootheest@...way.nl>,
	dri-devel@...ts.freedesktop.org, Daniel Vetter <daniel@...ll.ch>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference,
 i915_gem_object_move_to_active

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@...ll.ch
Mobile: +41 (0)79 365 57 48
--
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/