From owner-freebsd-stable@freebsd.org Wed Sep 14 22:25:35 2016 Return-Path: Delivered-To: freebsd-stable@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 E4EDBBDAF16 for ; Wed, 14 Sep 2016 22:25:35 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A252310CB; Wed, 14 Sep 2016 22:25:35 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkIcV-000Eoy-UR; Thu, 15 Sep 2016 01:25:31 +0300 Date: Thu, 15 Sep 2016 01:25:31 +0300 From: Slawa Olhovchenkov To: Gary Palmer Cc: hiren panchasara , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914222531.GN2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160914214306.GU9397@strugglingcoder.info> <20160914215714.GK2840@zxy.spb.ru> <20160914220420.GW9397@strugglingcoder.info> <20160914221335.GM2840@zxy.spb.ru> <20160914222319.GD42278@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914222319.GD42278@in-addr.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2016 22:25:36 -0000 On Wed, Sep 14, 2016 at 11:23:20PM +0100, Gary Palmer wrote: > On Thu, Sep 15, 2016 at 01:13:35AM +0300, Slawa Olhovchenkov wrote: > > On Wed, Sep 14, 2016 at 03:04:20PM -0700, hiren panchasara wrote: > > > > > On 09/15/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > On Wed, Sep 14, 2016 at 02:43:06PM -0700, hiren panchasara wrote: > > > > > > > > > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > > > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > > > > > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > > > > Under high network load and may be addtional conditional system go to > > > > > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > > > > > debug this? > > > > > > > > > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > > > > > info when it goes unresponsive? > > > > > > > > > > > > ipmi console don't respond (chassis power diag don't react) > > > > > > login on sol console stuck on *tcp. > > > > > > > > > > I assume you tried ~^b (tilda followed by ctrl+b) without success? > > > > > > > > ~B, as in man ipmitool > > > > > > No, not shift-b but ctrl-b. > > > > > > I am not aware of ipmitool reference. On unresponsive console, try > > > ~^b (tilda followed by ctrl+b) > > > > ipmitool ~B send break, do you talk about break or about special > > serial console keystroke to enter debuger, distinct from break? > > A lot of old console servers used to send break when they reset or > on boot, so the FreeBSD console does not break to debugger when > a break command is received. That's why the tidla CTRL-b is > required as it's sufficiently unlikely to be accidentally sent by > equipment connected to the serial console. OK, thanks to clarification, I am try ~^B on next attempt.