From: Bob Tracy <rct@frus.com>
To: Michael Cree <mcree@orcon.net.nz>,
debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org
Subject: Re: 5.17.0 boot issue on Miata
Date: Mon, 4 Apr 2022 20:42:38 -0500 [thread overview]
Message-ID: <YkuejknyPDJoQEDC@gherkin.frus.com> (raw)
In-Reply-To: <20220326222157.GA13650@tower>
On Sun, Mar 27, 2022 at 11:21:57AM +1300, Michael Cree wrote:
> 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).
Did we have this painted into the "SMP vs. not-SMP" corner at one point?
Miata is an automatic not-SMP case for hand-built kernels for that
architecture, which might explain why I'm not seeing the problems with
user space memory corruption.
Just successfully booted on v5.17-rc1 a little while ago. Moving on to
"-rc2".
--Bob
next prev parent reply other threads:[~2022-04-05 1:42 UTC|newest]
Thread overview: 12+ 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
2022-04-05 1:42 ` Bob Tracy [this message]
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-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=YkuejknyPDJoQEDC@gherkin.frus.com \
--to=rct@frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
--cc=mcree@orcon.net.nz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.