From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Slusarz Subject: Re: drm/nouveau: crash regression in 3.5 Date: Mon, 30 Jul 2012 19:16:29 +0200 Message-ID: <20120730171629.GA3271@joi.lan> References: <500D916A.60703@odi.ch> <20120724170002.GA3129@joi.lan> <500ED9EC.5040309@odi.ch> <20120724205746.GA8707@joi.lan> <500FB279.1020904@odi.ch> <20120725184205.GA3119@joi.lan> <50113E76.9090706@odi.ch> <20120729201532.GA3566@joi.lan> <50166D15.7090305@odi.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <50166D15.7090305@odi.ch> Sender: linux-kernel-owner@vger.kernel.org To: Ortwin =?utf-8?B?R2zDvGNr?= Cc: linux-kernel@vger.kernel.org, bskeggs@redhat.com, dri-devel@lists.freedesktop.org, airlied@redhat.com List-Id: dri-devel@lists.freedesktop.org On Mon, Jul 30, 2012 at 01:16:37PM +0200, Ortwin Gl=C3=BCck wrote: > On 29.07.2012 22:15, Marcin Slusarz wrote: > > No, the real problem is: with "noaccel" we don't register "software= engine", > > but vblank ISR relies on its existance and happily derefences NULL = pointer. > > > > Now, this patch should fix it for real... >=20 > Unfortunately I am still seeing the crash. Without "noaccel" it works= though=20 > (until X crashes the machine, but that is a different thing). Are you sure you boot the correct kernel? I'm asking because your panic= says its version is "3.5.0 #3" - exactly the same as in previous crash log. Marcin