xorg-dev + intel driver + KMS

[Andrey Kosachenko]

On 04.09.2011 18:46, Kostik Belousov wrote:
> Show me the output of procstat -kk<Xorg pid>  and ps axlww.

I believe you are interested in those listing in the context of the 
hanged Xorg, right?. If so, then I've to wait for the next issue 
occurrence and will provide outputs then.

though (just in case) current listings are:
ps axlww: http://pastebin.com/eTccAM0q
procstat -kk: http://pastebin.com/TfEWLkfm

>> I've collected ktrdump output. It is quite large (~500k after
>> compression), so I'll send it to you off-list.
> There is no gpu hang, right ?

Well, honestly speaking I'm not sure how to detect "gpu hang" phenomena.
Wiki states the following:
--
"In the case of GPU hang or error, the GPU dump is available at 
hw.dri.0.info.i915_error_state."
--

so given that in my case it was:
--
hw.dri.0.info.i915_error_state: no error state collected
--
the implication is gpu didn't hang.



Not sure whether it can be useful but still: when Xorg is operating 
normally there is a bunch of records like
--
Sep  4 17:00:42 beastie kernel: [drm:KMS:pid1650:intel_crtc_cursor_set]
Sep  4 17:00:42 beastie kernel: [drm:KMS:pid1650:intel_crtc_cursor_set] 
cursor off
Sep  4 17:00:42 beastie kernel: [drm:KMS:pid1650:intel_crtc_cursor_set]
Sep  4 17:01:02 beastie kernel: [drm:KMS:pid1650:intel_crtc_cursor_set]
Sep  4 17:01:02 beastie kernel: [drm:KMS:pid1650:intel_crtc_cursor_set] 
cursor off
--
which appear quite often (several records per minute). After Xorg stuck 
I could not find any of them until the next boot.

--
WBR,
Andrey Kosachenko