On Wed, 15 Dec 2010 11:14:53 +0800, Zhenyu Wang zhen...@linux.intel.com wrote:
Chris, just notice you removed pipe control notify entirely on -next,
that seems wrong to me. In Ironlake time, we've seen interrupt stall issue
with user interrupt, and be warned user interrupt is deprecated, so
On 2010.12.15 10:05:01 +, Chris Wilson wrote:
On Wed, 15 Dec 2010 11:14:53 +0800, Zhenyu Wang zhen...@linux.intel.com
wrote:
Chris, just notice you removed pipe control notify entirely on -next,
that seems wrong to me. In Ironlake time, we've seen interrupt stall issue
with user
On 2010/12/16 9:59, Zhenyu Wang wrote:
On 2010.12.15 10:05:01 +, Chris Wilson wrote:
On Wed, 15 Dec 2010 11:14:53 +0800, Zhenyu Wangzhen...@linux.intel.com wrote:
Chris, just notice you removed pipe control notify entirely on -next,
that seems wrong to me. In Ironlake time, we've seen
Chris, just notice you removed pipe control notify entirely on -next,
that seems wrong to me. In Ironlake time, we've seen interrupt stall issue
with user interrupt, and be warned user interrupt is deprecated, so we moved
on to use pipe control notify, although there's a workaround later covered
Yeah, I also met this issue, and bisection point to this as well :)
32402 https://bugs.freedesktop.org/show_bug.cgi?id=32402 19:05:15
cri hig ch...@chris-wilson.co.uk shuang...@intel.com NEW
[piketon -next bisected] Many tests make GPU hang and reset
Thanks
--Shuang
On
