Date: Fri, 8 Nov 2019 22:28:47 -0600 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Niclas Zeising <zeising@freebsd.org> Cc: freebsd-x11@freebsd.org Subject: Re: drm-fbsd11.2-kmod on 12 Message-ID: <20191109042847.GB3169@over-yonder.net> In-Reply-To: <87da494d-207e-269c-f608-c6266c274384@freebsd.org> References: <20191103231435.GH86455@over-yonder.net> <3231b40d-1041-10d2-f062-eda237e07a02@freebsd.org> <20191106230916.GI86455@over-yonder.net> <77bac16b-0438-b7ed-0c44-fadc230e55f8@freebsd.org> <20191107220050.GA3169@over-yonder.net> <87da494d-207e-269c-f608-c6266c274384@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 08, 2019 at 09:46:43AM +0100 I heard the voice of Niclas Zeising, and lo! it spake thus: > > Can you please report this on the FreeBSDDesktop github. I mean, I _can_, if you think it'll be useful. It just doesn't seem like a particularly actionable bug report to me. "This crashes after a couple days with no obvious trigger and a generic looking backtrace I deleted 11 months ago" doesn't seem like something that helps anyone. I was hoping to be able to at least be able supplement it with "and it still hapens on drm-bsd12.0-kmod-5.something", before I figured it worth making noise. I figured I could keep living on 4.11 that long. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191109042847.GB3169>