From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: frequent x crashes with gen6/sna Date: Tue, 18 Oct 2011 20:47:04 +0200 Message-ID: <20111018184704.GA2914@phenom.ffwll.local> References: <20111017202009.183480@gmx.net> <20111017204632.GL2971@phenom.ffwll.local> <20111018075232.25960@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20111018075232.25960@gmx.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Dieter Mummenschanz Cc: intel-gfx@lists.freedesktop.org, libva@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Tue, Oct 18, 2011 at 09:52:32AM +0200, Dieter Mummenschanz wrote: > I've installed your libva patch: > > libva: libva version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/local/lib/dri/i965_drv_video.so > libva: va_openDriver() returns 0 > vainfo: VA API version: 0.32 > vainfo: Driver version: Intel i965 driver - 1.0.15.pre1 > > No Changes. With iommu switched off there are less frequent hangs but there still are :-(. dmesg shows: > > WARNING: at drivers/gpu/drm/i915/i915_drv.c:354 gen6_gt_force_wake_get+0x1f/0x3c [i915]() > Hardware name: 4236NGG > Modules linked in: snd_hda_codec_conexant fbcon font bitblit softcursor i915 thinkpad_acpi nvram drm_kms_helper drm fb fbdev cfbcopyarea video iwlagn backlight cfbimgblt cfbfillrect e1000e snd_hda_intel snd_hda_codec intel_agp intel_gtt agpgart > Pid: 0, comm: swapper Not tainted 3.1.0-rc4+ #1 > Call Trace: > [] ? warn_slowpath_common+0x78/0x8c > [] ? i915_vblank_swap+0x6/0x6 [i915] > [] ? gen6_gt_force_wake_get+0x1f/0x3c [i915] > [] ? i915_hangcheck_elapsed+0x109/0x29a [i915] > [] ? i915_vblank_swap+0x6/0x6 [i915] > [] ? run_timer_softirq+0x195/0x222 > [] ? __do_softirq+0x7f/0x106 > [] ? call_softirq+0x1c/0x30 > [] ? do_softirq+0x31/0x67 > [] ? irq_exit+0x44/0xa5 > [] ? smp_apic_timer_interrupt+0x85/0x95 > [] ? apic_timer_interrupt+0x6b/0x70 > [] ? intel_idle+0xcd/0xe9 > [] ? intel_idle+0xa9/0xe9 > [] ? cpuidle_idle_call+0xa0/0xdb > [] ? cpu_idle+0x52/0x75 > [] ? start_kernel+0x401/0x40c We already know about this backtrace. It's a possible sideffect of a overloaded/dying gpu, but unrelated to the bug at hand. > In this special case the gpu was successfully reset and continued normally. > > Any other ideas? Not at the moment, unfortunately. Can you please report a bug against libva with a small summary of all the things we've already discussed here? Also please add a error_state with my patches applied. And don't forget to put me on cc and post the bug # here in this thread. Yours, Daniel -- Daniel Vetter Mail: daniel@ffwll.ch Mobile: +41 (0)79 365 57 48