From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88758] Low FPS in settings on Dota2
Date: Thu, 29 Jan 2015 11:24:48 +0000 [thread overview]
Message-ID: <bug-88758-502-fScQ3zMtYN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88758-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88758
--- Comment #11 from Lorenzo Bona <lorenz.bona@gmail.com> ---
(In reply to Michel Dänzer from comment #10)
> (In reply to Lorenzo Bona from comment #8)
> > git_bisect.log
>
> That looks way too short to be the final result. Keep going until git bisect
> tells you which commit is the first bad one.
Sorry for the delay. Here the git bisect result:
$git bisect bad
02376d8282b88f07d0716da6155094c8760b1a13 is the first bad commit
commit 02376d8282b88f07d0716da6155094c8760b1a13
Author: Michel Dänzer <michel.daenzer@amd.com>
Date: Thu Jul 17 19:01:08 2014 +0900
drm/radeon: Allow write-combined CPU mappings of BOs in GTT (v2)
v2: fix rebase onto drm-fixes
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
:040000 040000 369d9e0ff185b6e6c9614de87296fc60072f56b9
d9fb7256264156abdaf238cd0e6f0925d7e54ac7 M drivers
Attached the complete git bisect log.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2276 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-29 11:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 17:34 [Bug 88758] Low FPS in settings on Dota2 bugzilla-daemon
2015-01-23 17:35 ` bugzilla-daemon
2015-01-26 8:19 ` bugzilla-daemon
2015-01-26 8:28 ` bugzilla-daemon
2015-01-26 9:41 ` bugzilla-daemon
2015-01-28 7:04 ` bugzilla-daemon
2015-01-28 10:26 ` bugzilla-daemon
2015-01-28 13:41 ` bugzilla-daemon
2015-01-28 13:42 ` bugzilla-daemon
2015-01-28 14:16 ` bugzilla-daemon
2015-01-28 14:17 ` bugzilla-daemon
2015-01-29 11:24 ` bugzilla-daemon [this message]
2015-01-29 11:25 ` bugzilla-daemon
2015-01-29 13:55 ` bugzilla-daemon
2015-01-29 14:02 ` bugzilla-daemon
2015-01-29 14:38 ` bugzilla-daemon
2015-01-29 15:04 ` bugzilla-daemon
2015-01-29 15:58 ` bugzilla-daemon
2015-01-29 16:44 ` bugzilla-daemon
2015-01-29 17:14 ` bugzilla-daemon
2015-01-29 17:15 ` bugzilla-daemon
2015-01-29 18:10 ` bugzilla-daemon
2015-01-30 3:17 ` bugzilla-daemon
2015-01-30 8:41 ` bugzilla-daemon
2015-01-30 11:56 ` bugzilla-daemon
2015-01-30 11:57 ` bugzilla-daemon
2015-01-30 11:58 ` bugzilla-daemon
2015-01-30 11:59 ` bugzilla-daemon
2015-01-31 17:45 ` bugzilla-daemon
2015-01-31 17:46 ` bugzilla-daemon
2015-01-31 17:46 ` bugzilla-daemon
2015-01-31 17:50 ` bugzilla-daemon
2015-02-03 5:54 ` bugzilla-daemon
2015-02-03 6:54 ` bugzilla-daemon
2015-02-03 6:55 ` bugzilla-daemon
2015-02-03 6:55 ` bugzilla-daemon
2015-02-03 7:06 ` 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-88758-502-fScQ3zMtYN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox