Date: Wed, 17 Aug 2016 09:03:38 +0700 From: Felix Hanley <felix@userspace.com.au> To: freebsd-x11@freebsd.org Subject: Re: drm-4.7-final tagged - CFT for drm-next was Re: drm-4.7-rc1 tagged Message-ID: <20160817020338.GA1121@hewie.yelnah> In-Reply-To: <1568d21aacd.f8cd4ff3172638.3926950928184142414@nextbsd.org> References: <1567da024af.bfcdfbc455906.5120985150976586422@nextbsd.org> <15686fbfed7.b47b2120143737.5219243845741262240@nextbsd.org> <20160814124342.GA1125@hewie.yelnah> <1568b4317e9.11b24266b159467.3434767500385208720@nextbsd.org> <20160814234007.GA5735@hewie.yelnah> <1568d21aacd.f8cd4ff3172638.3926950928184142414@nextbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 15, 2016 at 12:36:49AM -0700, Matthew Macy wrote: > > Please read the wiki for the project on github. > > Just because you're not getting a core doesn't mean it's not > panicking. There are a number of steps you can take to greatly > increase the likelihood of obtaining a core dump. > Thanks Matt, I have all those settings enabled and I have previously been able to capture a crash dump but on current drm-next it does not, just a blank screen and unresponsive. I will try again in a couple of days. -felix
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160817020338.GA1121>