[Libva] [Intel-gfx] frequent x crashes with gen6/sna

Daniel Vetter daniel at ffwll.ch
Tue Oct 18 11:47:04 PDT 2011


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:
>  <IRQ>  [<ffffffff8102fcf2>] ? warn_slowpath_common+0x78/0x8c
>  [<ffffffffa0113fd9>] ? i915_vblank_swap+0x6/0x6 [i915]
>  [<ffffffffa010c484>] ? gen6_gt_force_wake_get+0x1f/0x3c [i915]
>  [<ffffffffa01140e2>] ? i915_hangcheck_elapsed+0x109/0x29a [i915]
>  [<ffffffffa0113fd9>] ? i915_vblank_swap+0x6/0x6 [i915]
>  [<ffffffff81039799>] ? run_timer_softirq+0x195/0x222
>  [<ffffffff8103466f>] ? __do_softirq+0x7f/0x106
>  [<ffffffff813b4f2c>] ? call_softirq+0x1c/0x30
>  [<ffffffff81003396>] ? do_softirq+0x31/0x67
>  [<ffffffff810348a0>] ? irq_exit+0x44/0xa5
>  [<ffffffff81015cdd>] ? smp_apic_timer_interrupt+0x85/0x95
>  [<ffffffff813b468b>] ? apic_timer_interrupt+0x6b/0x70
>  <EOI>  [<ffffffff811d5022>] ? intel_idle+0xcd/0xe9
>  [<ffffffff811d4ffe>] ? intel_idle+0xa9/0xe9
>  [<ffffffff812ae307>] ? cpuidle_idle_call+0xa0/0xdb
>  [<ffffffff81000840>] ? cpu_idle+0x52/0x75
>  [<ffffffff81677b60>] ? 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 at ffwll.ch
Mobile: +41 (0)79 365 57 48


More information about the Libva mailing list