I'm currently experiencing a spinloop wait type with command of Unknown Token. The issue occured when I copied DB filed from another server and attempted to attach it -using the SSMS wizard - to the affected DB.
The attach failed due to an OS permission error but the database engine - for no clear reason - mounted the DB in a Recovery/Read Only mode; the transaction did not rollback. This rogue DB cannot be altered, dropped, detached, etc and KILL command fails
against the culprit SPID.
In the DB log there is a stack dump at Location: "logmgr.cpp":5527, * Expression: !(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo).
And the errors: Error: 17066, Severity: 16, State: 1; Error: 3624, Severity: 20, State: 1.
The logs continue thereafter with the following: Process 29:0:0 (0xe48) Worker 0x0000000015D6E1C0 appears to be non-yielding on Scheduler 18. Thread creation time: 12927361417467. Approx Thread CPU Used: kernel 46 ms, user 4040 ms. Process Utilization 7%.
System Idle 88%. Interval: 132567 ms.
I also discovered that sql server agent will not run jobs although the serive is running. Its logs read:
2010-08-27 08:36:26 - ?  Waiting for SQL Server to recover databases...
2010-08-27 10:41:59 - ?  SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2010-08-27 10:42:00 - ?  SQLServerAgent term
View Complete Post