Bug 43852 - [IVB] avcenc cannot work with the latest libva driver
Summary: [IVB] avcenc cannot work with the latest libva driver
Status: VERIFIED FIXED
Alias: None
Product: libva
Classification: Unclassified
Component: intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: haihao
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-15 00:46 UTC by cc
Modified: 2011-12-15 22:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description cc 2011-12-15 00:46:37 UTC
I try to test encoding with the latest driver but failed,I paste the error info as follows:

[drm:i915_driver_open], 
------------[ cut here ]------------
WARNING: at drivers/gpu/drm/i915/i915_drv.c:354 gen6_gt_force_wake_get+0x27/0x45 [i915]()
Hardware name: 2012 Client Platform
Modules linked in: sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter iptable_filter ip6_tables ip_tables x_tables dm_mirror dm_region_hash dm_log mcs7830 usbnet mii snd_hda_codec_realtek snd_hda_intel snd_hda_codec e1000e snd_hwdep snd_seq snd_seq_device snd_pcm sg snd_timer snd soundcore pcspkr microcode iTCO_wdt iTCO_vendor_support i2c_i801 snd_page_alloc shpchp ipv6 autofs4 ext3 jbd mbcache sd_mod firewire_ohci firewire_core crc_itu_t ehci_hcd i915 drm_kms_helper drm i2c_algo_bit button i2c_core video dm_mod [last unloaded: scsi_wait_scan]
Pid: 0, comm: swapper Tainted: G        W   3.1.0_unstable_20111213+ #1
Call Trace:
 <IRQ>  [<ffffffff8103c250>] warn_slowpath_common+0x80/0x98
 [<ffffffff8103c27d>] warn_slowpath_null+0x15/0x17
 [<ffffffffa008172a>] gen6_gt_force_wake_get+0x27/0x45 [i915]
 [<ffffffffa0081806>] i915_read32+0x2f/0x90 [i915]
 [<ffffffffa0088590>] i915_hangcheck_elapsed+0xc4/0x1f4 [i915]
 [<ffffffff81048cfe>] run_timer_softirq+0x202/0x2cb
 [<ffffffffa00884cc>] ? i915_driver_irq_handler+0x4c3/0x4c3 [i915]
 [<ffffffff8105f488>] ? ktime_get+0x5f/0xb5
 [<ffffffff81041fe0>] __do_softirq+0xc2/0x182
 [<ffffffff8105aab4>] ? hrtimer_interrupt+0x10d/0x19f
 [<ffffffff813b92ec>] call_softirq+0x1c/0x30
 [<ffffffff8100395b>] do_softirq+0x33/0x68
 [<ffffffff81041d58>] irq_exit+0x44/0x9e
 [<ffffffff810198c3>] smp_apic_timer_interrupt+0x86/0x94
 [<ffffffff813b7e0b>] apic_timer_interrupt+0x6b/0x70
 <EOI>  [<ffffffff8105b438>] ? __hrtimer_start_range_ns+0x352/0x364
 [<ffffffff8123edb7>] ? acpi_idle_enter_bm+0x221/0x255
 [<ffffffff8123edb2>] ? acpi_idle_enter_bm+0x21c/0x255
 [<ffffffff812ef613>] cpuidle_idle_call+0x119/0x1d1
 [<ffffffff81001d68>] cpu_idle+0x5e/0x9f
 [<ffffffff8139c739>] rest_init+0x6d/0x6f
 [<ffffffff8167fb7d>] start_kernel+0x32f/0x33a
 [<ffffffff8167f2a8>] x86_64_start_reservations+0xb8/0xbc
 [<ffffffff8167f399>] x86_64_start_kernel+0xed/0xf4
---[ end trace c9b4bfcf5e07da1f ]---
------------[ cut here ]------------

=====================
Environment:
libva: 
commit 4aeaa296febf2f71200ff30380902e2c80cbf679
Author: Xiang, Haihao <haihao.xiang@intel.com>
Date:   Thu Nov 10 13:19:33 2011 +0800

intel-driver:
commit 62154620aacab804dd697f7a9f5e1dd2766a1f8a
Author: Xiang, Haihao <haihao.xiang@intel.com>
Date:   Thu Nov 24 14:21:03 2011 +0800

=====================
Reproduce steps:
1. xinit&
2. check to vaapi-ext branch and install libva  
3. ./avcenc 720 480 iceage_720x480_491.yuv /tmp/1.264 fb=10000 mode=1
Comment 1 haihao 2011-12-15 17:35:21 UTC
This issue has been fixed. However the result is wrong.  It works well on master so it is regression on vaapi-ext branch. Could you help to bisect it to find the bad commit?
Comment 2 haihao 2011-12-15 21:59:32 UTC
The wrong result issue is also fixed
Comment 3 cc 2011-12-15 22:11:33 UTC
On the vaapi-ext branch ,the avcenc can work now.

using intel-driver commit :
commit b519b78479ae10dddab17d3d482452b0eb07fa0c
Author: Xiang, Haihao <haihao.xiang@intel.com>
Date:   Fri Dec 16 13:38:32 2011 +0800


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.