[Bug 52661] New: GPU hang when transferring large files

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Sun Jan 13 14:44:39 PST 2013


https://bugzilla.kernel.org/show_bug.cgi?id=52661

           Summary: GPU hang when transferring large files
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.7
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
        AssignedTo: intel-gfx-bugs at lists.freedesktop.org
        ReportedBy: sudaraka.wijesinghe at gmail.com
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No


Created an attachment (id=91221)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=91221)
lspci output

Every time a large file (i.e 2GB) is transferred from one place to another, GPU
hangs with the following error message.

-- from: journalctl -f --------------------------------------------------------
Jan 13 20:18:11 sw-main kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck
timer elapsed... GPU hung
Jan 13 20:18:12 sw-main kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck
timer elapsed... GPU hung
Jan 13 20:18:12 sw-main kernel: [drm:i915_reset] *ERROR* GPU hanging too fast,
declaring wedged!
Jan 13 20:18:12 sw-main kernel: [drm:i915_reset] *ERROR* Failed to reset chip.
-------------------------------------------------------------------------------

Hardware info of the machine (Acer Aspire 4738) is attached, On another machine
it freezes entirely with attached error log (hp-error.txt)


-- bisect result --------------------------------------------------------------
504c7267a1e84b157cbd7e9c1b805e1bc0c2c846 is the first bad commit
commit 504c7267a1e84b157cbd7e9c1b805e1bc0c2c846
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Thu Aug 23 13:12:52 2012 +0100

    drm/i915: Use cpu relocations if the object is in the GTT but not mappable

    This prevents the case of unbinding the object in order to process the
    relocations through the GTT and then rebinding it only to then proceed
    to use cpu relocations as the object is now in the CPU write domain. By
    choosing to use cpu relocations up front, we can therefore avoid the
    rebind penalty.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

:040000 040000 090ed3d52b4f3210b988877f747b6ff86e123385
1d48be89ded4777a543b693db833de64877059c4 M    drivers
-------------------------------------------------------------------------------

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list