Messages in this thread | | | Date | Sun, 26 Mar 2006 23:04:59 +0100 (MET) | From | Esben Nielsen <> | Subject | Re: 2.6.16-rt7 and deadlock detection. |
| |
On Sun, 26 Mar 2006, Esben Nielsen wrote:
> I don't get any print outs of any deadlock detection with many of my > tests. > When there is a deadlock down() simply returns instead of blocking > forever.
rt_mutex_slowlock seems to return -EDEADLK even though caller didn't ask for deadlock detection (detect_deadlock=0). That is bad because then the caller will not check for it. It ought to simply leave the task blocked.
It only happens with CONFIG_DEBUG_RT_MUTEXES. That one also messes up the task->pi_waiters as earlier reported.
Esben
> > Esben > > > > On Sun, 26 Mar 2006, Esben Nielsen wrote: > > > It just looks like also normal, non-rt tasks are boosting. > > > > Esben > > > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Please read the FAQ at http://www.tux.org/lkml/ > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |