From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 81644] Random crashes on RadeonSI with Chromium. Date: Tue, 05 Aug 2014 15:47:48 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0329299742==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 25E9B6E140 for ; Tue, 5 Aug 2014 08:47:48 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0329299742== Content-Type: multipart/alternative; boundary="1407253668.B2b60.13552"; charset="us-ascii" --1407253668.B2b60.13552 Date: Tue, 5 Aug 2014 15:47:47 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D81644 --- Comment #41 from jackdachef@gmail.com --- Created attachment 104076 --> https://bugs.freedesktop.org/attachment.cgi?id=3D104076&action=3Dedit dmesg-output after 25 minute hardware-accelerated html5 video crash, no hardlock this time (Magic SYSRQ works), screen corruption (screen subdivided horizontally into ~18 parts) kernel running with drm-next-3.17-rebased-on-fixes applied on top of 3.16-r= c6 latest commit: author Christian K=C3=B6nig 2014-07-28 11:= 30:12 (GMT) committer Alex Deucher 2014-08-04 21:45:53 (GMT) commit fa783807977da98da35590fd1d5efdfd4f33fd59 (patch) tree 0f1573ae770843228930a0f278a82eb5d482a4c5 parent 5fc6854683aad9ae8b711cbe0d824c11b4aad66c (diff) drm/radeon: allow userptr write access under certain conditions several hours of pushing and trying to get X/system lockup with firefox (hardware acceleration enabled) and watching & opening up large jpg images - showed that at least that issue was resolved (Bug #81612 ) Then now proceeded to re-test HTML5 video with hardware acceleration (hardw= are acceleration disabled was seemingly stable so far) the funny thing: each of the last 3 test attempts after pretty much exactly= 25 minutes it tends to lock up X reproducer: chromium 38.0.2107.3 (previous versions should also work), but = this one has more options disabled which should rule out other crash/instability triggers, youtube.com , keywords: movie trailers 2014 watching random movie trailers with preferrably 1080p (some only available = in 720p) result: screen content locks up, mouse still movable for a short time & sou= nd continuing, the screen turning black - (box locking up/hardlock - this time *not*) - this time: (in total 2) attempts to salvage via Magic SYSRQ + k screen flickers, another Magic SYSRQ + k screen turns on again, mentioned screen corruption (screen subdivided horizontally into ~18 parts) with mostly white and green color in the shape= of tiles took a photo, if needed so we got a *clear* improvement: the box does *not* hardlock anymore, Magic SYSRQ key works again and screen attempts to recover with Magic SYSRQ + k, but it's not successful yet hope the information of dmesg helps with further adding some ideas on how to solve this added the following patchset (patches 2-7) on top of that kernel https://lkml.org/lkml/2014/8/3/120 ([PATCH 0/7] locking/rwsem: enable reader opt-spinning & writer respin ), not sure if that might increase stability Cheers --=20 You are receiving this mail because: You are the assignee for the bug. --1407253668.B2b60.13552 Date: Tue, 5 Aug 2014 15:47:48 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 41 on bug 81644<= /a> from jackdachef@= ;gmail.com 
Created attachment 1=
04076 [details]
dmesg-output after 25 minute hardware-accelerated html5 video crash, no
hardlock this time (Magic SYSRQ works), screen corruption (screen subdivided
horizontally into ~18 parts)

kernel running with drm-next-3.17-rebased-on-fixes applied on top of 3.16-r=
c6

latest commit:
author    Christian K=C3=B6nig <christian.koenig@amd.com>    2014-07-28 11:30:12
(GMT)
committer    Alex Deucher <alexander.deucher@amd.com>    2014-08-04 21:45:53
(GMT)
commit    fa783807977da98da35590fd1d5efdfd4f33fd59 (patch)
tree    0f1573ae770843228930a0f278a82eb5d482a4c5
parent    5fc6854683aad9ae8b711cbe0d824c11b4aad66c (diff)
drm/radeon: allow userptr write access under certain conditions



several hours of pushing and trying to get X/system lockup with firefox
(hardware acceleration enabled) and watching & opening up large jpg ima=
ges -
showed that at least that issue was resolved (Bug #81612 )


Then now proceeded to re-test HTML5 video with hardware acceleration (hardw=
are
acceleration disabled was seemingly stable so far)

the funny thing: each of the last 3 test attempts after pretty much exactly=
 25
minutes it tends to lock up X


reproducer: chromium 38.0.2107.3 (previous versions should also work), but =
this
one has more options disabled which should rule out other crash/instability
triggers,

youtube.com ,
keywords: movie trailers 2014

watching random movie trailers with preferrably 1080p (some only available =
in
720p)


result: screen content locks up, mouse still movable for a short time &=
 sound
continuing, the screen turning black - (box locking up/hardlock - this time
*not*) - this time: (in total 2) attempts to salvage via Magic SYSRQ + k

screen flickers, another Magic SYSRQ + k

screen turns on again, mentioned screen corruption (screen subdivided
horizontally into ~18 parts) with mostly white and green color in the shape=
 of
tiles

took a photo, if needed


so we got a *clear* improvement: the box does *not* hardlock anymore, Magic
SYSRQ key works again and screen attempts to recover with Magic SYSRQ + k,

but it's not successful yet


hope the information of dmesg helps with further adding some ideas on how to
solve this


added the following patchset (patches 2-7) on top of that kernel
https://lkml.org/lkml/2014/8=
/3/120 ([PATCH 0/7] locking/rwsem: enable reader
opt-spinning & writer respin ), not sure if that might increase stabili=
ty


Cheers

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1407253668.B2b60.13552-- --===============0329299742== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0329299742==--