Date: Fri, 06 Jan 2017 13:44:37 -0500 From: "Jonathan Anderson" <jonathan.robert.anderson@gmail.com> To: "Pete Wright" <pete@nomadlogic.org> Cc: freebsd-current@freebsd.org Subject: Re: PQ_LAUNDRY: unexpected behaviour Message-ID: <4778A6AC-97CF-4AE0-957A-7768964867D9@gmail.com> In-Reply-To: <1779f83b-687d-ac6f-587f-90bdc6d61c20@nomadlogic.org> References: <CAMGEAwBknRjecXFyyFGWFQtstX1OiOUvQoVsb9RXj7rmMQ6dDA@mail.gmail.com> <1596d0f6d6d.1266583c3319360.3590554896761456790@nextbsd.org> <74A6C6D0-90A4-4DB2-8D89-5D2B1E495F88@FreeBSD.org> <15974c6426d.12945df5e62589.5931208946643250381@nextbsd.org> <1779f83b-687d-ac6f-587f-90bdc6d61c20@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 Jan 2017, at 12:48, Pete Wright wrote: > On 1/6/17 9:14 AM, Matthew Macy wrote: >> >> I just did the merge and it's using a relatively untested new KPI so >> regressions aren't too surprising I'm afraid. #96 is more or less >> content free in terms of providing useful information. Getting a core >> + backtrace would be a lot more helpful. See the repo's wiki for >> details on improving your odds of getting a core. >> > > I have found the following has enabled me to catch kernel panic's > pretty reliably on the drm-next branch when i have the i915kms module > loaded: > > dev.drm.skip_ddb=1 Excellent: I turned that on and got a core, then got another core while tar'ing up the first core. :) The machine in question is currently not connected to any network (iwm is being a bit unhappy), but once it is, where can I put the tarball? Jon -- jonathan.anderson@ieee.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4778A6AC-97CF-4AE0-957A-7768964867D9>