Deadlocked on lock | communication buffer resources

Warehouse server; MAXDOPS = 12

Last command that caused/encountered problem: DBCC UPDATEUSAGE(SPIEWeb)WITHNO_INFOMSGS

SQL version:Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)   Jun 17 2011 00:54:03   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

Wait state info:

wait_type                                        wait_time_s      pct      running_pct
CXPACKET                                       55446284.88     38.51      38.51
LATCH_EX                                       44292238.47     30.77      69.28
DISPATCHER_QUEUE_SEMAPHORE      4614765.87      3.21      72.49
XE_TIMER_EVENT                              4136938.33      2.87       75.36
LOGMGR_QUEUE                               4136710.51      2.87       78.23
REQUEST_FOR_DEADLOCK_SEARCH   4135825.51      2.87       81.11
FT_IFTSHC_MUTEX                            4132677.15      2.87       83.98
XE_DISPATCHER_WAIT                      4121962.50      2.86       86.84
CHECKPOINT_QUEUE                         4115884.09      2.86       89.70
FT_IFTS_SCHEDULER_IDLE_WAIT       4086988.27      2.84       92.54

I'm surprised to find this happening with the DBCC UPDATEUSAGE.  I wouldn't be surprised if it was caused by the deliberately parallelized SSIS packages the BI guys are writing, but the DBCC command?

Any suggestions would be helpful.

TIA,

Al