Comment 5 for bug 1295596

(not related to the issue, but to a hang just after this message appears, for which people may be googling the startpar-bridge message)

I found this continually as the last suspicious event before hang on an arm64 with an old 14.04 nfsroot system.
After this it would always hang at "nfs: server xx.xx.xx.xx not responding, still trying".

System used to work, but I was using this nfsroot on a new board.
It had hung partway thru apt-upgrade to modern 14.04 packages (before intended update to 16.10).
That hang was due to kernel issues on the new hardware.

Root cause of the hang was /run/shm being a directory, not a symlink.
Removing /nfsroot/run/shm fixed the hang.

Somewhere in the evolution of 14.04 the implementation of /run/shm apparently changed, and interrupting update leaves system unbootable