From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Re: Suspected bug in wait syscall or similar
Date: Thu, 09 Apr 2020 08:47:48 +0000 [thread overview]
Message-ID: <e2d9baa6-6fcb-53c8-b5e4-c624d1046f47@physik.fu-berlin.de> (raw)
In-Reply-To: <1848982.8N1hjUtedq@eto.sf-tec.de>
On 4/9/20 10:11 AM, Rolf Eike Beer wrote:
> Am Montag, 30. März 2020, 10:41:09 CEST schrieb Rolf Eike Beer:
>> I run a 32 bit Gentoo userspace on my T5120 with a 64 bit kernel (5.5.7 at
>> the moment). This is nothing really new, I see this for a while, but it
>> seems to got a bit worse lately.
>>
>> My observations are:
>> -the testsuite of the fish shell often hangs. A subprocess goes zombie, but
>> the parent never cleans this up
>
> This also happens on sparc64.
Indeed. The testsuite times out for us as well with kernel 5.4.19 and 2.29:
> https://buildd.debian.org/status/fetch.php?pkg=fish&arch=sparc64&ver=3.1.0-1.1&stamp\x1583586710&raw=0
Last successful build was 2019-03-26 with kernel 4.19.28 and glibc 2.28:
> https://buildd.debian.org/status/fetch.php?pkg=fish&arch=sparc64&ver=3.0.2-2&stamp\x1553615326&raw=0
Will retry with glibc 2.31 and kernel 5.5.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2020-04-09 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 8:41 Suspected bug in wait syscall or similar Rolf Eike Beer
2020-03-30 10:18 ` John Paul Adrian Glaubitz
2020-03-30 19:26 ` Adhemerval Zanella
2020-04-02 14:57 ` Rolf Eike Beer
2020-04-02 15:04 ` John Paul Adrian Glaubitz
2020-04-02 18:53 ` Adhemerval Zanella
2020-04-09 8:11 ` Rolf Eike Beer
2020-04-09 8:47 ` John Paul Adrian Glaubitz [this message]
2020-04-09 18:50 ` Rolf Eike Beer
2020-06-07 7:34 ` Rolf Eike Beer
2020-06-07 9:11 ` John Paul Adrian Glaubitz
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=e2d9baa6-6fcb-53c8-b5e4-c624d1046f47@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=sparclinux@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 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.