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: Tue, 5 Apr 2022 17:01:25 +1200 [thread overview]
Message-ID: <20220405050125.GA25969@tower> (raw)
In-Reply-To: <YkuejknyPDJoQEDC@gherkin.frus.com>
On Mon, Apr 04, 2022 at 08:42:38PM -0500, Bob Tracy wrote:
> 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?
No, this affects both ES45 (with 3 cpus) and XP1000 (one cpu).
The problem is rare. I often have to run tests for 12 hours on
the XP1000 before I see a problem. On miata it might occur even
less often.
I hope I am getting close to the bad commit, but it is taking
time when I run testing for a whole day before I feel confident
enough to mark the kernel as good. And I have been wrong on
that one a couple of times now, having to repeat part of the
bisection.
Cheers,
Michael.
next prev parent reply other threads:[~2022-04-05 5:01 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
2022-04-05 5:01 ` Michael Cree [this message]
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=20220405050125.GA25969@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 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.