From: "Linux kernel regression tracking (#adding)" <email@example.com>
To: Nick Bowler <firstname.lastname@example.org>,
Cc: Peter Xu <email@example.com>
Subject: Re: PROBLEM: sparc64 random crashes starting w/ Linux 6.1 (regression)
Date: Mon, 30 Jan 2023 10:37:48 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
On 29.01.23 03:17, 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.
> Usually, it manifests with ssh connections just suddenly dropping out
> like this:
> malloc(): unaligned tcache chunk detected
> Connection to alectrona closed.
> but other kinds of failures (random segfaults, bus errors, etc.) are
> seen too.
> I have not ever seen the kernel itself oops or anything like that, there
> are no abnormal kernel log messages of any kind; except for the normal
> ones that get printed when processes segfault, like this one:
> [ 563.085851] zsh: segfault at 10 ip 00000000f7a7c09c (rpc
> 00000000f7a7c0a0) sp 00000000ff8f5e08 error 1 in
> I was able to reproduce this fairly reliably by using GNU ddrescue to
> dump a disk from the dvd drive -- things usually go awry after a minute
> or two. So I was able to bisect to this commit:
> 2e3468778dbe3ec389a10c21a703bb8e5be5cfbc is the first bad commit
> commit 2e3468778dbe3ec389a10c21a703bb8e5be5cfbc
> Author: Peter Xu <email@example.com>
> Date: Thu Aug 11 12:13:29 2022 -0400
> mm: remember young/dirty bit for page migrations
> This does not revert cleanly on master, but I ran my test on the
> immediately preceding commit (0ccf7f168e17: "mm/thp: carry over dirty
> bit when thp splits on pmd") extra times and I am unable to get this
> one to crash, so reasonably confident in this bisection result...
> Let me know if you need any more info!
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
#regzbot ^introduced 2e3468778dbe3ec3
#regzbot title sparc64: random crashes
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.
Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-01-30 9: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)
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) [this message]
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).