From: Carlos O'Donell <carlos@systemhalted.org>
To: John David Anglin <dave.anglin@bell.net>
Cc: debian-hppa@lists.debian.org,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: futex: Use same lock set as lws calls
Date: Mon, 17 Oct 2011 16:55:31 -0400 [thread overview]
Message-ID: <4E9C9643.6030309@systemhalted.org> (raw)
In-Reply-To: <4E9C6F9E.5000605@bell.net>
On 10/17/2011 2:10 PM, John David Anglin wrote:
> On 10/17/2011 11:47 AM, Carlos O'Donell wrote:
>> The test-fork1 failure is still unexplained and happens intermittently.
>
> I have built a lot of unstable on my rp3440. I think this one causes failures in the thread
> testsuites of perl, python2.7 and glib2.0. These are characterized by tests hanging.
>
> There is another class of failures. They typically cause my rp3440 to crash due
> to cache corruption. The GCC libgomp and libatomic-ops testsuite seem to trigger
> this one. As I have mentioned, it's the libgomp "for" tests that
>>
>> The cancellation issues happen in tst-cancel*.
>>
>> I believe the cancellation issues are toolchain issues and I need to
>> look into them.
> Possibly, this is related to the following bug that I found last week building mpfr-3.1.0:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50691
> A call to __tls_get_addr clobbers first argument of call to mpfr_cache. Don't have a
> fix at the moment, but there is a simple testcase.
>
> On a different subject, I tried to get udev-172-1 working. However, this breaks bootstrap
> due to an invalid argument in a call to inotify_init. It's somewhat timing dependent since
> some kernels will boot if they build enough of /dev before udev messes up. In any case,
> I believe that Guy Martin posted a patch a year or so ago to correct an inconsistency
> between the glibc and the kernel for some bit definitions. I'm thinking this may fix the
> udev problem.
What patch is this? I don't remember it. URL?
> It appears that this change got lost and didn't make it into the debian glibc patch set.
> Was a consensus reached on how to fix this inconsistency?
>
> I plan on seeing if I can resolve the GCC mpfr bug, then I want to rebuild glibc with
> the flag bits fixed.
>
> I also found a GCC ICE compiling udev-172-1 with gcc-4.4. Gcc-4.5 and gcc-4.6 seem
> ok.
Cheers,
Carlos.
next prev parent reply other threads:[~2011-10-17 20:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 20:40 [PATCH] parisc: futex: Use same lock set as lws calls John David Anglin
2011-10-10 14:30 ` Rolf Eike Beer
2011-10-10 20:27 ` John David Anglin
2011-10-10 20:30 ` James Bottomley
2011-10-17 15:23 ` Domenico Andreoli
2011-10-17 15:47 ` Carlos O'Donell
2011-10-17 18:10 ` John David Anglin
2011-10-17 20:55 ` Carlos O'Donell [this message]
2011-10-17 21:09 ` John David Anglin
2011-10-17 21:57 ` Domenico Andreoli
2011-10-17 22:28 ` John David Anglin
2011-10-18 9:31 ` Domenico Andreoli
2011-10-18 9:33 ` Domenico Andreoli
2011-10-18 14:20 ` John David Anglin
2011-10-18 3:01 ` Carlos O'Donell
2011-10-18 3:21 ` Carlos O'Donell
2011-10-18 21:22 ` Carlos O'Donell
2011-10-20 15:35 ` Carlos O'Donell
2011-10-20 17:57 ` Matt Turner
2011-10-20 18:11 ` Carlos O'Donell
2011-10-20 18:16 ` Matt Turner
2011-10-20 1:47 ` John David Anglin
2011-10-21 14:49 ` Carlos O'Donell
2011-10-21 17:42 ` John David Anglin
2011-10-21 18:11 ` John David Anglin
2011-10-21 18:15 ` Carlos O'Donell
2011-10-30 15:04 ` John David Anglin
2011-10-30 15:31 ` Rolf Eike Beer
2011-10-30 16:13 ` John David Anglin
2011-10-31 0:21 ` Carlos O'Donell
2011-10-31 1:36 ` John David Anglin
2011-10-31 9:41 ` Domenico Andreoli
2011-10-31 12:28 ` John David Anglin
2011-10-31 23:26 ` John David Anglin
2011-11-01 9:15 ` Domenico Andreoli
2011-11-01 2:15 ` Carlos O'Donell
2011-11-01 9:19 ` Domenico Andreoli
2011-11-01 19:56 ` John David Anglin
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=4E9C9643.6030309@systemhalted.org \
--to=carlos@systemhalted.org \
--cc=dave.anglin@bell.net \
--cc=debian-hppa@lists.debian.org \
--cc=linux-parisc@vger.kernel.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).