All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Tracy <rct@frus.com>
To: debian-alpha@lists.debian.org
Cc: mcree@orcon.net.nz, linux-alpha@vger.kernel.org
Subject: 5.17.0 boot issue on Miata
Date: Thu, 24 Mar 2022 21:54:15 -0500	[thread overview]
Message-ID: <Yj0u150JJpsb9nj4@gherkin.frus.com> (raw)

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.

Assuming the 5.17.0 kernel or its associated initrd had bad sectors, I
rebuilt both and saw no I/O errors during the build nor afterward when
copying the new kernel into place under "/boot".

Even tried a cross-compile build of a 5.17.0 alpha kernel on my x86_64
platform to save build time (34 hours for a native build on a PWS 433au
vs. 2 hours on the x86_64 platform).  That build produced identical
results when I tried booting on it.

If anyone else is seeing this and can get a head-start on bisecting,
that would be very much appreciated.  I won't be able to get to it for
about a week and a half :-(.  5.16.0 works.  5.17.0 doesn't.  Might get
lucky and find that the offending changes happened in the first 5.17.0
release candidate.

As always, sincere thanks in advance.

--Bob

             reply	other threads:[~2022-03-25  2:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  2:54 Bob Tracy [this message]
2022-03-26 22:21 ` 5.17.0 boot issue on Miata Michael Cree
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-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=Yj0u150JJpsb9nj4@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.