From owner-freebsd-x11@freebsd.org Fri Jul 1 17:49:39 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 90902B8EBAC for ; Fri, 1 Jul 2016 17:49:39 +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 7F68126FD for ; Fri, 1 Jul 2016 17:49:39 +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 D7B2C125EE2; Fri, 1 Jul 2016 10:49:38 -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 CB105125EBA; Fri, 1 Jul 2016 10:49:38 -0700 (PDT) Subject: Re: Debugging System Lockup To: gljennjohn@gmail.com References: <2893a3f4-7c49-85a0-1dd1-6c61e337c0db@nomadlogic.org> <20160701125303.35f2c59a@ernst.home> Cc: freebsd-x11@freebsd.org From: Pete Wright Message-ID: <2bcdad95-e9f6-35bc-7af1-ecab3c3c335f@nomadlogic.org> Date: Fri, 1 Jul 2016 10:49:37 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20160701125303.35f2c59a@ernst.home> Content-Type: text/plain; charset=windows-1252 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: Fri, 01 Jul 2016 17:49:39 -0000 On 07/01/2016 03:53, Gary Jennejohn wrote: > On Thu, 30 Jun 2016 16:02:30 -0700 > Pete Wright wrote: > >> 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! >> > > Serial console? Should even work well enough using a FTDI adapter. Unfortunately the system I am debugging only has USB - I investigated using some of the advanced Intel SOL functionality on the system (it's a Lenovo M900 Tiny micro-computer) but it requires windows to work. I did test using a usb->db9 serial adapter which was then connected to may laptop (which also had a usb->db9 serial adapter) but that was unsuccessful. cheers, -pete -- Pete Wright pete@nomadlogic.org