Comment=
# 2
on bug 92858<=
/a>
from =
Darren
(In reply to Christian K=C3=B6nig from comment #1)
> (In reply to Darren from comment #0)
> > The section pasted above of the dmesg from kernel 4.3-rc-7 indica=
tes the
> > driver is failing on the "drm:r600_ringtest"...however,=
this is not a r600
> > card but a Southern Islands.
>=20
> Yeah, indeed the very basic test if the command process is up and runn=
ing
> didn't worked. Because of this the driver pretty much disables itself,
> except for bringing up a picture to the screen.
>=20
> That r600_ringtest is used for a Verde is perfectly normal, we only got
> r100_ringtest, r300_ringtest and r600_ringtest for the different hardw=
are
> generations.
>=20
> > 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, bu=
t even when
> > I installed linux-firmware-git from the AUR to replace the standa=
rd
> > linux-firmware package and then booted linux 4.3-rc7, mesa was st=
ill using
> > llvmpipe instead of radeonsi, due to no GPU accel. I've also comp=
iled the
> > 4.3.0 kernel using the tarball directly from kernel.org, and a de=
fault
> > kernel configuration file from ubuntu. When I booted into the 4.3=
.0 upstream
> > kernel, GPU acceleration was still disabled. As neither the sourc=
e nor the
> > kernel config were from Manjaro, doesn't this rule out a distro b=
ug and
> > indicate the issue is upstream?
>=20
> Yes that sounds like somewhere between 4.1 and 4.2 a patch broke the s=
upport
> for Verde.
>=20
> As far as I know we didn't changed anything related to Verde between 4=
.1 and
> 4.2.
>=20
> 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?