From: John David Anglin <dave.anglin@bell.net>
To: Helge Deller <deller@gmx.de>, Sam James <sam@gentoo.org>,
linux-parisc@vger.kernel.org
Cc: hppa@gentoo.org
Subject: Re: Recurring INEQUIVALENT ALIASES issues and userland corruption/crashes
Date: Tue, 22 Mar 2022 14:30:51 -0400 [thread overview]
Message-ID: <deca5592-b258-32cb-024b-4b2197efddb2@bell.net> (raw)
In-Reply-To: <23931882-c00e-79b1-09ed-91c8799d0aa7@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On 2022-03-22 2:14 p.m., Helge Deller wrote:
>> The machine is currently running 5.17.0 along with Helge's tree up to (and including) Linus's pull for 5.18.0
>> (https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=a04b1bf574e1f4875ea91f5c62ca051666443200).
> The INEQUIVALENT ALIASES messages are most likely not related to the instability
> of your machine. I see them randomly on the debian buildd servers as well.
>
> Instead of using the latest (development) kernels, I'd suggest that you
> first try with a "stable" kernel.
> On the debian buildd servers I'm currently running Kernel 5.10.106+, which is pretty stable.
> I think Dave is running 5.16.x quite ok.
I do have a few patches for 5.16. Most should be in latest pull except for VDSO support. See attached file.
Dave
--
John David Anglin dave.anglin@bell.net
[-- Attachment #2: linux-5.16.16-20220319-m.patch.gz --]
[-- Type: application/x-gzip, Size: 14586 bytes --]
next prev parent reply other threads:[~2022-03-22 18:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 17:52 Recurring INEQUIVALENT ALIASES issues and userland corruption/crashes Sam James
2022-03-22 18:14 ` Helge Deller
2022-03-22 18:30 ` John David Anglin [this message]
2022-03-22 19:47 ` Sam James
2022-03-22 18:19 ` John David Anglin
2022-03-22 19:37 ` Sam James
2022-03-22 19:52 ` Helge Deller
2022-03-22 20:42 ` Sam James
2022-03-22 21:04 ` John David Anglin
[not found] ` <73bf3336-9207-ba0e-1950-8cb1b7d6adc3@bell.net>
2022-03-22 20:29 ` John David Anglin
2022-03-22 20:43 ` Sam James
2022-03-22 23:59 ` John David Anglin
2022-04-05 21:13 ` John David Anglin
2022-04-12 5:18 ` Sam James
2022-04-12 12:27 ` John David Anglin
2022-04-12 13:20 ` John David Anglin
2022-04-12 23:45 ` Sam James
2022-04-19 19:52 ` Sam James
2022-04-19 21:29 ` John David Anglin
2022-04-19 21:52 ` James Bottomley
2022-04-20 0:11 ` John David Anglin
2022-04-23 20:33 ` 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=deca5592-b258-32cb-024b-4b2197efddb2@bell.net \
--to=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=hppa@gentoo.org \
--cc=linux-parisc@vger.kernel.org \
--cc=sam@gentoo.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