[Bug 63921] [snb] GTT mapping fails after GPU hang

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=63921

--- Comment #2 from Nicolas Hillegeer <nicolashillegeer at gmail.com> ---
(In reply to comment #1)
> If you can grab the i915_error_state (kill X, kill everything, and try
> again) file a bug against libva for causing the GPU hang. However, I blame
> Daniel for never believing me when I sent patches to prevent this... :-p

At the bottom of my original bug report I had already mentioned that I never
got anything substantial out of the i915_error_log. I'll try again on the next
crash, but last time I went so far as to kill apache, mongodb, fluentd, sshd,
rpcbind, ... basically anything I could get my hands on (trust me the process
list was really small after that, memory usage below 100 MB according to htop),
and still it told me it had insufficient memory. Is there anything special I
could try? Btw X kills itself after that error, no need to kill it twice.

The unit only reports having about 1.8GB of memory (should be 2GB but hey...).
Does the unit just have too little memory for a good crash report? Is there
maybe something I can use to force linux to flush everything? I have to admit I
don't really know how gem/dri/"the driver" tries to allocate that buffer.

Should I report to the libva list regardless of getting a good i915_error_state
trace?

It's a bit heartening to know that you at least seem to be aware that this
could be an issue! Were my suspicions correct about it not releasing GPU memory
or is it something else entirely? No need for a big explanation, I guess I'm
just curious :)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130425/5ea181f3/attachment.html>