Date: Fri, 06 Jan 2017 11:06:26 -0800 From: Matthew Macy <mmacy@nextbsd.org> To: "Pete Wright" <pete@nomadlogic.org> Cc: "Jonathan Anderson" <jonathan.robert.anderson@gmail.com>, "" <freebsd-current@freebsd.org> Subject: Re: PQ_LAUNDRY: unexpected behaviour Message-ID: <159752cc975.ae39473f72793.2628711433769346229@nextbsd.org> In-Reply-To: <a3063792-f155-0fce-4deb-c1625e283a55@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> <4778A6AC-97CF-4AE0-957A-7768964867D9@gmail.com> <a3063792-f155-0fce-4deb-c1625e283a55@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
kernel cores tend to be large (all of wired memory after all) and unless I have exactly the same kernel as you with the same sources at the same changeset, not useful. A backtrace is a good place to start. > kgdb /boot/kernel/kernel /var/crash/vmcore.last % bt -M ---- On Fri, 06 Jan 2017 10:53:03 -0800 Pete Wright <pete@nomadlogic.org> wrote ---- > > > On 1/6/17 10:44 AM, Jonathan Anderson wrote: > > 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? > > > > > oh great! > > i've been having the same problems with iwm too (failing to load > firmware on boot). my trick has been to either boot into an old kernel > where iwm was mostly usable. also i've commented out the line enabling > wlan0 in my rc.conf then uncommented it after boot and manually running > "service netif start" to bring up iwm. that method works most of the > time... > -pete > > -- > Pete Wright > pete@nomadlogic.org > nomadlogicLA > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?159752cc975.ae39473f72793.2628711433769346229>