Aoostar WTR Pro kernel issues

system: aoostar wtr pro, 5825U 4 bay

ever since several updates ago, around 25.10.3-ish and later after all the kernel security updates, the system would hang if I did not disable C6.

on update, 25.10.6, the system would boot and freeze/hang. Tried 25.10.7, same issue

I saw the disk size stuff bugging out

then I saw ethernet loop flapping in the middle of my jellyfin stream/transcoding testing

Oct 09 08:36:39 snuwtrpro kernel: br-3e17519bc528: port 6(vethbdba881) entered blocking state
Oct 09 08:36:39 snuwtrpro kernel: br-3e17519bc528: port 6(vethbdba881) entered disabled state
Oct 09 08:36:39 snuwtrpro kernel: vethbdba881: entered allmulticast mode
Oct 09 08:36:39 snuwtrpro kernel: vethbdba881: entered promiscuous mode
Oct 09 08:36:39 snuwtrpro kernel: eth1: renamed from veth3c9cfa0
Oct 09 08:36:39 snuwtrpro kernel: br-3e17519bc528: port 6(vethbdba881) entered blocking state
Oct 09 08:36:39 snuwtrpro kernel: br-3e17519bc528: port 6(vethbdba881) entered forwarding state

this but repeated dozens of times, I think my router eventually kicked it off the LAN until I reset the router itself

then now it boots and immediately crashes/freezes, reverting to older kernel doesn’t work as it can’t find the debug kernel from prior releases for some strange reason

I did try live booting a ubuntu liveiso (latest) and it also freezes so I believe it’s a newer kernel issue.

I did update the BIOS to the latest available one on the Aoostar website and the machine no longer hangs but it did reset a few times on its own which should not happen (but at least it stopped freezing/hanging)

I tried ubuntu 26.04 liveiso old bios, hangs kernel 7.0

ubuntu 24.04 liveiso old+new bios, does not hang. kernel 6.8

I don’t know where to report this issue and I mainly use truenas, so please excuse the sloppy writing and tell me what logs/details to provide so this can be sent upstream. I’m also (of course) in the middle of pulling my hair out to see if I can make sure it’s stable before freaking out some more.

https://www.reddit.com/r/Kubuntu/comments/1vfjxi9/kernel_70028_29_shutdown_hangup_amdgpu_driver/

https://askubuntu.com/questions/1566809/ubuntu-26-04-lts-probably-unstable-driver-amdgpu

testing w/ blacklisting amdgpu module from kernel now, looks like that + current kernel version is the culprit.

truenas 25.10.7 kernel version 6.12.105-production+truenas need to blacklist amdgpu in kernel or else it’ll keep resetting

midclt call system.advanced.update ‘{“kernel_extra_options”:“amdgpu.dcdebugmask=0x10”}’ still crashes, not the problem

downgrading attempts:

25.10.7 - crash | kernel 6.12.105

25.10.6 - crash | kernel 6.12.99

25.10.4 - crash | kernel 6.12.91

25.10.3.1 - crash | kernel 6.12.33

25.10.3 - crash | kernel 6.12.33

25.10.2 - crash | kernel 6.12.33

I’m beginning to suspect something in the jellyfin container caused the crash. The machine hung when I was starting and stopping a transcode. Trying to clear the transcode dir by destroying the container and recreating it, also by stopping the jellyfin container so it stops running by default when the system starts up.

jellyfin container recreated (tmpfs + transcode folder deleted/destroyed), host not down

looks like it’s a bug in amdgpu driver for all versions/upstream, has nothing to do with truenas kernel versions it seems. jellyfin using ffmpeg using amdgpu should never crash the host like that.

starting jellyfin → host crashed again

starting truenas → no /dev/dri passed to jellyfin, amdgpu enabled for all other containers from before → no crash o_O

there might be 2 issues going on, hard stall/frozen, and a reboot that resets the machine

I suspect the one that resets the machine is the c6 disable that’s required and the hard stall is amdgpu, something going on with jellyfin+immich

might’ve been a combination of 4k media import/thumbnail generation/trickplay + transcoding, not sure. it also just crashed when I opened my ssh client to remote in for some reason.

but after that reboot (and the 12 hours in between where /dev/dri was removed from jellyfin and immich, I’m guessing allowing the background processing to be done on cpu) the machine is now stable again on latest 25.10.7.

machine still crashing, trying 27.0.0-RC.1 kernel 6.18.52

the fix was destroying all containers and networks, then starting all the stacks back up. had nothing to do w/ amdgpu.

amdgpu was likely a red herring because it prevented a few containers from starting up due to compose dependencies, but once those were started the machine would crash as well.

Looks like a docker networking bug, not an amdgpu bug.

Just to clarify, blacklisting AMDGPU didn’t stop the crashes; it prevented four containers/3-4 networks from starting and delayed the crash which still happened. Previously was crashing in under 3-5mins of startup, now it’s been stable for >24hrs. Suspected Docker/container-network state issue.

Welp, another day another update.

Machine started crashing again so I brought down all containers, destroyed them, and destroyed all docker networks. It was still crashing on boot screen even though NO containers were being loaded.

I guessed if it was an amdgpu issue, so I blacklisted the driver and surprise, machine starts booting again and running without issue.

I think there is something broken between the docker networks and amdgpu causing the host to crash regardless of kernel. I’ve disabled amdgpu for now in the hopes a later kernel or docker version will be more stable. Maybe the issue is a combination factor of both docker networking + amdgpu.

Edit: looks like these are related

https://gitlab.freedesktop.org/drm/amd/-/work_items/5196

https://www.reddit.com/r/archlinux/comments/1p9kt9l/newest_firmware_causes_amd_gpu_crash/

https://bbs.archlinux.org/viewtopic.php?id=310497

https://bbs.archlinux.org/viewtopic.php?id=299954

https://bbs.archlinux.org/viewtopic.php?id=311628

https://github.com/void-linux/void-packages/issues/53787

I moved the physical disks (ssds + hdds) to a 2 bay N150 Aoostar R1

no crashes, no issues. same 70 containers, same appdata, same truenas install/config.

looks more and more like an amd platform (amdgpu + kernel) bug to me.

It’s a motherboard issue. I obtained a friend’s 5825U wtr pro and his booted ubuntu 26.04.1 perfectly fine, mine would crash/hang most times. Swapped RAM, PSU (from working set) and mine still would crash. No storage in both. Mine would also hang if ethernet was plugged in. Died after ~20 months.

Looks like only solution is to get a new unit.