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? > > > > > That usually drops into db> > > > > May be now need some sysctl for enable this? > > There is a sysctl for this too but on console, the keystrokes I said > should work, imo. > > Cheers, > Hiren _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
