Date: Wed, 25 Feb 2015 13:06:32 +0100 From: "J.R. Oldroyd" <fbsd@opal.com> To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= <dumbbell@FreeBSD.org> Cc: freebsd-x11@freebsd.org Subject: Re: [Call for testers] DRM device-independent code update to Linux 3.8 Message-ID: <20150225130632.5b76d091@shibato> In-Reply-To: <54ECD4EC.80708@FreeBSD.org> References: <54E3D2A0.2090903@FreeBSD.org> <54E74988.1050301@icloud.com> <20150220221246.661f2d01@shibato> <54ECD4EC.80708@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 24 Feb 2015 20:45:48 +0100 Jean-S=C3=A9bastien P=C3=A9dron <dumbbel= l@FreeBSD.org> wrote: > > On 21.02.2015 04:12, J.R. Oldroyd wrote: > > But, booting does not go well: > >=20 > > Feb 20 21:58:22 xx kernel: panic: mtx_lock() of destroyed mutex @ /usr/= src/sys/modules/drm2/drm2/../../../dev/drm2/drm_irq.c:1036 >=20 > Could you please try the following patch? > https://people.freebsd.org/~dumbbell/graphics/drm_fb_helper-mtx-destroyed= -panic.1.patch >=20 > Apply it over your already patched source tree (not in place of > drm-update-38.*.patch). >=20 With that patch, I am now able to boot without the mtx_lock() panic. Thanks. Other observations: On a cold boot, the CP init now succeeds with no CAFEDEAD - wow! However, on a reboot (without power off) the CP init is still *mostly* failing with the CAFEDEAD - I've rebooted about 6 times and 4 times got the CAFEDEAD. This is still pointing at there being something not quite right with the initialization sequence. Chip is RS690 X1270 IGP, and the CAFEDEAD is from r100_ring_test(). There are 10 LORs being logged on booting this revision (r279092), but none related to drm code. -jr
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150225130632.5b76d091>