Messages in this thread | | | Subject | Re: 2.6.17 x86_64 regression - reboot fails due to deadlock | From | Arjan van de Ven <> | Date | Thu, 06 Jul 2006 18:23:16 +0200 |
| |
> In kdb, the system sits idle awaiting something to schedule, but nothing > will schedule since there is > a deadlock on the supermicro. Any clues as to how to find which notifier > is deadlocked?
Hi,
if it's really a deadlock, then lockdep (new in 2.6.18-rc1) ought to find it... just enable the various locking debug options in the -rc1 kernel and... it's active.
Greetings, Arjan van de Ven
- 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/
| |