From: Olaf Hering <olaf@aepfle.de>
To: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: softlockup during glibc tst-robust in 2.6.18-rc3
Date: Thu, 3 Aug 2006 21:23:02 +0200 [thread overview]
Message-ID: <20060803192302.GA6049@aepfle.de> (raw)
In-Reply-To: <20060802053821.GA24356@aepfle.de>
On Wed, Aug 02, 2006 at 07:38:21AM +0200, Olaf Hering wrote:
>
> A 'make check' in glibc mainline triggers this lockup in current Linus tree on a
> 4cpu p630. All I can do at this point is a reboot via sysrq b.
>
> According to the glibc build log, tst-robust1 and tst-robust2 timed out, tst-robust3
> is still running.
> I'm using pseries_defconfig with HZ=100.
> BUG: soft lockup detected on CPU#1!
> Call Trace:
> [C000000087713610] [C00000000000EBDC] .show_stack+0x68/0x1b0 (unreliable)
> [C0000000877136B0] [C000000000081230] .softlockup_tick+0xf0/0x128
> [C000000087713760] [C00000000005961C] .run_local_timers+0x1c/0x30
> [C0000000877137E0] [C0000000000202BC] .timer_interrupt+0xa8/0x474
> [C0000000877138C0] [C0000000000034DC] decrementer_common+0xdc/0x100
> --- Exception: 901 at .handle_futex_death+0x28/0x98
> LR = .compat_exit_robust_list+0x108/0x1ac
> [C000000087713BB0] [C0000000FAB61810] 0xc0000000fab61810 (unreliable)
> [C000000087713C30] [C00000000006DA60] .compat_exit_robust_list+0x108/0x1ac
> [C000000087713D00] [C000000000050C6C] .do_exit+0x1f8/0x980
> [C000000087713DB0] [C0000000000514C0] .complete_and_exit+0x0/0x2c
> [C000000087713E30] [C00000000000861C] syscall_exit+0x0/0x40
0f0410823792ae0ecb45f2578598b115835ffdbb is first bad commit
diff-tree 0f0410823792ae0ecb45f2578598b115835ffdbb (from b471f55427ee94d6de2b33b88a7409f8cbc6b5dc)
Author: David Woodhouse <dwmw2@infradead.org>
Date: Tue May 23 07:46:40 2006 -0700
[PATCH] powerpc: wire up sys_[gs]et_robust_list
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: Paul Mackerras <paulus@samba.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
:040000 040000 3baf7e58d2e81265b7918fd43c2f8fe8a2a622fd 5d7ac9147e4de3de41fe8be28753024bf5be2149 M arch
:040000 040000 9c7655ffb8bd4927585604d3c9da723f56d2cbc0 2221102e21e320dfdad18fb822bf97675e9c8353 M include
However, I guess the real culprit is e9056f13bfcdd054a0c3d730e4e096748d8a363a
[PATCH] lightweight robust futexes: arch defaults
next prev parent reply other threads:[~2006-08-03 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 5:38 softlockup during glibc tst-robust in 2.6.18-rc3 Olaf Hering
2006-08-03 19:23 ` Olaf Hering [this message]
2006-08-04 19:35 ` [PATCH] futex: Apply recent futex fixes to futex_compat Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060803192302.GA6049@aepfle.de \
--to=olaf@aepfle.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.