public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Kernel 6.18 fist tests...
Date: Wed, 17 Dec 2025 14:50:53 +0100	[thread overview]
Message-ID: <57905d1bd3feb93af1322e1229c325fbf4902d4e.camel@ipfire.org> (raw)
In-Reply-To: <acfbb12a98a6deff9302fca036e481d5@ipfire.org>

Hi Arne, hi all,

Am Donnerstag, dem 11.12.2025 um 13:00 +0100 schrieb Arne Fitzenreiter:
> Hi,
> 
> i have compiled a first test kernel 6.18 for x86_64.
> 
> https://people.ipfire.org/~arne_f/highly-experimental/kernel/
> 
> please help testing and report your findings...
> 
> Arne


I have been running kernel-6.18.1-ipfire.x86_64 for over a day now on
real (quite old) hardware and everything is working perfectly so far.

Hardware:
- SECO 0949 motherboard
- Intel Atom N2600 @ 1.6 GHz (4 threads), 2 GB RAM
- 2× Realtek RTL8111/8168 (r8169 driver) – green0 and red0 at 100 Mbps
- USB Wi-Fi: Ralink RT5572 (rt2800usb) – blue0
- Crucial BX500 240 GB SSD

Installation as described in the README (with fixed typo) went
smoothly. dracut correctly included the initqueue module, and grub-
mkconfig placed the new kernel at the top.

Tested (all working flawlessly):
- Normal boot (multiple reboots)
- Web interface
- Internet access via RED
- Clients browsing normally behind GREEN and BLUE (Wi-Fi stable)
- OpenVPN tunnel (tun0) starts, routes are set
- WireGuard interface (wg0) present
- No kernel errors/warnings in dmesg
- System stable for 18+ hours, normal RAM usage, no swap

Additional stress tests:
- CPU stress (stress --cpu 4 for ~15 minutes):
  - Load average ~4.0–4.3 (100% on all threads)
  - CPU frequency stable at 1596 MHz (no throttling)
  - Temperatures max. 56°C (Core 1) / 55°C (zone) – safe and cooled
down quickly
  - No kernel errors

- Network tests:
  - LAN TCP (client to IPFire green0): stable 94 Mbits/sec (full link
speed)
  - LAN UDP overload: ~60 Mbits/sec with only 4.4% loss (expected on
100 Mbps link)
  - Local loopback TCP (4 parallel streams): ~2.71 Gbits/sec aggregate
  - Local loopback UDP: 25.3 Mbits/sec with 0% loss
  - No packet errors on r8169 interfaces (ethtool -S shows all error
counters at 0)
  - No drops in /proc/net/softnet_stat

Conclusion: On this older low-power hardware, kernel 6.18.1 runs
absolutely stable with no noticeable regressions – network performance
is excellent and the system handles both CPU and network load very
well.

I will keep it running as my daily driver and report if anything
changes.

Many thanks for the test builds, Arne – great work!

Best,

Erik


  parent reply	other threads:[~2025-12-17 13:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 12:00 Arne Fitzenreiter
2025-12-11 13:57 ` Adam Gibbons
2025-12-11 17:20   ` Adolf Belka
2025-12-11 17:28     ` Adolf Belka
2025-12-11 18:04       ` Adolf Belka
2025-12-11 21:01         ` Michael Tremer
2025-12-11 22:35           ` Adolf Belka
2025-12-12 11:30             ` Adolf Belka
2025-12-12 13:57               ` Adolf Belka
2025-12-15 11:46                 ` Adolf Belka
2025-12-15 20:13                   ` Adam Gibbons
2025-12-17 13:50 ` ummeegge [this message]
2025-12-17 15:38   ` ummeegge

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=57905d1bd3feb93af1322e1229c325fbf4902d4e.camel@ipfire.org \
    --to=ummeegge@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