Alpha arch development list
 help / color / mirror / Atom feed
From: Michael Cree <mcree@orcon.net.nz>
To: Bob Tracy <rct@frus.com>
Cc: debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org
Subject: Re: 5.17.0 boot issue on Miata
Date: Sun, 27 Mar 2022 11:21:57 +1300	[thread overview]
Message-ID: <20220326222157.GA13650@tower> (raw)
In-Reply-To: <Yj0u150JJpsb9nj4@gherkin.frus.com>

On Thu, Mar 24, 2022 at 09:54:15PM -0500, Bob Tracy wrote:
> When I attempt to boot a 5.17.0 kernel built from the kernel.org
> sources, I see disk sector errors on my "sda" device, and the boot
> process hangs at the point where "systemd-udevd.service" starts.
> 
> Rebooting on 5.16.0 works with no disk I/O errors of any kind.

Oh, you can run a 5.16.y kernel on Alpha?  I have had problems
with everything since 5.9.y with rare, random, corruptions in
memory in user space (exhibiting as glibc detected memory
corruptions or segfaults).

This is why I am still running a 5.8.y kernel on the Debian
Ports buildd.

I just compiled up a 5.16.y kernel and the problem is still there.
It did take a bit to trigger the bug (about 10 hours of testing
before it happened).

I had done a bisection between 5.8.0 and 5.9.0 last year but I
think it went astray (as testing is difficult and not fool proof).
You email has prompted me to go back to it and see if I can nail
down the offending commit.  We really want to get it fixed.

Cheers,
Michael.


  reply	other threads:[~2022-03-26 22:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  2:54 5.17.0 boot issue on Miata Bob Tracy
2022-03-26 22:21 ` Michael Cree [this message]
2022-04-05  1:42   ` Bob Tracy
2022-04-05  5:01     ` Michael Cree
2022-04-05 13:55       ` Bob Tracy
2022-04-05 18:22         ` Helge Deller
2022-04-06 22:44           ` Bob Tracy
2022-04-08 13:02             ` Bob Tracy
2022-04-19  4:53               ` Bob Tracy
2022-04-25  9:26                 ` John Garry
2022-05-03 15:50                   ` Bob Tracy

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=20220326222157.GA13650@tower \
    --to=mcree@orcon.net.nz \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=rct@frus.com \
    /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