Date: Tue, 13 Oct 2015 15:45:00 -0400 From: Ed Maste <emaste@freebsd.org> To: Arto Pekkanen <isoa@kapsi.fi> Cc: "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: Testing the new i915 driver Message-ID: <CAPyFy2CBugHY=-4TCpwA7tzCEYRovOe0G-7Er1BHLqEUXk2ZGw@mail.gmail.com> In-Reply-To: <24fa3cba31bb8ef5594bde422bce5d09@kapsi.fi> References: <5615A42C.3080908@FreeBSD.org> <CAPyFy2D=N=TdoQHn=rTd9ThXdxvLCWS2BcN-HTfw9vb4y9SDag@mail.gmail.com> <24fa3cba31bb8ef5594bde422bce5d09@kapsi.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 October 2015 at 15:27, Arto Pekkanen <isoa@kapsi.fi> wrote: > I get the same error as you, and have reported this earlier. I also included > text core dump as attachment in the message. Ah, I haven't seen your message -- where was it posted? > How did you manage to paste the dmesg text here? Is there are way to attach > dmesg on the generated core dump? After my laptop panicked, the only thing I > could do was take a shot of the dmesg with a camera. This is on my laptop, and I don't see any output on the screen -- the crash happens before anything is output on the display. I'm using the Intel AMT Serial over LAN to access the console and debugger. My build host has comms/amtterm installed, and the target has AMT configured with a static IP address, mostly as described on http://www.thinkwiki.org/wiki/Intel_Active_Management_Technology_%28AMT%29
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2CBugHY=-4TCpwA7tzCEYRovOe0G-7Er1BHLqEUXk2ZGw>