Date: Wed, 14 Sep 2016 23:23:20 +0100 From: Gary Palmer <gpalmer@freebsd.org> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: hiren panchasara <hiren@strugglingcoder.info>, freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914222319.GD42278@in-addr.com> In-Reply-To: <20160914221335.GM2840@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Regards, Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160914222319.GD42278>