[Call for testers] DRM device-independent code update to Linux 3.8 (take #2)

[Jean-Sébastien Pédron]

On 04.03.2015 17:28, J.R. Oldroyd wrote:
> On Tue, 03 Mar 2015 23:33:23 +0100 Jean-Sébastien Pédron <dumbbell at FreeBSD.org> wrote:
> The first boot, done as a warm "reboot" command while running 10-stable
> shows that the CP init failed again and I am back to the mtx_lock panic.

The panic you have can only happen when the CP initialization failed. In
this case, the driver does some cleanup, including an mtx_destroy(9).

The panic happens because the code tries to use the destroyed mutex. The
previous core.txt.6 made me think the code we added for vt(4) didn't
check the state correctly. But core.txt.7 shows this happens with a
regular ioctl as well.

The crash was fixed in Linux 3.10. I will import the patch.

> The pattern that's emerging here is that older (mid-2014) kernels
> boot and init fine, warm or cold.  The CP init problem started
> somewhere mid-2014.

I can't reproduce it here. I still need to work with the informations
you emailed me already a month ago.

> BTW, I now also have the ring CP init failure on a second system
> that was just updated to 10.1-RELEASE-p6.  It has ATI Radeon HD 4200
> which is RS780 and it also shows the ring init failure at CAFEDEAD
> but in r600_ting_test().  Unfortunately, this system is a production
> one so I can't easily play with it.  Note, no mtx_lock panic here.
> Fortunately, the graphics not working isn't a problem on this system.

What version of FreeBSD were you running before the update?

-- 
Jean-Sébastien Pédron

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20150304/eb09c224/attachment.sig>