DietPi Trixie crashes on my PC, Bookworm can't update

Troubleshooting
1

Hi everyone here is my pc:

HP t5565 Thin Client – Core Hardware Specs

CPU

  • VIA Nano u3500

  • 1.0 GHz, single-core, 64-bit capable

  • Fanless (ultra-low power Isaiah core)

Chipset / Motherboard

  • VIA VX900 (unified North/South Bridge Media System Processor)

  • Integrated: Chrome9 HD graphics (ChromotionHD 2.0), SATA, USB, Audio, PCIe

Key Integrated PCI Devices (lspci summary)

  • Host bridges: Multiple VX900 functions (00:00.0–00:00.7) – control, DRAM, power, APIC, etc.

  • Graphics: VIA VX900 Chrome9 HD (00:01.0)

  • Audio: VIA 9170 (00:01.1) + VT8237A/VT8251 HDA (00:14.0)

  • PCIe: VX900 Root Ports x4 (00:03.0–00:03.3) + PHY (00:03.4)

  • SATA: VX900 Serial ATA Controller (00:0f.0)

  • USB: 3× UHCI USB 1.1 (00:10.0–00:10.2) + USB 2.0 (00:10.4)

  • ISA bridge: VX900 (00:11.0)

  • South-North interface: VX8xx (00:11.7)

  • PCI-to-PCI bridge: VX900 (00:13.0)

  • NIC: Broadcom BCM57780 Gigabit Ethernet PCIe (05:00.0)

Cant run DietPi Trixi (crashes when bootup), so no access to logs, only some error on screen (should’ve taken a picture…) It happened to my with every release of trixie. So its not specific to 10.1.
Can run Bookworm, but can’t update, here is the pic:

image
image1599×899 223 KB

How can I make it update?
Why trixie crashes? Should I provide pic? Should I test Forky?
Thanks

2

EDIT: Well, I only installed SAMBA, DietPi Dashboard, FTP, and when copying 30gb of files, it crashed HARD:

image
image1599×899 353 KB

3

For the first error, can you check that your system time is correct.

1 Like
4

Thanks to chatgpt, I seemed to fix the fatal crash. I managed to copy 100gb (1 file!) and 30 700mb files without a crash.

Here is the solution:

Kernel Panic Under Heavy Samba Load on VIA Eden (Fixed)

Problem:
On a VIA Eden 3500U system running DietPi (Debian kernel 6.x), the server crashed during large file transfers (30–100GB over Samba). The kernel panic occurred in:

memcg_slab_post_alloc_hook

This indicates a crash in the memory cgroup (memcg) subsystem under heavy I/O and slab allocator activity.

Cause:
Kernel 6.x memory cgroups are unstable on some legacy VIA hardware under sustained load. Not a RAM or disk failure.

Solution:
Disable memory cgroups at boot.

Edit:

/etc/default/grub

Modify:

GRUB_CMDLINE_LINUX_DEFAULT="consoleblank=0"

To:

GRUB_CMDLINE_LINUX_DEFAULT="consoleblank=0 cgroup_disable=memory"

Then run:

update-grub
reboot

Result:
System became fully stable under 100GB sustained transfers at 100% CPU load.

This fix is safe if you’re not using Docker or container memory limits.

5

Nope:
Details:

  • Date | 2026-02-26 00:20:13
  • Program name | DietPi-Update
  • Command | apt-get -y -eany update
  • Exit code | 100
  • DietPi version | v10.1.2 (MichaIng/master)
  • Distro version | bookworm (ID=7)
  • Kernel version | Linux DietPi-Thin 6.1.0-43-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.162-1 (2026-02-08) x86_64 GNU/Linux
  • Architecture | amd64
  • Hardware model | Native PC (x86_64) (ID=21)

Additional logs:

Ign:1 https://dietpi.com/apt bookworm InRelease
Hit:2 https://deb.debian.org/debian bookworm InRelease
Hit:3 https://deb.debian.org/debian bookworm-updates InRelease
Hit:4 https://deb.debian.org/debian-security bookworm-security InRelease
Hit:5 https://deb.debian.org/debian bookworm-backports InRelease
Ign:1 https://dietpi.com/apt bookworm InRelease
Ign:1 https://dietpi.com/apt bookworm InRelease
Err:1 https://dietpi.com/apt bookworm InRelease
  Certificate verification failed: The certificate is NOT trusted. The signature in the certificate is invalid.  Could not handshake: Error in the certificate verification. [IP: 2606:4700:20::ac43:4539 443]
Reading package lists...
E: Failed to fetch https://dietpi.com/apt/dists/bookworm/InRelease  Certificate verification failed: The certificate is NOT trusted. The signature in the certificate is invalid.  Could not handshake: Error in the certificate verification. [IP: 2606:4700:20::ac43:4539 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
6

This is a simple certificate issue for apt package manager. It has nothing to do with a system crash. As already requested by @Jappe, did you verified your system time?

7

Hi. Yeah, 2 different problems:

1st, kernek crash due to memory cgroup (memcg), already fixed.
2nd apt certificate issue, and yes, system time is correct.

@Jappe any idea how fix on apt certificate issue for boorworm?

8

for me the certificate is correct and working. Might be something local or on the way between your and our server. As well you are the only one reporting this. I would experte more users to have the issue if it would be on our server.

Can you try to open Index of /apt on a local browser and check the certificate?