public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: John David Anglin <dave.anglin@bell.net>
Cc: Helge Deller <deller@gmx.de>,
	 "Andreas K. Huettel" <dilfridge@gentoo.org>,
	 Florian Weimer <fweimer@redhat.com>,
	 Helge Deller <deller@kernel.org>,
	 libc-alpha@sourceware.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH] hppa: Wire up cacheflush syscall
Date: Thu, 26 Sep 2024 20:08:07 +0100	[thread overview]
Message-ID: <87ikuiutbc.fsf@gentoo.org> (raw)
In-Reply-To: <e959c48b-8584-440a-a46e-a7442043076f@bell.net> (John David Anglin's message of "Sat, 3 Aug 2024 04:57:47 -0400")

John David Anglin <dave.anglin@bell.net> writes:

> On 2024-07-09 9:41 a.m., Sam James wrote:
>> In this instance, I wonder if we should do the extra checks. The kernel
>> instability because of the cache / TLB issues means at least one of our
>> machines runs an older kernel for now. (Dave's latest patches seem to
>> help a lot there, but you get the point.)
> Can you be more specific?  Do you still experience instability due to cache / TLB issues
> on this machine?

Sorry for the delay. Our main machine, 'muta', has been suffering
instability for a while. It ended up also having bad RAM and failing
disks. We've now replaced them last night.

We had a lot of kernel crashes since then but after upgrading to
6.10.11, everything seems okay so far. Fingers crossed, and then I can
get back to the other bits (like testing the binutils patch).

(The panics were all in pte_offset_map_nolock.)

>
> Dave

thanks,
sam

  reply	other threads:[~2024-09-26 19:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08  1:10 [PATCH] hppa: Wire up cacheflush syscall Helge Deller
2024-07-08  8:13 ` Florian Weimer
2024-07-08  8:58   ` Helge Deller
2024-07-08 16:00     ` Andreas K. Huettel
2024-07-08 18:26       ` Helge Deller
2024-07-09 13:41         ` Sam James
2024-08-03  8:57           ` John David Anglin
2024-09-26 19:08             ` Sam James [this message]
2024-09-27  7:16               ` Helge Deller

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=87ikuiutbc.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=deller@kernel.org \
    --cc=dilfridge@gentoo.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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