From: Andi Kleen <ak@suse.de>
To: Olaf Hering <olaf@aepfle.de>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Futex BUG in 2.6.18rc2-git7
Date: Fri, 4 Aug 2006 10:36:47 +0200 [thread overview]
Message-ID: <200608041036.47763.ak@suse.de> (raw)
In-Reply-To: <20060804082637.GA19493@aepfle.de>
On Friday 04 August 2006 10:26, Olaf Hering wrote:
> On Fri, Aug 04, 2006 at 09:17:00AM +0200, Andi Kleen wrote:
> >
> > One of my test machines (single socket core2 duo) running 2.6.18rc2-git7 over night
> > under moderate load threw this, followed by an endless loop of soft lockup timeouts
> > (one exemplar appended)
> >
> > I assume it is related to the new PI mutexes.
>
> Maybe triggered by this, if it was from wagner.suse.de:
Yes it was that box. So it looks like the new mutex code cannot run
the glibc test suite.
-Andi
> > /usr/src/packages/BUILD/glibc-2.4/cc-nptl/nptl/tst-robustpi8.out
> Read from remote host wagner: Connection reset by peer
>
>
next prev parent reply other threads:[~2006-08-04 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 7:17 Futex BUG in 2.6.18rc2-git7 Andi Kleen
2006-08-04 8:26 ` Olaf Hering
2006-08-04 8:36 ` Andi Kleen [this message]
2006-08-04 20:12 ` Thomas Gleixner
2006-08-04 20:26 ` Olaf Hering
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=200608041036.47763.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=olaf@aepfle.de \
/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.