Re: [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.1

[Mark_H_Johnson]

>there was one place missing - does the patch below fix this type of
>deadlock?

A different deadlock this time, same two actors but apparently a
different pair of locks.

Will send the full console log shortly.
  --Mark


===============================================
BUG: circular semaphore deadlock detected!
-----------------------------------------------
ksoftirqd/1/6 is deadlocking current task ksoftirqd/0/3


1) ksoftirqd/0/3 is trying to acquire this lock:
 [dfb5c8a4] {r:0,a:-1,&n->lock}
.. held by:       ksoftirqd/1/    6 [dff886f0,   0]
... acquired at:  arp_solicit+0x167/0x230
... trying at:   neigh_update+0x2a/0x390

2) ksoftirqd/1/6 is blocked on this lock:
 [c03c8900] {r:1,a:-1,ptype_lock}
.. held by:       ksoftirqd/0/    3 [dffe8020,   0]
... acquired at:  net_rx_action+0x8e/0x200

------------------------------
| showing all locks held by: |  (ksoftirqd/0/3 [dffe8020,   0]):
------------------------------

#001:             [d9044c30] {r:0,a:-1,&tp->rx_lock}
... acquired at:  rtl8139_poll+0x48/0x180 [8139too]

------------------------------
| showing all locks held by: |  (ksoftirqd/1/6 [dff886f0,   0]):
------------------------------

#001:             [dfb5c8a4] {r:0,a:-1,&n->lock}
... acquired at:  arp_solicit+0x167/0x230

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/