From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeff Bailey <jbailey@ubuntu.com>
Cc: linuxppc-dev@ozlabs.org,
Fabio Massimo Di Nitto <fabbione@ubuntu.com>,
Paul Mackerras <paulus@samba.org>,
Steve Munroe <sjmunroe@us.ibm.com>,
Ben Collins <ben.collins@ubuntu.com>
Subject: Re: glibc-2.5 test suite hangs/crashes the machine
Date: Mon, 30 Oct 2006 12:47:05 +1100 [thread overview]
Message-ID: <1162172825.25682.139.camel@localhost.localdomain> (raw)
In-Reply-To: <1161966154.18515.1.camel@localhost.localdomain>
On Fri, 2006-10-27 at 12:22 -0400, Jeff Bailey wrote:
> Le vendredi 27 octobre 2006 à 07:56 +0200, Fabio Massimo Di Nitto a
> écrit :
> > Hi everybody,
> >
> > i am in the process of bootstrapping the new toolchain for ubuntu and I am
> > hitting a problem building glibc-2.5 on ppc.
> >
> > This behaviour has been reproduced on 2.6.15/2.6.17 and 2.6.19-rc2 (where the
> > machine crashes) and with ppc32 and ppc64 kernels.
> > A hard reboot of the machine is required to get rid of the Zl processes hanging
> > around that keep spinning the CPU at 100%.
> >
> > I did place sources here: http://people.ubuntu.com/~fabbione/benh/
> >
> > but i start to believe it is a kernel bug we are exploiting only now.
> >
> > Any hint or help for what to look for would be extremely appreciated.
>
> Heya Fabio, just an update, it looks like the tests that are zombie'ing
> are the nptl tst-robust[1-8] tests. According to /proc/##/wchan, the
> tasks are cheerfully spinning in do_exit.
So I've built that glibc with debian 2.6.16 kernel headers (since Fabio
says the problem doesn't happen with glibc built with 2.6.19 headers)
and have ran that with 2.6.19-rc3-git-du-jour.
The machine didn't crash, nor did I see any zombie with those
tst-robust[1-8], however, I did get as SIGBUS with tst-robustpi1. I've
tracked it down to being an alignment exception. It looks like glibc is
doing a lwarx on a non-aligned value, though I can't say precisely
what's up here. I don't know how I can get a backtrace when running
those test-cases... the test harness seems to catch signals, I suppose
it could be modified to spit one out.
At this point, it would be useful to have somebody who knows glibc to
tell us:
- what are those tst-robust all about ? (what do they do "special" that
might trigger bad reactions with older kernels)
- how can glibc ever do atomic operations on a non-aligned value ?
Ben.
next prev parent reply other threads:[~2006-10-30 1:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 5:56 glibc-2.5 test suite hangs/crashes the machine Fabio Massimo Di Nitto
2006-10-27 16:22 ` Jeff Bailey
2006-10-30 1:47 ` Benjamin Herrenschmidt [this message]
2006-11-01 22:17 ` Steve Munroe
2006-11-01 22:35 ` Benjamin Herrenschmidt
2006-11-01 22:56 ` Steve Munroe
2006-11-01 23:22 ` Benjamin Herrenschmidt
2006-10-30 3:02 ` Benjamin Herrenschmidt
2006-10-30 11:35 ` Fabio Massimo Di Nitto
2006-10-30 20:36 ` Benjamin Herrenschmidt
2006-10-31 6:37 ` Fabio Massimo Di Nitto
2006-10-31 6:51 ` Fabio Massimo Di Nitto
2006-10-31 9:47 ` Fabio Massimo Di Nitto
2006-10-31 20:30 ` Benjamin Herrenschmidt
2006-10-31 20:44 ` Fabio Massimo Di Nitto
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=1162172825.25682.139.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ben.collins@ubuntu.com \
--cc=fabbione@ubuntu.com \
--cc=jbailey@ubuntu.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sjmunroe@us.ibm.com \
/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.