From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 170 testing report - "next/06b4164d" crashes on my x86_64 testing machine
Date: Sun, 07 Aug 2022 12:14:22 +0000 [thread overview]
Message-ID: <b2ff5516-eeb9-9b45-1be5-c45dbdc2f00b@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Hello all, especially Arne,
today, I upgraded to "IPFire 2.27 - Core Update 170 Development Build: next/06b4164d",
which primarily comes with Linux 5.15.59 and the slab cache merging disabled. On
my physical testing hardware, the boot process stalled after several kernel trace
message blocks being displayed.
Unfortunately, I was unable to recover them in detail, but they occurred fairly
early, roughly around the mounting of the root file system. Since the machine is
semi-productive (we all test in production, don't we? ;-) ), I went back to C169
and will now investigate further which change broke the update.
An earlier version of Core Update 170 (commit 668cf4c0d0c2dbbc607716956daace413837a8da,
I believe, but it was definitely after the randstruct changes) ran fine for days here,
so it must be a pretty recent change. Will keep you updated.
Thanks, and best regards,
Peter Müller
next reply other threads:[~2022-08-07 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 12:14 Peter Müller [this message]
[not found] <d4d5fe5f-08c5-df44-4ba6-0a77f16bf890@ipfire.org>
2022-08-08 9:50 ` Michael Tremer
2022-08-08 10:16 ` Peter Müller
2022-08-08 10:22 ` Michael Tremer
2022-08-08 14:15 ` Arne Fitzenreiter
2022-08-08 15:47 ` Peter Müller
2022-08-09 6:23 ` Arne Fitzenreiter
2022-08-09 8:27 ` Arne Fitzenreiter
2022-08-09 9:28 ` Peter Müller
2022-08-09 9:31 ` Michael Tremer
2022-08-09 10:26 ` Peter Müller
2022-08-09 10:37 ` Michael Tremer
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=b2ff5516-eeb9-9b45-1be5-c45dbdc2f00b@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/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