From: John David Anglin <dave.anglin@bell.net>
To: matoro <matoro_mailinglist_kernel@matoro.tk>
Cc: Vidra.Jonas@seznam.cz, linux-parisc@vger.kernel.org,
John David Anglin <dave@parisc-linux.org>,
Helge Deller <deller@gmx.de>
Subject: Re: [PATCH] parisc: Try to fix random segmentation faults in package builds
Date: Mon, 10 Jun 2024 16:17:31 -0400 [thread overview]
Message-ID: <37cf9a08-decf-4ba9-802d-7e19dee2f6a5@bell.net> (raw)
In-Reply-To: <13894865a496a7f2a6ed607e2ef708c4@matoro.tk>
Hi Matoro,
On 2024-06-10 3:52 p.m., matoro wrote:
> Unfortunately I had a few of these faults trip today after ~4 days of uptime with corresponding random segfaults. One of the WARNs was
> emitted shortly before, though not for the same PID. Reattempted the build twice and randomly segfaulted all 3 times. Had to reboot as usual
> to get it out of the bad state.
Please try v3 patch sent today.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2024-06-10 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 16:58 [PATCH] parisc: Try to fix random segmentation faults in package builds John David Anglin
2024-05-08 8:54 ` Vidra.Jonas
2024-05-08 15:23 ` John David Anglin
2024-05-08 19:18 ` matoro
2024-05-08 20:52 ` John David Anglin
2024-05-08 23:51 ` matoro
2024-05-09 1:21 ` John David Anglin
2024-05-09 17:10 ` John David Anglin
2024-05-29 15:54 ` matoro
2024-05-29 16:33 ` John David Anglin
2024-05-30 5:00 ` matoro
2024-06-04 15:07 ` matoro
2024-06-04 17:08 ` John David Anglin
2024-06-10 19:52 ` matoro
2024-06-10 20:17 ` John David Anglin [this message]
2024-06-26 6:12 ` matoro
2024-06-26 15:44 ` John David Anglin
2024-05-12 6:57 ` Vidra.Jonas
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=37cf9a08-decf-4ba9-802d-7e19dee2f6a5@bell.net \
--to=dave.anglin@bell.net \
--cc=Vidra.Jonas@seznam.cz \
--cc=dave@parisc-linux.org \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
/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