[[Plugin] autotweak]

On 4/17/2024 at 12:24 AM, Fuzzy0101 said:

I uploaded the new version 1.3.11

• Adds NVME SSD power management policy feature.
• Improves GUI field descriptions and consistency.

 

On 4/17/2024 at 2:19 PM, Fuzzy0101 said:

Yes. Probably buggy firmware.

It turns out you can disable L1.1 and L1.2 per device. 

If the pci address of the NVME is 01:00.0, you can disable L1.2 like this:

 

echo 0 > /sys/bus/pci/devices/0000\:01\:00.0/link/l1_2_aspm 

 

There are other switches in that directory to turn off other pm features:

l1_1_pcipm  l1_2_aspm  l1_2_pcipm  l1_aspm

 

Still no luck for me, Must be some deeper incompatibility issue specific with my mainboard/NVMe combination. Thank you anyway

 

If I'm not wrong kernel.org must have an ASPM blacklist somewhere in their kernel code since you can report buggy devices on the mailing list. It may be wise to not override this list until getting desperate.

If you can get your hands on it it may be good to implement/update it with each Unraid release since your plugin might ignore it.

[[Plugin] autotweak]

14 hours ago, Fuzzy0101 said:

 

Yes but also makes it probably very warm. I don't know how much you played with it to make it work, but may be you can try to disable only APST PS states deeper than PS3.
You can see the exlat parameters of PS3 and PS4 at the end of nvme id-ctrl /dev/nvme0
If you set nvme_core.default_ps_max_latency_us between the two value you can disable only PS4 
You can check the current PS state with: nvme get-feature -f 2 -H /dev/nvme0
 

 

Sadly it still doesnt work. Even with 0 the NVMe keeps crashing so i guess its a whole another issue on L1.1 and L2.2 that is pcie related.

[[Plugin] autotweak]

nvme_core.default_ps_max_latency_us=0 as a bootflag should do the trick against buggy NVMe low power state.

[[Plugin] autotweak]

On 4/10/2024 at 11:33 PM, Fuzzy0101 said:

 

In the next release I changed it to schedutil in balanced profile on cpus that don't have pstate driver. Otherwise it uses powersave.

I don't have a system with AMD CPU to test it. But I have a 6.6.22 kernel compiled myself...

 

ASPM is tuned through a global kernel parameter not per device.

Did you try to update the firmware of your NVMe? I updated my WD NVMe with nvme-cli.

 

 

Thanks for the answer. I use amd_pstate since a while without any issue whatsoever on other devices with fitting hardware and of course newer kernel.

As for ASPM i wasnt sure if blacklisting is possible as it seems it need to be driver specific. For example the amdgpu driver allows to do so with amdgpu.aspm=0

 

The NVMe is uptodate, so no luck here. But its nearing its end of life anyway so i will keep attention on the next purchase. For example the newer KIOXIA NVMe with TLC and DRAM supports officially L1.1 and L1.2.

[[Plugin] autotweak]

On 4/6/2024 at 11:52 PM, DuzAwe said:

Could we get the conservative power governor?

Also amd_pstate=active (with the upcoming 6.6 kernel) for Zen2 and newer AMD CPUs. After that the performance and especially the powersave governor are working way better.

 

Schedutil should be also preferred before ondemand/performance if amd_pstate is not availabe for your CPU.

 

Also the possibility to blacklist certain devices yourself. For example my M.2 SSD doesn't like L1+ (L1.1 and L1.2) but the rest seems fine.

 

PS:

 

Quote

[c0a9:540a] 01:00.0 Non-Volatile memory controller: Micron/Crucial Technology P2 [Nick P2] / P3 / P3 Plus NVMe PCIe SSD (DRAM-less) (rev 01)

[N:0:1:1] disk CT1000P2SSD8__1 /dev/nvme0n1 1.00TB

In the case you want to blacklist the M.2 for everybody.

[[Plugin] Swapfile for 6.9.1]

On 3/29/2024 at 7:44 PM, primeval_god said:

Logs (specifically anything that mentions swapfile) and the specifics of your settings would be helpful. Also the actual unRAID Version as i am not certain what the last 2 minor releases were. 
 

Will try again once parity is fully sync again in about 24 hours since i couldn't really check for logs and didn't save them otherwise before crashing. Had to hard reset the system yesterday after it got unresponsive and didn't do the regular shutdown over the case shutdown button. What i stated was only what i could perceive in the "surviving" unresponsive ssh htop shell. After uninstalling the plugin system is stable again. But since some workload i use likes a lot of ram i still need this plugin on the long run .

 

PS: Nothing special in the logs, for now it seems to work again without any issues.

[[Plugin] Swapfile for 6.9.1]

Since the last 2 minor unraid updates it seems that mkswap can't grab the created swapfile anymore (on xfs), resulting in a massive CPU load (50 to over 100 load on a 16 thread CPU) ending in the system being unresponsive.

[[Support] A75G Repo]

Hallo and first: thank you

 

22 hours ago, A75G said:

For tags this is my standard so i cant do anytihng but the thing about docker is you can switch which version using the tags.

Exactly this seems not to work. No matter if i change from "phlak/mumble:latest" to "phlak/mumble:1.3.2" or vice versa, 1.3.1 is pulled down.

 

22 hours ago, A75G said:

and lastly renaming it to murmur the repo i use called it mumble, it might confused people but i can switch it if you feel its for the best

Maybe adding "murmur" in the description can resolve both issues? That way, people looking for both should be able to find the docker.

[[Support] A75G Repo]

Hi @A75G,

 

thank you for your work, so far im using your murmur/mumble docker.

 

Still, i have some suggestions for this particular docker:

1. Rename the docker with "murmur", since this is the real name of the server application for mumble.
2. The Project Page is not mumble.com, but mumble.info.
3. Latest and 1.3.2 branches doesn't pull 1.3.2 but 1.3.1.

Greetings

 

[Unraid Forum 100K Giveaway]

So first time posting i guess

 

What i like so far: user friendly in any way.

 

What i want for 2020: built in possibilities for external backup of important data (cloud, any kind of external drives or network storages).