dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 15 Nov 2015 11:00:45 +0000	[thread overview]
Message-ID: <bug-92858-502-h0R8a91CK6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92858-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1343 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=92858

--- Comment #10 from Christian König <deathsimple@vodafone.de> ---
That looks promising. Here are a few hints how to proceed.

> git bisect good c11d716218910c3aa2bac1bb641e6086ad649555
First of all you don't need to always specify the commit, git knows that by
itself. E.g. "git bisect good" without the commit hash should be sufficient.

(In reply to Darren D. from comment #9)
> git bisect bad c5fd936e992dd2829167d2adc63e151675ca6898
> 
> The kernel I build after I tell git bisect the above revision is bad freezes
> on "loading initial ramdisk."

That's unfortunate but happens sometimes. Since
c5fd936e992dd2829167d2adc63e151675ca6898 is bad the problem must be somewhere
between v4.1 and c5fd936e992dd2829167d2adc63e151675ca6898.

Since it is a radeon driver problem I suggest you limit bisect to only test the
changes made to radeon.

Please try the command "git bisect start
c5fd936e992dd2829167d2adc63e151675ca6898 v4.1 drivers/gpu/drm/radeon/".

If that still doesn't work try "git bisect skip" if you have a commit that
won't work at all.

If that also doesn't work just go on with "git bisect good/bad" and try to
figure out when the issue with the ramdisk started.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2369 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

  parent reply	other threads:[~2015-11-15 11:00 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 [this message]
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
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-h0R8a91CK6@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