Date: Wed, 04 Mar 2015 21:31:04 +0100 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= <jean-sebastien.pedron@dumbbell.fr> To: freebsd-x11@freebsd.org Subject: Re: [Call for testers] DRM device-independent code update to Linux 3.8 (take #2) Message-ID: <54F76B88.9090902@dumbbell.fr> In-Reply-To: <20150304172802.0b285585@shibato> References: <54F636B3.90701@FreeBSD.org> <20150304172802.0b285585@shibato>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6fp2a2uVtCaw1QbjFI4fcgnRi9CmHFDN0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04.03.2015 17:28, J.R. Oldroyd wrote: > On Tue, 03 Mar 2015 23:33:23 +0100 Jean-S=C3=A9bastien P=C3=A9dron <dum= bbell@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= =2E 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? --=20 Jean-S=C3=A9bastien P=C3=A9dron --6fp2a2uVtCaw1QbjFI4fcgnRi9CmHFDN0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJU92uJXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMutcQAJsemS9IYfdowcxcUlZGLVpA pxCJlg3BiWTCXr3Mn+llpqK8UFfx/JqAmPTJd8q8lPnonB+Ywg+glSFC70Jz1ydE rEokyuuN10jXSAhN0qZEahoR38rB10XycK+5m8nTOQ+21fmKXVzRlbdvO+Qbmpao YFGVUbcGcpJRavMcXxwMHL3bhwjzNvOpPjejYEe3t/kqOy5LY/M1+T5on6BRt50c P5qZpOP0/yzbczHm/ABV1WliB7VQuFRni8MOeLlVpIzj5bJXaoBsZixXOSrYtff0 MfODopMmprMZ8lg9QXz1PUjdNXteICYZO4X9FrGEle4Va1lm/ynORiroiw7TtZem IafprN8PrdMHuL+FECn//UtgIZrd0Gy+/EgAyL2+Gr6sOngtgt89WeVX4n9ruJ5Z LWCxqP0B63LvPibBICc1XmTuAbpqjMiwpjkq+MGBYoxJmDOhinwfFNNuc1Kp15Sr jXDlnJSW8yvkqFvnanvZX+oCo+xx3CrQP7ptl/aZlojg0YFkl1OyjIJaeE3gtPQ/ 2iUBazQhGD9AKLKkgNo698cRhkUFhf0fyjMIz+4FjqQbwuuDInFricKiBNuDrqRA 0kbDku9o+yEXvEtWabwHX6OQAcV4yC6dIHyWYBBM7Xc7XNwJ+61tb88uLPo9ZhXz Qs/9xocHnqaLKVeqFGmg =Vef5 -----END PGP SIGNATURE----- --6fp2a2uVtCaw1QbjFI4fcgnRi9CmHFDN0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54F76B88.9090902>