Bug 83699 - [IVB ppgtt]X is sporadical no response and has *ERROR* pin & fence failed
Summary: [IVB ppgtt]X is sporadical no response and has *ERROR* pin & fence failed
Status: CLOSED WONTFIX
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: All Linux (All)
: medium enhancement
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-10 03:32 UTC by lu hua
Modified: 2015-05-13 07:37 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (86.26 KB, text/plain)
2014-09-10 03:32 UTC, lu hua
no flags Details
Xorg.0.log (13.10 KB, text/plain)
2014-09-10 03:33 UTC, lu hua
no flags Details
i915_error_state (2.14 MB, text/plain)
2014-09-10 07:00 UTC, lu hua
no flags Details

Description lu hua 2014-09-10 03:32:40 UTC
Created attachment 106020 [details]
dmesg

System Environment:
--------------------------
Platform: IVB
Libdrm:		(master)libdrm-2.4.56-21-g8c2ae1695913990cbe6c6a8aa294f354eba33bd0
Mesa:		(master)4ea1565bbc49df79d4c39ba5491b0a83c2679a05
server:	(master)xorg-server-1.16.0-152-g3a51418b2db353519a1779cf3cebbcc9afba2520
Xf86_video_intel:(master)2.99.916-2-ge0f7e9fc2f0b39b9e939ff48edea29950f125420
Libva:		(master)e0d25ece01e7aba819c910e98c4fb4706cdab055
Libva_intel_driver:(master)b18479e4fdd7af7cf2840542ef19dbe9114fdeaf
Kernel:   (drm-intel-nightly)4a3d32734bdcef6813b31f06a58430436e98711e

Bug detailed description:
---------------------------
Clean boot system, run xinit, X is no response, screen is black and dmesg reports "*ERROR* pin & fence failed".
Fail rate: 
drm-intel-nightly: 2/10
drm-intel-next-queued: 0/10
drm-intel-fixes: 0/10
drm-fixes: 0/10
drm-next: 0/10

Reproduce steps:
-------------------------
1. clean boot system
2. xinit
Comment 1 lu hua 2014-09-10 03:33:44 UTC
Created attachment 106021 [details]
Xorg.0.log
Comment 2 Chris Wilson 2014-09-10 06:18:28 UTC
You have several GPU hangs during boot... One of those hangs occurs during the modeset which ends up triggering an -EIO and failure.


Can you please attach the error state whilst I try to sell Daniel on the virtues of my patch?
Comment 3 Chris Wilson 2014-09-10 06:42:37 UTC
A bisect would be useful, or you can just try i915.enable_ppgtt=1, or you can try my shotgun at

git://people.freedesktop.org/~ickle/linux-2.6 requests

(i.e. the requests branch and http://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=requests&id=7c7dd4183286496be6c24580b6bf347ba9162d5f in particular)
Comment 4 lu hua 2014-09-10 07:00:11 UTC
Created attachment 106025 [details]
i915_error_state
Comment 5 Chris Wilson 2014-09-10 07:13:38 UTC
Dies inside the first BLT.  The PP_DIR_BASE and GFX_MODE look correct, so the LRI worked correctly. However, ACTHD is looping through a ppgtt that is all zero. A coherency problem? A TLB issue? PDEs?
Comment 6 lu hua 2014-09-10 07:28:37 UTC
(In reply to comment #3)
> A bisect would be useful, or you can just try i915.enable_ppgtt=1, or you
> can try my shotgun at
> 
> git://people.freedesktop.org/~ickle/linux-2.6 requests
> 
> (i.e. the requests branch and
> http://cgit.freedesktop.org/~ickle/linux-2.6/commit/
> ?h=requests&id=7c7dd4183286496be6c24580b6bf347ba9162d5f in particular)

Add i915.enable_ppgtt=1, run 10 cycles, it works well.
About bisect, I am not sure which branch is broken, up to now, I only reproduce it on -nightly branch.
Comment 7 Chris Wilson 2014-09-10 07:40:39 UTC
Don't worry about the bisect, it is pretty clear this is full-ppgtt fallout.
Comment 8 Chris Wilson 2014-09-10 12:12:32 UTC
I tripped over the golden render state, but that should only affect haswell. I haven't had any misfortune with ivb yet.
Comment 9 lu hua 2014-11-07 03:33:47 UTC
# cat /sys/module/i915/parameters/enable_ppgtt
1
Default enable_ppgtt is 1, this issue goes away, decreasing priority.
Comment 10 Jesse Barnes 2015-03-02 21:32:30 UTC
No full PPGTT on pre-gen8.


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.