PC Engines apu2 experiences
-
@logan5247 said in PC Engines apu2 experiences:
pfSense 2.4.5 is available.
Announcement here
https://www.netgate.com/blog/pfsense-2-4-5-release-now-available.htmlNetgate recommends holding on remote upgrades, due to COVID-19 travel restrictions and remote working.
https://www.netgate.com/blog/pfsense-upgrade-guidance-during-covid-19-travel-restrictions.htmlJust updated an APU2D4 to 2.4.5, no issues so far. I don't run anything crazy (no VPN, IDS/IPS, blocking, etc...), just a couple VLANS. I did uninstall all my packages first, then did the upgrade, then reinstalled the packages.
-
PC Engines / 3mdeb have released new coreboot firmware:
Mainline v4.11.0.5 (link https://pcengines.github.io/#mr-33)
No major changes although a few features of interest:
- enabled PCI Express power management capabilities. ASPM can be used to increase client device power savings ... whilst not really aimed at FreeBSD/pfSense users it may be of interest for other OS projects
- added PCI Express endpoint reset logic at boot. 3mdeb commented that this should improve detection of PCI Express modules.
- added thermal zone definition in ACPI. This allows FreeBSD (and thus pfSense dashboard) to derive temperature via ACPI without any further configuration (ie System / Advanced / Miscellaneous / Thermal Sensors can be left on default None/ACPI)
Probably not worth upgrading unless any of these fixes are of particular interest.
Regardless I've updated my test system and it's running fine so far.
-
@dugeem Thanks for the report.
-
Please do me a favor:
Enter this at the command prompt:
sysctl dev.cpu.0.freq
and post the result.
Thank you very much,
fireodo -
@fireodo said in PC Engines apu2 experiences:
sysctl dev.cpu.0.freq
sysctl: unknown oid 'dev.cpu.0.freq'Appears the sysctl dev.cpu tree is missing. I'm running pfSense 2.4.5. It might be useful if someone still running 2.4.4-p3 can verify if behaviour is same to rule out FreeBSD 11.3 as cause.
-
@dugeem said in PC Engines apu2 experiences:
@fireodo said in PC Engines apu2 experiences:
sysctl dev.cpu.0.freq
sysctl: unknown oid 'dev.cpu.0.freq'Appears the sysctl dev.cpu tree is missing. I'm running pfSense 2.4.5. It might be useful if someone still running 2.4.4-p3 can verify if behaviour is same to rule out FreeBSD 11.3 as cause.
Go back to Bios 4.11.0.4 and you are set! I have done myself yesterday the same thing but I wasnt shure, thats why I asked you to enter that line.
-
@fireodo Maybe report it? Just checked and can confirm 2.4.5 and bios 4.11.0.4 gives
[2.4.5-RELEASE][root@pfSense.localdomain]/root: sysctl dev.cpu.0.freq dev.cpu.0.freq: 1000 -
@Qinn said in PC Engines apu2 experiences:
@fireodo Maybe report it? Just checked and can confirm 2.4.5 and bios 4.11.0.4 gives
[2.4.5-RELEASE][root@pfSense.localdomain]/root: sysctl dev.cpu.0.freq dev.cpu.0.freq: 1000Done: https://github.com/pcengines/coreboot/issues/389
Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
pfsense 2.7.2 CE
Packages: Apcupsd Cron Iftop Iperf LCDproc Nmap pfBlockerNG RRD_Summary Shellcmd Snort Speedtest System_Patches. -
@fireodo said in PC Engines apu2 experiences:
@Qinn said in PC Engines apu2 experiences:
@fireodo Maybe report it? Just checked and can confirm 2.4.5 and bios 4.11.0.4 gives
[2.4.5-RELEASE][root@pfSense.localdomain]/root: sysctl dev.cpu.0.freq dev.cpu.0.freq: 1000Sorry I'm in Home Office - I have not so much time ...
Before there can be a report, we need to be sure if this i bug is for all apu2 or specific to certain versions, as I see you use a C0 and I a C4.
At the moment I cannot upgrade to 4.11.0.5 as I cannot "Halt" this router, maybe later in the day...
-
@fireodo said in PC Engines apu2 experiences:
@Qinn said in PC Engines apu2 experiences:
@fireodo Maybe report it? Just checked and can confirm 2.4.5 and bios 4.11.0.4 gives
[2.4.5-RELEASE][root@pfSense.localdomain]/root: sysctl dev.cpu.0.freq dev.cpu.0.freq: 1000Done: https://github.com/pcengines/coreboot/issues/389
Kudos!
-
@Qinn It seems to be a good strategy to NOT do software/BIOS/firmware updates immediately after release. Lets first wait for others to burn themselves, then when the fire is put out, do the update.
-
Did anyone experience similar issues with their APUs?
https://forum.netgate.com/topic/151963/throughput-issues-on-pfsense-2-4-5-with-apu2e4I myself am using 4.11.0.4.
-
@soder Yes always sound to deploy to test systems first and/or wait for others.
In this case this is not a serious bug unless you are modifying the dev.cpu.* sysctl to reduce clock speed from default 1.0/1.4GHz default. Benchmarking shows that CPU performance is unchanged between releases.
The likely 3mdeb APU coreboot change which caused this is https://github.com/pcengines/coreboot/commit/9550e97304ecc1c1b6271d50ea089c82b9a82946
Anyway @fireodo has raised issue with 3mdeb ... have to wait for feedback.
-
From https://github.com/pcengines/coreboot/issues/389
"it looks like I rushed things... FreeBSD 12.x detects CPU on ACPI correctly with v4.11.0.5. If pfSense 2.5.0 based on FreeBSD 12.0 is out it will work I guess.
Sorry about that. Will revert it on next release."
-
@bigsy Thanks for informing us
-
That 4.11.05 bios! Back on 4.11.04 now.
Another issue I have on .05 is that my throughput decreased drastically.
I have a 500/500 line and could easily saturate it on .04:
iperf3 -c x.x.x. -P 4
[ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 158 MBytes 132 Mbits/sec 130 sender [ 5] 0.00-10.00 sec 157 MBytes 131 Mbits/sec receiver [ 7] 0.00-10.00 sec 118 MBytes 98.7 Mbits/sec 152 sender [ 7] 0.00-10.00 sec 116 MBytes 97.5 Mbits/sec receiver [ 9] 0.00-10.00 sec 139 MBytes 117 Mbits/sec 102 sender [ 9] 0.00-10.00 sec 138 MBytes 116 Mbits/sec receiver [ 11] 0.00-10.00 sec 190 MBytes 159 Mbits/sec 158 sender [ 11] 0.00-10.00 sec 188 MBytes 158 Mbits/sec receiver [SUM] 0.00-10.00 sec 604 MBytes 507 Mbits/sec 542 sender [SUM] 0.00-10.00 sec 599 MBytes 503 Mbits/sec receiverOn .05:
[ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 49.8 MBytes 41.8 Mbits/sec 230 sender [ 5] 0.00-10.00 sec 49.3 MBytes 41.4 Mbits/sec receiver [ 7] 0.00-10.00 sec 50.4 MBytes 42.3 Mbits/sec 240 sender [ 7] 0.00-10.00 sec 49.8 MBytes 41.8 Mbits/sec receiver [ 9] 0.00-10.00 sec 42.3 MBytes 35.5 Mbits/sec 222 sender [ 9] 0.00-10.00 sec 42.0 MBytes 35.3 Mbits/sec receiver [ 11] 0.00-10.00 sec 40.0 MBytes 33.6 Mbits/sec 259 sender [ 11] 0.00-10.00 sec 39.7 MBytes 33.3 Mbits/sec receiver [SUM] 0.00-10.00 sec 183 MBytes 153 Mbits/sec 951 sender [SUM] 0.00-10.00 sec 181 MBytes 152 Mbits/sec receiverAPU2C4 pfSense 2.4.5 with this configuration: https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/
-
@stefanl Thanks for informing, maybe also report it at https://github.com/pcengines/coreboot/issues/
-
@fireodo said in PC Engines apu2 experiences:
sysctl dev.cpu.0.freq
I have also noticed that the telegraf CPU temp script reports CPU temp much lower than expected.
https://www.reddit.com/r/PFSENSE/comments/b496kt/get_cpu_temp_using_telegraf/
This line now only reports total CPU temperate, not the temperature of each core.
VAR1=$(sysctl -a | awk '/temperature/ {print $2;}' | sed s/C// | tr '\n' '+' | sed 's/\(.*\)+/\1/') -
@stefanl I've struggling with low througput
Made some tweaks from https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/ and no matter the settings no performance change was gained.
Tested on APU3C4 on pfsense and opnsense.BIOS factory installed was 4.11.0.2. Upgraded to 4.11.0.5
Accepted connection from 192.168.10.188, port 31427 [ 5] local 192.168.10.21 port 5201 connected to 192.168.10.188 port 21880 [ 7] local 192.168.10.21 port 5201 connected to 192.168.10.188 port 60804 [ 9] local 192.168.10.21 port 5201 connected to 192.168.10.188 port 18408 [ 11] local 192.168.10.21 port 5201 connected to 192.168.10.188 port 37996 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 10.9 MBytes 91.1 Mbits/sec [ 7] 0.00-1.00 sec 9.88 MBytes 82.8 Mbits/sec [ 9] 0.00-1.00 sec 12.0 MBytes 101 Mbits/sec [ 11] 0.00-1.00 sec 12.9 MBytes 108 Mbits/sec [SUM] 0.00-1.00 sec 45.6 MBytes 383 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 1.00-2.00 sec 10.8 MBytes 90.8 Mbits/sec [ 7] 1.00-2.00 sec 11.7 MBytes 98.3 Mbits/sec [ 9] 1.00-2.00 sec 11.9 MBytes 100 Mbits/sec [ 11] 1.00-2.00 sec 12.0 MBytes 101 Mbits/sec [SUM] 1.00-2.00 sec 46.5 MBytes 390 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 2.00-3.00 sec 12.4 MBytes 104 Mbits/sec [ 7] 2.00-3.00 sec 11.9 MBytes 100 Mbits/sec [ 9] 2.00-3.00 sec 11.7 MBytes 98.4 Mbits/sec [ 11] 2.00-3.00 sec 10.1 MBytes 84.9 Mbits/sec [SUM] 2.00-3.00 sec 46.2 MBytes 387 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 3.00-4.00 sec 11.5 MBytes 96.5 Mbits/sec [ 7] 3.00-4.00 sec 11.8 MBytes 99.3 Mbits/sec [ 9] 3.00-4.00 sec 10.7 MBytes 89.8 Mbits/sec [ 11] 3.00-4.00 sec 12.0 MBytes 100 Mbits/sec [SUM] 3.00-4.00 sec 46.0 MBytes 386 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 4.00-5.00 sec 7.71 MBytes 64.7 Mbits/sec [ 7] 4.00-5.00 sec 13.2 MBytes 111 Mbits/sec [ 9] 4.00-5.00 sec 9.66 MBytes 81.0 Mbits/sec [ 11] 4.00-5.00 sec 14.8 MBytes 124 Mbits/sec [SUM] 4.00-5.00 sec 45.4 MBytes 380 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 5.00-6.00 sec 11.7 MBytes 98.1 Mbits/sec [ 7] 5.00-6.00 sec 12.1 MBytes 101 Mbits/sec [ 9] 5.00-6.00 sec 11.4 MBytes 95.6 Mbits/sec [ 11] 5.00-6.00 sec 11.2 MBytes 94.0 Mbits/sec [SUM] 5.00-6.00 sec 46.3 MBytes 389 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 6.00-7.00 sec 11.8 MBytes 99.2 Mbits/sec [ 7] 6.00-7.00 sec 11.3 MBytes 94.9 Mbits/sec [ 9] 6.00-7.00 sec 10.5 MBytes 87.9 Mbits/sec [ 11] 6.00-7.00 sec 12.7 MBytes 107 Mbits/sec [SUM] 6.00-7.00 sec 46.3 MBytes 389 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 7.00-8.00 sec 11.2 MBytes 93.6 Mbits/sec [ 7] 7.00-8.00 sec 7.00 MBytes 58.7 Mbits/sec [ 9] 7.00-8.00 sec 13.2 MBytes 111 Mbits/sec [ 11] 7.00-8.00 sec 14.2 MBytes 119 Mbits/sec [SUM] 7.00-8.00 sec 45.5 MBytes 382 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 8.00-9.00 sec 13.3 MBytes 112 Mbits/sec [ 7] 8.00-9.00 sec 7.52 MBytes 63.0 Mbits/sec [ 9] 8.00-9.00 sec 12.1 MBytes 102 Mbits/sec [ 11] 8.00-9.00 sec 13.1 MBytes 110 Mbits/sec [SUM] 8.00-9.00 sec 46.1 MBytes 387 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 9.00-10.00 sec 10.6 MBytes 89.1 Mbits/sec [ 7] 9.00-10.00 sec 11.0 MBytes 92.2 Mbits/sec [ 9] 9.00-10.00 sec 12.9 MBytes 108 Mbits/sec [ 11] 9.00-10.00 sec 12.2 MBytes 102 Mbits/sec [SUM] 9.00-10.00 sec 46.7 MBytes 391 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 10.00-10.01 sec 95.5 KBytes 121 Mbits/sec [ 7] 10.00-10.01 sec 87.0 KBytes 110 Mbits/sec [ 9] 10.00-10.01 sec 89.8 KBytes 113 Mbits/sec [ 11] 10.00-10.01 sec 22.8 KBytes 28.8 Mbits/sec [SUM] 10.00-10.01 sec 295 KBytes 372 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 5] 0.00-10.01 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-10.01 sec 112 MBytes 93.9 Mbits/sec receiver [ 7] 0.00-10.01 sec 0.00 Bytes 0.00 bits/sec sender [ 7] 0.00-10.01 sec 107 MBytes 90.1 Mbits/sec receiver [ 9] 0.00-10.01 sec 0.00 Bytes 0.00 bits/sec sender [ 9] 0.00-10.01 sec 116 MBytes 97.4 Mbits/sec receiver [ 11] 0.00-10.01 sec 0.00 Bytes 0.00 bits/sec sender [ 11] 0.00-10.01 sec 125 MBytes 105 Mbits/sec receiver [SUM] 0.00-10.01 sec 0.00 Bytes 0.00 bits/sec sender [SUM] 0.00-10.01 sec 461 MBytes 386 Mbits/sec receiverAfter flashing BIOS Legacy v4.0.30
Accepted connection from 192.168.10.188, port 62725 [ 5] local 192.168.10.21 port 5201 connected to 192.168.10.188 port 61859 [ 7] local 192.168.10.21 port 5201 connected to 192.168.10.188 port 12000 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 69.4 MBytes 582 Mbits/sec [ 7] 0.00-1.00 sec 39.8 MBytes 333 Mbits/sec [SUM] 0.00-1.00 sec 109 MBytes 915 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 1.00-2.00 sec 67.2 MBytes 564 Mbits/sec [ 7] 1.00-2.00 sec 45.3 MBytes 380 Mbits/sec [SUM] 1.00-2.00 sec 113 MBytes 944 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 2.00-3.00 sec 74.8 MBytes 628 Mbits/sec [ 7] 2.00-3.00 sec 35.4 MBytes 297 Mbits/sec [SUM] 2.00-3.00 sec 110 MBytes 925 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 3.00-4.00 sec 74.8 MBytes 628 Mbits/sec [ 7] 3.00-4.00 sec 35.4 MBytes 297 Mbits/sec [SUM] 3.00-4.00 sec 110 MBytes 925 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 4.00-5.00 sec 75.0 MBytes 629 Mbits/sec [ 7] 4.00-5.00 sec 35.0 MBytes 294 Mbits/sec [SUM] 4.00-5.00 sec 110 MBytes 923 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 5.00-6.00 sec 74.7 MBytes 626 Mbits/sec [ 7] 5.00-6.00 sec 37.8 MBytes 317 Mbits/sec [SUM] 5.00-6.00 sec 112 MBytes 943 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 6.00-7.00 sec 74.3 MBytes 623 Mbits/sec [ 7] 6.00-7.00 sec 38.4 MBytes 322 Mbits/sec [SUM] 6.00-7.00 sec 113 MBytes 945 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 7.00-8.00 sec 68.9 MBytes 578 Mbits/sec [ 7] 7.00-8.00 sec 43.8 MBytes 368 Mbits/sec [SUM] 7.00-8.00 sec 113 MBytes 946 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 8.00-9.00 sec 75.1 MBytes 630 Mbits/sec [ 7] 8.00-9.00 sec 37.6 MBytes 315 Mbits/sec [SUM] 8.00-9.00 sec 113 MBytes 945 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 9.00-10.00 sec 76.8 MBytes 644 Mbits/sec [ 7] 9.00-10.00 sec 35.7 MBytes 300 Mbits/sec [SUM] 9.00-10.00 sec 113 MBytes 944 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 5] 10.00-10.03 sec 1.89 MBytes 616 Mbits/sec [ 7] 10.00-10.03 sec 971 KBytes 309 Mbits/sec [SUM] 10.00-10.03 sec 2.84 MBytes 925 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 5] 0.00-10.03 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-10.03 sec 733 MBytes 613 Mbits/sec receiver [ 7] 0.00-10.03 sec 0.00 Bytes 0.00 bits/sec sender [ 7] 0.00-10.03 sec 385 MBytes 322 Mbits/sec receiver [SUM] 0.00-10.03 sec 0.00 Bytes 0.00 bits/sec sender [SUM] 0.00-10.03 sec 1.09 GBytes 935 Mbits/sec receiverI'm making more tests and will post results here.
-
@cysiacom said in PC Engines apu2 experiences:
@stefanl I've struggling with low througput
Made some tweaks from https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/ and no matter the settings no performance change was gained.
Tested on APU3C4 on pfsense and opnsense.BIOS factory installed was 4.11.0.2. Upgraded to 4.11.0.5
Accepted connection from 192.168.10.188, port 31427 [SUM] 10.00-10.01 sec 295 KBytes 372 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - After flashing BIOS Legacy v4.0.30Accepted connection from 192.168.10.188, port 62725
[ 5] local 192.168.10.21 port 5201 connected to 192.168.10.188 port 61859
[ 7] local 192.168.10.21 port 5201 connected to 192.168.10.188 port 12000
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 69.4 MBytes 582 Mbits/sec
[ 7] 0.00-1.00 sec 39.8 MBytes 333 Mbits/sec
[SUM] 0.00-1.00 sec 109 MBytes 915 Mbits/sec
I'm making more tests and will post results here.The differences are huge! :-( I have read that with 4.11.0.4 the speed should be OK. Maybe you give it a try!
Regards,
fireodo
