From owner-freebsd-stable@freebsd.org  Wed Sep 14 21:57:16 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 EBAEDBDA019
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 14 Sep 2016 21:57:16 +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 AEDB61867
 for <freebsd-stable@FreeBSD.org>; Wed, 14 Sep 2016 21:57:16 +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 1bkIB8-000E6W-Dv; Thu, 15 Sep 2016 00:57:14 +0300
Date: Thu, 15 Sep 2016 00:57:14 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: hiren panchasara <hiren@strugglingcoder.info>
Cc: freebsd-stable@FreeBSD.org
Subject: Re: 11.0 stuck on high network load
Message-ID: <20160914215714.GK2840@zxy.spb.ru>
References: <20160904215739.GC22212@zxy.spb.ru>
 <20160905014612.GA42393@strugglingcoder.info>
 <20160914213503.GJ2840@zxy.spb.ru>
 <20160914214306.GU9397@strugglingcoder.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160914214306.GU9397@strugglingcoder.info>
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: Wed, 14 Sep 2016 21:57:17 -0000

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

> That usually drops into db>

May be now need some sysctl for enable this?

> I am also fighting an issue where upon said keystrokes, I see 
> "KDB: enter: Break to debugger" but it doesn't drop to db>
> At that point I have to 'ipmitool blah power reset' the box.
> 
> Cheers,
> Hiren