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, 08 Nov 2015 11:55:01 +0000 [thread overview]
Message-ID: <bug-92858-502-DyMfWIdZtA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92858-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2165 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92858
Christian König <deathsimple@vodafone.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #1 from Christian König <deathsimple@vodafone.de> ---
(In reply to Darren from comment #0)
> The section pasted above of the dmesg from kernel 4.3-rc-7 indicates the
> driver is failing on the "drm:r600_ringtest"...however, this is not a r600
> card but a Southern Islands.
Yeah, indeed the very basic test if the command process is up and running
didn't worked. Because of this the driver pretty much disables itself, except
for bringing up a picture to the screen.
That r600_ringtest is used for a Verde is perfectly normal, we only got
r100_ringtest, r300_ringtest and r600_ringtest for the different hardware
generations.
> Steps taken while attempting to resolve the issue: I'd initiallly thought it
> could be a firmware issue, with the linux-firmware package in the distro
> perhaps not having been updated to support the latest kernels, but even when
> I installed linux-firmware-git from the AUR to replace the standard
> linux-firmware package and then booted linux 4.3-rc7, mesa was still using
> llvmpipe instead of radeonsi, due to no GPU accel. I've also compiled the
> 4.3.0 kernel using the tarball directly from kernel.org, and a default
> kernel configuration file from ubuntu. When I booted into the 4.3.0 upstream
> kernel, GPU acceleration was still disabled. As neither the source nor the
> kernel config were from Manjaro, doesn't this rule out a distro bug and
> indicate the issue is upstream?
Yes that sounds like somewhere between 4.1 and 4.2 a patch broke the support
for Verde.
As far as I know we didn't changed anything related to Verde between 4.1 and
4.2.
Can you get the kernel source using git and then run "git bisect start v4.2
v4.1" to figure out which patch exactly caused the regression?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3759 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-11-08 11:55 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 [this message]
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
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-DyMfWIdZtA@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