archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <>
To: Nick Bowler <>, Peter Xu <>
	Andrew Morton <>
Subject: Re: PROBLEM: sparc64 random crashes starting w/ Linux 6.1 (regression)
Date: Wed, 15 Feb 2023 15:49:56 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 31.01.23 02:46, Nick Bowler wrote:
> On 2023-01-29, Peter Xu <> wrote:
>> On Sat, Jan 28, 2023 at 09:17:31PM -0500, Nick Bowler wrote:
>>> Starting with Linux 6.1.y, my sparc64 (Sun Ultra 60) system is very
>>> unstable, with userspace processes randomly crashing with all kinds of
>>> different weird errors.  The same problem occurs on 6.2-rc5.  Linux
>>> 6.0.y is OK.
> [...]
>> Could you try below patch to see whether it fixes your problem?  It should
>> cover the last piece of possible issue with dirty bit on sparc after that
>> patchset.  It's based on latest master branch (commit ab072681eabe1ce0).
> Haven't seen any failures yet, so it seems this patch on top of 6.2-rc6
> makes things much better.
> I'll keep running this for a while to see if any other problems come up.

Nick, I assume no other problems showed up?

In that case Peter could send the patch in for merging. Or did you do
that already?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
If I did something stupid, please tell me, as explained on that page.

#regzbot ignore-activity

  reply	other threads:[~2023-02-15 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29  2:17 PROBLEM: sparc64 random crashes starting w/ Linux 6.1 (regression) Nick Bowler
2023-01-29 22:14 ` Peter Xu
2023-01-30  1:36   ` Nick Bowler
2023-01-31  1:46   ` Nick Bowler
2023-02-15 14:49     ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-02-15 15:21       ` Peter Xu
2023-02-16  5:32         ` Nick Bowler
2023-02-16 15:33           ` Peter Xu
2023-01-30  9:37 ` Linux kernel regression tracking (#adding)

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).