From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions
Date: Thu, 17 Dec 2015 07:19:48 +0000 [thread overview]
Message-ID: <bug-92858-502-jQidr5Kosq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92858-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1450 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92858
--- Comment #14 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Darren D. from comment #13)
> Another update: I think I'm either finished or close to finished--shouldn't
> bisect say which of the revisions is bad once i get down to 0, though?
>
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [bdcddf95e82b1c4e370fc1196b1f4f50f775dab4] Backmerge v4.1-rc4 into into
> drm-next
That refers to the number of commits that need to be tested after the current
one (bdcddf95). You'd still need to mark the current commit as good or bad to
get the result. However...
> Any bisects that say bad after 81663016dbfd53e29d1b5c5ddbc9b12ae1d66474 are
> marked bad not because of lack of accel, but because they didn't boot up. I
> was able to locate, however, the next bootable kernel after the 'initial
> ramdisk" boot failures started. Commit ID
> 744b058827b3db9a4f6027522dd9c73a208c2d31, and it both booted and had
> functional accelerated OpenGL on the videocard.
... I think you'll need to restart the bisection process with
744b058827b3db9a4f6027522dd9c73a208c2d31 as the initial good commit and the
nearest bad one you've found so far. Otherwise the result will likely be
inconsistent, because you marked different commits bad according to different
criteria.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2446 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-12-17 7:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 22:57 [Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions bugzilla-daemon
2015-11-08 11:47 ` bugzilla-daemon
2015-11-08 11:55 ` bugzilla-daemon
2015-11-08 15:40 ` bugzilla-daemon
2015-11-08 15:56 ` bugzilla-daemon
2015-11-08 19:55 ` bugzilla-daemon
2015-11-12 2:40 ` bugzilla-daemon
2015-11-12 2:52 ` bugzilla-daemon
2015-11-12 4:59 ` bugzilla-daemon
2015-11-12 12:57 ` bugzilla-daemon
2015-11-15 0:58 ` bugzilla-daemon
2015-11-15 11:00 ` bugzilla-daemon
2015-12-05 17:47 ` bugzilla-daemon
2015-12-05 18:28 ` bugzilla-daemon
2015-12-12 19:57 ` bugzilla-daemon
2015-12-17 7:19 ` bugzilla-daemon [this message]
2015-12-17 7:24 ` bugzilla-daemon
2015-12-19 16:33 ` bugzilla-daemon
2015-12-19 17:58 ` bugzilla-daemon
2016-01-10 2:46 ` bugzilla-daemon
2016-01-10 2:47 ` bugzilla-daemon
2016-01-10 2:47 ` bugzilla-daemon
2016-01-13 7:14 ` bugzilla-daemon
2016-01-16 16:12 ` bugzilla-daemon
2016-01-18 6:35 ` 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-92858-502-jQidr5Kosq@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