From owner-freebsd-stable@freebsd.org  Thu Sep 15 09:06:35 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
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 A32F8BDCEF8
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Thu, 15 Sep 2016 09:06: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 67C4010BB
 for <freebsd-stable@FreeBSD.org>; Thu, 15 Sep 2016 09:06:35 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1bkScr-0004Qj-Em; Thu, 15 Sep 2016 12:06:33 +0300
Date: Thu, 15 Sep 2016 12:06:33 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Konstantin Belousov <kostikbel@gmail.com>
Cc: freebsd-stable@FreeBSD.org
Subject: Re: 11.0 stuck on high network load
Message-ID: <20160915090633.GS2840@zxy.spb.ru>
References: <20160904215739.GC22212@zxy.spb.ru>
 <20160905014612.GA42393@strugglingcoder.info>
 <20160914213503.GJ2840@zxy.spb.ru>
 <20160915085938.GN38409@kib.kiev.ua>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160915085938.GN38409@kib.kiev.ua>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Sep 2016 09:06:35 -0000

On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote:

> On Thu, Sep 15, 2016 at 12:35:04AM +0300, 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.
> 
> Is 'login' you reference is the ipmi client state, or you mean login(1)
> on the wedged host ?

on the wedged host

> If BMC stops responding simultaneously with the host, I would suspect
> the hardware platform issues instead of a software problem.  Do you have
> dedicated LAN port for BMC ?

Yes.
But BMC emulate USB keyboard and this is may be lock inside USB
system.
"ipmi console don't respond" must be read as "ipmi console runnnig and
attached but system don't react to keypress on this console".
at the sime moment system respon to `enter` on ipmi sol console, but
after enter `root` stuck in login in the '*tcp' state (I think this is
NIS related).