From owner-freebsd-x11@freebsd.org Thu Jun 30 23:02:37 2016 Return-Path: Delivered-To: freebsd-x11@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 3AED0B8671C for ; Thu, 30 Jun 2016 23:02:37 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2B2A72CA6 for ; Thu, 30 Jun 2016 23:02:37 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (localhost [127.0.0.1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.nomadlogic.org (Postfix) with ESMTPS id 84861125EE2 for ; Thu, 30 Jun 2016 16:02:30 -0700 (PDT) Received: from pop.rubicorp.com (unknown [72.34.113.100]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.nomadlogic.org (Postfix) with ESMTPSA id 7CB07125EBA for ; Thu, 30 Jun 2016 16:02:30 -0700 (PDT) To: freebsd-x11@freebsd.org From: Pete Wright Subject: Debugging System Lockup Message-ID: <2893a3f4-7c49-85a0-1dd1-6c61e337c0db@nomadlogic.org> Date: Thu, 30 Jun 2016 16:02:30 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 23:02:37 -0000 Hi All, I've been working with mmacy on testing the new i915kms support on skylake. I've got a stubborn bug where I am able to trigger a hard-lock of my system requiring a manual power-off/power-on to get it back in working order. Unfortunately, I have not been able to get any debugging information out of this system when this happens - no core, backtrace in dmesg buffer, etc. I was hoping someone on this list has had experience in debugging situations like this and could offer some tips for trying to get useful info out of this crash. I was going to configure my system to use dcons(4) - but this system does not have a fireware device, so that seems to rule out that avenue. So any input would be really appreciated! Thanks in advance! -pete -- Pete Wright pete@nomadlogic.org