Date: Tue, 05 Sep 2017 19:12:00 +0200 From: Nils Beyer <nbe@renzel.net> To: Pete Wright <pete@nomadlogic.org> Cc: freebsd-x11@freebsd.org Subject: Re: drm-next-kmod panic Message-ID: <e335a57ed408c57c3dd1e0a59d1c3c7f@renzel.net> In-Reply-To: <0d085613-cb55-c2e3-142f-93fc4fe388df@nomadlogic.org> References: <cf88383f-5f7a-9904-996e-b26d1d49bc65@alvermark.net> <69456e0e-8b97-51fd-8a65-023ecb093cfd@nomadlogic.org> <fbc06fc9-a839-96e1-69ef-1603bbdefcea@renzel.net> <0d085613-cb55-c2e3-142f-93fc4fe388df@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-09-05 18:43 CEST, Pete Wright wrote: > I've filed this ticket in the drm-next Github project (I am running into this issue as well): > https://github.com/FreeBSDDesktop/freebsd-base-graphics/issues/173 thank you - I've added my finding as well; still not completely sure if that problem more likely belongs to FreeBSD's bugtracker...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e335a57ed408c57c3dd1e0a59d1c3c7f>