Kernel 6.18.20-1 breaks networking

[Rapty]

because some of us are not concerned by this bug I'm wondering if it could be linked to a kernel related software and the way Arch handles it.

I'm using iptables-nft (now just "iptables") and wireguard. What about people with this issue ? and people without ?

[df8oe]

Yes, I think, too the problem pops up when specific services or other software is used. But I have no idea what I can test - there is much software on my rpi4b running... I am using iptables, too.

Interesting is that virtual devices (docker network devices) are affected, too. Complete network breaks.

[df8oe]

On Github now it is silent around this bug since about one week. I do not want to break my system and chroot into to repair if new kernel also fails (it is a production system). Are there informations if this is fixed in 6.18.24-1 ?

[Rapty]

@df8oe
It's not fixed in 6.18.26-1

[df8oe]

That is bad. Can anyone build a kernel package without "EEE-commit" so that I can test if this is the cause?

[Rapty]

Hello !
Things are moving on Raspbian side, it seems many people are now impacted.

There is a workaround, switching off EEE.

If you are luckey, you can simply put 'dtparam=eee=off' in your '/boot/config.txt'.
If you're not, you have to use 'ethtool' to swith it off :

Check your current status:
ethtool --show-eee end0
Swith it off:
ethtool --set-eee end0 eee off

On my side, I'm lucky, config.txt is enough.
Currently running Linux Pi4 6.18.29-1-rpi for more than 11 min

Cheers

[df8oe]

On my side, neither config.txt nor kernel parameter in cmdline.txt switches eee reliable off. Even if I switch it off via ethtool it is magically enabled again a few seconds later...

But there is a new kernel available for testing - hopefully this is soon available for us and not only for Debian based systems...

[graysky]

6.18.32-1 is building now

[df8oe]

@graysky: Thank you for providing this. Using this build I can disable EEE and the issue is gone. I do not need EEE so for me everything is perfect now. But of course I am very interested what is the root cause of this strange issue - I will observe it until it is solved...