From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95659] HD 7450, R9-270, GPU locked when testing glmark2
Date: Fri, 27 May 2016 01:48:08 +0000 [thread overview]
Message-ID: <bug-95659-502-R8ZgikPzBH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95659-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1055 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95659
--- Comment #5 from Tiger <tigerliu.ee@gmail.com> ---
So after two days of testing, I found this bug is still present in mesa-11.1.2.
The GPU lockup does not occur after i tested several times with 11.0.2 on my R9
270/HD 5450/HD 7450, but locked up on E6760.
11.1.2 or 11.2.0 + kernel-4.4 = lockup (HD7450,5450,r9-270)
11.0.2 + kernel-4.4 = No problems!
That looks more like some patches from commit
51e0b06d9916e126060c0d218de1aaa4e5a4ce26(11.0.2) to commit
7bcd827806b0816d61122ba3d37dd40178d96d98(11.1.2) introduced this bug and
triggered by 'glmark2 -b grid'.
I want to use 'format-patch' to pick the patches from 11.0.2 to 11.1.2, can
anyone provide a classification of the patches or some critical patches to me
to locate. I don't have a in-depth understanding of the Mesa.
Furthermore, I'll try the latest Mesa for some times and report back if I
either get a gpu lockup, or don't.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1829 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-27 1:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 12:03 [Bug 95659] HD 7450, R9-270, GPU locked when testing glmark2 bugzilla-daemon
2016-05-25 1:22 ` bugzilla-daemon
2016-05-25 2:35 ` bugzilla-daemon
2016-05-25 3:05 ` bugzilla-daemon
2016-05-25 6:18 ` bugzilla-daemon
2016-05-27 1:48 ` bugzilla-daemon [this message]
2016-05-27 6:36 ` bugzilla-daemon
2016-08-04 3:38 ` bugzilla-daemon
2016-08-04 3:45 ` bugzilla-daemon
2016-08-04 6:14 ` bugzilla-daemon
2018-04-12 6:41 ` bugzilla-daemon
2019-09-25 17:54 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-95659-502-R8ZgikPzBH@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.