All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198511] lags in youtube videos 1080p 60fps with radeon hd4650 and kernel 4.15rc8
Date: Sat, 20 Jan 2018 01:26:50 +0000	[thread overview]
Message-ID: <bug-198511-2300-UB5ivttZOy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198511-2300@https.bugzilla.kernel.org/>

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

--- Comment #10 from Barto (mister.freeman@laposte.net) ---
I think I found the real "first bad commit",

it's :

commit 648bc3574716400acc06f99915815f80d9563783
Author: Christian König <christian.koenig@amd.com>
Date:   Thu Jul 6 09:59:43 2017 +0200

    drm/ttm: add transparent huge page support for DMA allocations v2

    Try to allocate huge pages when it makes sense.

    v2: fix comment and use ifdef

    Signed-off-by: Christian König <christian.koenig@amd.com>
    Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

because the previous commit( d188bfa5532ce5b426681d8530ff1a9683eea0ad ) before
this bad commit doesn't have the bug, so I can conclude that the first bad
commit which introduces the bug is 648bc3574716400acc06f99915815f80d9563783,

I have made a new bisect which confirms the same thing,

so what do you think Alex ?
I tried to revert 648bc3574716400acc06f99915815f80d9563783 but git refuses to
revert this commit because of conflict file, it seems that later one developper
has edited one or several files modified previoulsy by commit
648bc3574716400acc06f99915815f80d9563783

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-01-20  1:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 19:54 [Bug 198511] New: lags in youtube videos 1080p 60fps with radeon hd4650 and kernel 4.15rc8 bugzilla-daemon
2018-01-18 19:56 ` [Bug 198511] " bugzilla-daemon
2018-01-18 19:57 ` bugzilla-daemon
2018-01-18 20:35 ` bugzilla-daemon
2018-01-18 20:58 ` bugzilla-daemon
2018-01-19 21:17 ` bugzilla-daemon
2018-01-19 21:18 ` bugzilla-daemon
2018-01-19 21:20 ` bugzilla-daemon
2018-01-19 22:09 ` bugzilla-daemon
2018-01-19 22:10 ` bugzilla-daemon
2018-01-20  1:26 ` bugzilla-daemon [this message]
2018-01-20  1:29 ` bugzilla-daemon
2018-01-20  4:11 ` bugzilla-daemon
2018-01-20 15:59 ` bugzilla-daemon
2018-01-20 17:33 ` bugzilla-daemon
2018-01-21  8:07 ` bugzilla-daemon
2018-01-21  9:50 ` bugzilla-daemon
2018-01-21 10:14 ` bugzilla-daemon
2018-01-21 15:06 ` bugzilla-daemon
2018-01-21 15:19 ` bugzilla-daemon
2018-01-21 15:50 ` bugzilla-daemon
2018-01-21 16:08 ` bugzilla-daemon
2018-01-21 16:35 ` bugzilla-daemon
2018-01-21 17:20 ` bugzilla-daemon
2018-01-21 17:48 ` bugzilla-daemon
2018-01-21 18:07 ` bugzilla-daemon
2018-01-21 19:17 ` bugzilla-daemon
2018-01-21 19:38 ` bugzilla-daemon
2018-01-22  3:01 ` bugzilla-daemon
2018-01-22  8:44 ` bugzilla-daemon
2018-02-10 23:28 ` 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-198511-2300-UB5ivttZOy@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.