[Bug 52311] New: Flash 11.5 video hangs ivy bridge

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Fri Jan 4 10:09:59 PST 2013


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

           Summary: Flash 11.5 video hangs ivy bridge
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.8-rc2
          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: haagch.christoph at googlemail.com
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No


Created an attachment (id=90481)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=90481)
full dmesg with hang at the end

Software: linux 3.8-rc2, the problem also occured in rc1. In 3.7 it does NOT
hang.
mesa/xf86-video-intel are the latest from git master, I'm also using sna
Hardware: i7 3632qm

Unfortunately I have only been able to trigger this bug with flash 11.5 but
fortunately it always happens immediately so it's easy to reproduce.

Steps:
Use google chrome / chromium with pepper flash
Watch a flash video (e.g. from youtube) / try to put it on fullscreen

Without compositing: As soon as the video starts the hang occurs
With compositing (kwin 4.10 beta, opengl): The video plays fine, but as soon as
I put it on fullscreen the hang occurs.

Maybe I'll write this snippet from dmesg directly here so it's easier to find
with google (I have not found that exact problem):

[ 1424.837260] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU
hung
[ 1424.837270] [drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[ 1424.842657] [drm:kick_ring] *ERROR* Kicking stuck wait on render ring

The rest is hopefully clear from the attached files.

-- 
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