From: John David Anglin <dave.anglin@bell.net>
To: Sam James <sam@gentoo.org>
Cc: linux-parisc@vger.kernel.org, hppa@gentoo.org
Subject: Re: Recurring INEQUIVALENT ALIASES issues and userland corruption/crashes
Date: Tue, 22 Mar 2022 16:29:09 -0400 [thread overview]
Message-ID: <f7a714d9-b620-5100-a0e7-51360419eeda@bell.net> (raw)
In-Reply-To: <73bf3336-9207-ba0e-1950-8cb1b7d6adc3@bell.net>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On 2022-03-22 4:04 p.m., John David Anglin wrote:
> On 2022-03-22 3:37 p.m., Sam James wrote:
>> In our experience so far, there has been no good kernel version for us on this hardware.
> What happens with the attached config? My rp3440 runs okay with this config.
>>
>>> I've seen this before but it's not occurring in my current builds for rp3440 and c8000. I've been running for-next
>>> changes on c8000 for several weeks.
>>>
>> Yeah, I haven't seen this at all on my C8000 (or Gentoo's other HW, a C3600).
> Architecturally, there is no difference between rp3440 and c8000 with respect to the cache and TLB.
>
> As I said, the inequivalent alias are a memory mapping issue. This might vary depending on memory size.
Config might make a difference as well.
In order to debug, one needs to find the circumstances that cause it.
Dave
--
John David Anglin dave.anglin@bell.net
[-- Attachment #2: config-5.16.16+.gz --]
[-- Type: application/x-gzip, Size: 22500 bytes --]
next prev parent reply other threads:[~2022-03-22 20:29 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
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 [this message]
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=f7a714d9-b620-5100-a0e7-51360419eeda@bell.net \
--to=dave.anglin@bell.net \
--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