Comment # 3 on bug 1188019 from
Hello,

I find the solution finally.

1. First, my rpi2 is Raspberry Pi 2 Model B Rev 1.1, which use a different CPU
from Rev 1.2.
2. I reinstall Raspbian Buster lite, there is no this problem (using DHCP). So
my rpi2 is not broken.
3. Then I reinstall to OpenSUSE 15.3
(openSUSE-Leap-15.3-ARM-JeOS-raspberrypi2.armv7l-2021.05.31-Build8.1.raw.xz)
   If I use DHCP, there are huge of logs like these, and CPU still very high
from wicked:

> Jul 22 21:41:49 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:49 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:49 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:49 localhost wickedd[1007]: route ipv4 0.0.0.0/0 via 192.168.60.21 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv4:dhcp lease
> Jul 22 21:41:49 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:49 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:49 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:50 localhost wickedd[1007]: route ipv4 0.0.0.0/0 via 192.168.60.21 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv4:dhcp lease
> Jul 22 21:41:50 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:50 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:50 localhost wickedd[1007]: route ipv4 0.0.0.0/0 via 192.168.60.21 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv4:dhcp lease
> Jul 22 21:41:50 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:50 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:50 localhost wickedd[1007]: route ipv4 0.0.0.0/0 via 192.168.60.21 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv4:dhcp lease
> Jul 22 21:41:50 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:50 localhost wickedd[1007]: route ipv4 0.0.0.0/0 via 192.168.60.21 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv4:dhcp lease
> Jul 22 21:41:50 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:50 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)
> Jul 22 21:41:50 localhost wickedd[1007]: route ipv4 0.0.0.0/0 via 192.168.60.21 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv4:dhcp lease
> Jul 22 21:41:50 localhost wickedd-dhcp4[969]: eth0: Committed DHCPv4 lease with address 192.168.60.120 (lease time 4294967295 sec, renew in 2147483647 sec, rebind in 536870911 sec)


So I set static IP to this rpi2:
> cat /etc/sysconfig/network/ifcfg-eth0
> IPADDR='192.168.60.120/24'
> BOOTPROTO='static'
> STARTMODE='auto'

> cat /etc/sysconfig/network/ifroute-eth0
> default 192.168.60.21 - eth0

Then the CPU comes to 0 now. :)

and "journalctl -n 10" do not show these DHCP infos.

So, somethings wrong with wicked dhcp? Or is it normal that wicked will cause
high CPU when request DHCP?


You are receiving this mail because: