But, in this time, I can't reproduce this failure with your attached
configuration. Instead of this failure, sometimes, OOM happens in my
testing with your configuration. I don't know why it happens. :)

Could you have another configuration to trigger this bug?

Anyway, this calltrace is really suspicious, because it looks like
failure of tty driver initialization. Why it is failed in this early
phase? Maybe, it is also related to OOM mentioned above.