From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: CU178 kernel fixes Testing
Date: Mon, 14 Aug 2023 13:26:15 +0200 [thread overview]
Message-ID: <82b3acc4-29d5-47c2-9058-2e512fdb6e72@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
Hi All,
I didn't see any further notification about the kernel fixes in CU178 being available to test but looking in the Changelog in the nightlies it seemed that the fixes were available in the CU178 version in master.
So I have tested it on 2 vm systems that I have.
After update the systems were on 178 Development Build master/41e33931. During the reboot on both systems no issues were found and no red warning messages.
OpenVPN RW and N2N both worked as normal after the update.
Ran for a couple of hours and did a range of web activities.
Everything worked as expected and all graphs reviewed showed data as normally expected.
No problems found.
Regards,
Adolf.
next reply other threads:[~2023-08-14 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 11:26 Adolf Belka [this message]
2023-08-14 11:28 ` Adolf Belka
2023-08-14 14:03 ` Michael Tremer
2023-08-15 15:54 ` Peter Müller
2023-08-15 16:45 ` Michael Tremer
[not found] <D30F7F36-7A1D-42B6-AA52-D79B91B3DF16@ipfire.org>
2023-08-14 15:40 ` Adolf Belka
2023-08-14 15:57 ` Michael Tremer
2023-08-14 15:42 ` Michael Tremer
2023-08-14 16:37 ` Adolf Belka
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=82b3acc4-29d5-47c2-9058-2e512fdb6e72@ipfire.org \
--to=adolf.belka@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