From owner-freebsd-mobile@freebsd.org Thu Mar 31 22:29:52 2016 Return-Path: Delivered-To: freebsd-mobile@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 EC8B3AE4396 for ; Thu, 31 Mar 2016 22:29:52 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [70.91.206.90]) by mx1.freebsd.org (Postfix) with ESMTP id D518D1F35 for ; Thu, 31 Mar 2016 22:29:52 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO internal.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 31 Mar 2016 15:44:15 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by internal.ambrisko.com (8.14.9/8.14.4) with ESMTP id u2VMTpAM085567; Thu, 31 Mar 2016 15:29:51 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.9/8.14.4/Submit) id u2VMTp09085565; Thu, 31 Mar 2016 15:29:51 -0700 (PDT) (envelope-from ambrisko) Date: Thu, 31 Mar 2016 15:29:51 -0700 From: Doug Ambrisko To: Adrian Chadd Cc: Ian Smith , David Christensen , Torfinn Ingolfsen , "freebsd-mobile@freebsd.org" Subject: Re: Recommended laptop for FreeBSD 10.2 Xfce workstation? Message-ID: <20160331222951.GA81396@ambrisko.com> References: <56F6290E.10500@holgerdanske.com> <20160331142243.6e81d13b04bb549362a1fea2@getmail.no> <20160401003029.F39547@sola.nimnet.asn.au> <20160331214931.GA65904@ambrisko.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2016 22:29:53 -0000 On Thu, Mar 31, 2016 at 03:12:45PM -0700, Adrian Chadd wrote: | Ah, it's haswell. You're using vt(4), right? Yep vt(4) with Haswell Intel stuff in -current. Before I used the stuff in the git repro. Doing the bounce test works fine. I tried stripping down the kernel. I tried UEFI and legacy boot. Same thing. With AMT I can in theory reset it remotely but then it the HW errors out and won't POST when it gets into this stuck resume state. I was hoping that I could reset it remotely to see dmesg. If I do a warm remote the prior dmesg it there so I was hoping to see or be able to scrible something into dmesg to give a clue. I wish I had a parallel port so I could flip bits to light some LEDs on a debug thing I made up. Thanks, Doug A.