Date: Fri, 1 Jul 2016 12:53:03 +0200 From: Gary Jennejohn <gljennjohn@gmail.com> To: Pete Wright <pete@nomadlogic.org> Cc: freebsd-x11@freebsd.org Subject: Re: Debugging System Lockup Message-ID: <20160701125303.35f2c59a@ernst.home> In-Reply-To: <2893a3f4-7c49-85a0-1dd1-6c61e337c0db@nomadlogic.org> References: <2893a3f4-7c49-85a0-1dd1-6c61e337c0db@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 30 Jun 2016 16:02:30 -0700 Pete Wright <pete@nomadlogic.org> 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. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160701125303.35f2c59a>