From owner-freebsd-x11@freebsd.org Wed Jul 6 11:31:43 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 E234DB744E3 for ; Wed, 6 Jul 2016 11:31:43 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A114B1172 for ; Wed, 6 Jul 2016 11:31:43 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from kirsikka.kapsi.fi ([217.30.184.185] helo=roundcube.kapsi.fi) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1bKl3L-0005wM-NC; Wed, 06 Jul 2016 14:31:39 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 06 Jul 2016 14:31:39 +0300 From: Arto Pekkanen To: Pete Wright Cc: freebsd-x11@freebsd.org Subject: Re: Debugging System Lockup In-Reply-To: <2bcdad95-e9f6-35bc-7af1-ecab3c3c335f@nomadlogic.org> References: <2893a3f4-7c49-85a0-1dd1-6c61e337c0db@nomadlogic.org> <20160701125303.35f2c59a@ernst.home> <2bcdad95-e9f6-35bc-7af1-ecab3c3c335f@nomadlogic.org> Message-ID: <1a03f3e2dc1bb12bcd33938901d7d3cf@kapsi.fi> X-Sender: isoa@kapsi.fi User-Agent: RoundCube Webmail/0.9.4 X-SA-Exim-Connect-IP: 217.30.184.185 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false 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: Wed, 06 Jul 2016 11:31:44 -0000 Pete Wright kirjoitti 01.07.2016 20:49: > 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 Here is an example on how to setup a SoL system console: https://gist.github.com/pvalkone/9292589 In order to configure SoL on your device, you will need to enable SoL in the firmware settings first. THEN you must take note of the i/o port that the SoL port uses, because without that information you cannot configure kernel console to use the specific port. When you configure a SoL port, you must also set a username and password. They are used to authenticate the IPMI terminal session from a remote computer. If you have SoL configured, you can figure out the i/o port address: dmesg | grep uart You might get multiple uarts with different ports, but one of them is the true SoL serial port. You have to try which one is it, unless you know exactly what settings you enabled in firmware. The most important lines go to /boot/loader.conf: boot_multicons="YES" boot_serial="YES" console="comconsole,vidconsole" comconsole_port="0x248" In your case, you do NOT need to make changes to /etc/ttys, because you do not need to login via SoL! The "comconsole_port" variable must be set to the i/o port value your SoL is configured with. Not sure if the other settings apply in your case. After you've modified loader.conf, start IPMI terminal program on some other computer and connect to the SoL, reboot your computer and you should get all boot messages etc on the IPMI terminal. I got SoL working without problems on my Thinkpad T430. I might post my laptop config files later, if I feel like it. -- Arto Pekkanen