From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
Cc: linuxppc-dev@ozlabs.org, Jeff Bailey <jbailey@ubuntu.com>,
Paul Mackerras <paulus@samba.org>,
Ben Collins <ben.collins@ubuntu.com>
Subject: Re: glibc-2.5 test suite hangs/crashes the machine
Date: Tue, 31 Oct 2006 07:36:50 +1100 [thread overview]
Message-ID: <1162240610.25682.182.camel@localhost.localdomain> (raw)
In-Reply-To: <4545E38B.5010702@ubuntu.com>
On Mon, 2006-10-30 at 12:35 +0100, Fabio Massimo Di Nitto wrote:
> Benjamin Herrenschmidt wrote:
> > Does that patch fixes it ?
> >
>
> tested with kernel .17 and headers from .19 and the build hangs. Still tons of
> Zl processes around.
>
> On the note building with kernel .19 and .19 headers it all goes smooth.
Ok, so there's a different issue from what I've found. You haven't by
chance noted what those processes are (which test case typically) ?
Also, there's a sysrq to get a backtrace of all pending processes,
though I don't remember which one off the top of my mind, might be
useful to have a look though.
Ben.
next prev parent reply other threads:[~2006-10-30 20:36 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
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 [this message]
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=1162240610.25682.182.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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).