On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > 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). > > ~^B don't break to debuger. > But I can login to sol console.
You can probably: debug.kdb.enter: set to enter the debugger or force a panic and get vmcore: debug.kdb.panic: set to panic the kernel Cheers, Hiren
pgpgq86WSIRNf.pgp
Description: PGP signature
