Hello, i am currently using Unraid as OS and can't reach any higher C-States then C2/C3 while the Networkcable is pluged in. If i unplug the Network-Cable the system reaches immediately higher C-States (C6-C8) Asked the Mainboard Vendor for issue or dependency and Asus told me there are no issues and they can reach higher C-States in Powerhouse Mountain so it should be an Linux issue. Which Information do you need? Greetings JT
Created attachment 305892 [details] Powertop whit Networkcable Unraid
Created attachment 305893 [details] Asus Support Windows with PowerHousemountain
According to creator of powertop, issue is caused by a bug in the kernel driver for the Intel I226-V ethernet network controller. https://github.com/fenrus75/powertop/issues/143
Can replicate bug on an Odroid H4+ board running Ubuntu Server 24.04 LTS.
Bug still present in new release Ubuntu 24.04.1 LTS. Driver fails when power management is activated.
When enabling the power-saving tunable for the Intel Ethernet Controller I226-V using powertop, the system hangs. This issue occurs consistently and requires a hard reboot to recover. The problem persists across multiple kernel versions. Manually enabling the tunable using `echo "auto" > /sys/bus/pci/devices/0000:05:00.0/power/control` also causes the system to hang. Steps to Reproduce: Install powertop on a system with the Intel Ethernet Controller I226-V. Run powertop with superuser privileges: sudo powertop. Navigate to the Tunables tab. Enable the tunable for the Intel Ethernet Controller I226-V. Alternatively, manually enable the tunable using: echo "auto" > /sys/bus/pci/devices/0000:05:00.0/power/control. Observe that the system hangs and becomes unresponsive. Expected Result: The Ethernet controller should enter a low-power state without causing the system to hang. Actual Result: The system hangs and becomes unresponsive, requiring a hard reboot.
i can confirm that the system gets unresponsive if your turn on power saving.
Hey guys. Kernel 6.12 (new LTS) dropped a few months back. I read somewhere that the issue was solved around ~6.11 kernel. Can anyone of you please confirm the issue is solved in 6.12?