After dump transaction frees sufficient log space, suspended processes automatically awaken and complete. If writetext or select into has resulted in unlogged changes to the database since the last backup, the last-chance threshold procedure cannot execute dump transaction. When this occurs, make a copy of the database with dump database, then truncate the log with dump transaction.
If this does not free enough space to awaken the suspended processes, you may need to increase the size of the transaction log. Use the log on option of alter database to allocate additional log space.
As a last resort, System Administrators can use the sp_who command to determine which processes are in a log suspend status and then use the kill command to kill the sleeping process.
