Odd vPar issue regarding console

[Eric Yruegas]

We have a SuperDome with multiple nPars, and one nPar is carved up into multiple vPars. I defined a new vPar in vparmgr, but whenever that vPar is brought up, console access to that nPar locks up!

Rather, all keystrokes are queued up; if I shutdown that vPar, the console processes all the inputs from when it stopped responding.

I've reset the GSP/MP, no help. I can't figure out what might be happening. I've even redefined the vPar to entirely different hardware, but the same issue persists. I've used a different vPar name (thought perhaps the vPar database might not like it for whatever reason), same result.

I've toasted and recreated this new vPar from both the command line as well as the GUI, no change in behavior (I thought perhaps I was missing some option).

Any ideas where to go with figuring this out? We've opened a call with Support, but no luck so far. I thought perhaps the 'hive mind' here might have a pointer or two.

BTW - the vPar software is B.11.11.01.02.

Thanks gang!

[Eric Yruegas]

SHOOT - hit 'submit' too soon. We have a total of 10 vPars in this nPar. The console behaves normally when booting all other vPars until I get to this new one. Even if it's the only vPar loaded, still locks.

[Eric Yruegas]

Gaah- vPar Manager is B.11.11.01.02.

vPar software itself is A.03.02.04.

Sorry gang - didn't mean to confuse anyone.

[Torsten.]

You should be aware to never press CTRL S or Q by accident - this could cause some trouble.

And btw, the version of your vPar software is probably V.02.xx or V.03.xx - run swlist to figure out.

[Torsten.]

from the release notes:

"While a virtual partition is shutting down, panicking, or booting, typing
control-s to suspend its console output may cause the virtual partition to
stop making forward progress. The virtual partition may appear to hang."

Could this be related to your problem?

"a" is very close to "s" (at least at my keyboard).

[Eric Yruegas]

I've checked the CTRL-S and CTRL-Q issues (there's references in the rel notes as well as the KB). Not the issue here. It's specific to a given vPar being online or off.