From owner-freebsd-current@freebsd.org Fri Jan 6 18:53:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60A22CA20E1 for ; Fri, 6 Jan 2017 18:53:06 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47D561DB2 for ; Fri, 6 Jan 2017 18:53:06 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from la-dgt-31327.usa.tribune.com (nat-192-187-90-113.nat.tribpub.com [192.187.90.113]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 3085f7f8 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 6 Jan 2017 10:53:05 -0800 (PST) Subject: Re: PQ_LAUNDRY: unexpected behaviour To: Jonathan Anderson References: <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> Cc: freebsd-current@freebsd.org From: Pete Wright Message-ID: Date: Fri, 6 Jan 2017 10:53:03 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <4778A6AC-97CF-4AE0-957A-7768964867D9@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2017 18:53:06 -0000 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