Date: Fri, 1 Jul 2016 10:49:37 -0700 From: Pete Wright <pete@nomadlogic.org> To: gljennjohn@gmail.com Cc: freebsd-x11@freebsd.org Subject: Re: Debugging System Lockup Message-ID: <2bcdad95-e9f6-35bc-7af1-ecab3c3c335f@nomadlogic.org> In-Reply-To: <20160701125303.35f2c59a@ernst.home> References: <2893a3f4-7c49-85a0-1dd1-6c61e337c0db@nomadlogic.org> <20160701125303.35f2c59a@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/01/2016 03:53, Gary Jennejohn wrote: > 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. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2bcdad95-e9f6-35bc-7af1-ecab3c3c335f>