Cosmo SP console appears to have flow control problems.

I'm on the console (pilot sp console) on london sled 17, a Cosmo.
I've paniced because I ran the system out of memory and im currently sitting at the kmdb prompt.
There seems to be some sort of flow control that limits output until I press additional keys to "nudge" it along.
For example, I ran this command and I got the start of my output:

[0]> 0t2::pid2proc |::walk thread |::findstack -v
stack pointer for thread fffff40f87390c20 (pageout/1): fffff40f8738fd50
[ fffff40f8738fd50 _resume_from_idle+0x130() ]
  fffff40f8738fd80 swtch+0x139()
  fffff40f8738fdb0 cv_wait+0x70(fffffffffc179134, fffffffffc179128)
  fffff40f8738fe10 page_create_wait+0x11b(1, 43)
  fffff40f8738fef0 page_create_va+0x573(fffffffffc470638, fffffa10c1cad000, 1000, 53, fffff40f8738ff00, fffffa10c1cad000)
  fffff40f8738ff80 segkmem_page_create+0xa3(fffffa10c1cad000, 1000, 4, fffffffffc470638)
  fffff40f87390020 segkmem_xalloc+0x150(ffff

But, it stopped there, mid line.
I then hit space, and I get the rest of the output.

It does not always do this, and I've even seen it happen when I enter a single one line command and only 2/3rd of the command shows up
I don't get the rest of the output until I send more input.

Reproduce the issue at the kmdb prompt on the pilot SP console on London sled 17, using the shown stack-walk command and a one-line command. Trace where console output stops and verify that complete output arrives without pressing additional keys.