| To: | Kaz Kylheku <kaz@zeugmasystems.com> |
|---|---|
| Subject: | Re: futex_wake_op deadlock? |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Mon, 19 Nov 2007 18:48:37 +0000 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <DDFD17CC94A9BD49A82147DDF7D545C54DCBD2@exchange.ZeugmaSystems.local> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <DDFD17CC94A9BD49A82147DDF7D545C54DCBD2@exchange.ZeugmaSystems.local> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Fri, Nov 16, 2007 at 03:52:47PM -0800, Kaz Kylheku wrote: > From time to time, on 2.6.17.7, I see a deadlock situation go off. The > soft lockup tick occurs in the middle of do_futex, which is heavily > inlined. The system is actually hosed; it's not one of those > recoverable CPU busy situations that can sometimes trigger the lockup > detector. Can you reproduce thing hang also if you're not running in a binary compat mode, that is either running o32 binaries on a 32-bit kernel or 64-bit binaries on a 64-bit kernel? Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ohci-ssb driver on a Broadcom BCM5354, Michael Buesch |
|---|---|
| Next by Date: | Confirmation Request (1498870506), linux administration |
| Previous by Thread: | futex_wake_op deadlock?, Kaz Kylheku |
| Next by Thread: | RE: futex_wake_op deadlock?, Kaz Kylheku |
| Indexes: | [Date] [Thread] [Top] [All Lists] |