Could SQL Server lock partitioning cause deadlock?

I am facing exactly the same problem, in a server with 24 CPUs.

The deadlock always happens with two inserts in the same table, with one process owning partition ID = 0 with X lock and the other with a IX lock on a partition ID > 7 (number changes and has no index corresponding in sysindexes indid, so I guess it has to do with http://msdn.microsoft.com/en-us/library/ms187504.aspx). The deadlock occurs because the first process tries to obtain a X lock on that partition ID while the second process tries to obtain an X lock on the partition ID = 0.

Is there any news about this problem?