> after reset, it's illegal to call qlock without a process (notably > in an interrupt function), as it previously was.
That suggests that the (hopefully) few instances of qlock() invocations that may occur in this space should be burdened with the need to check for the value of "up" and altogether skip the call if it's nil. Mind you, this is not the problem we set out to fix anymore, although no doubt there is a relationship, however tenuous. ++L
