1
22.7 Legacy Series / Re: 3rd party tool turbostat crashes with "Floating exception (core dumped)"
« on: September 02, 2022, 02:00:33 pm »
Perfect, thanks for the hint!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
22.7 Legacy Series / Re: 3rd party tool turbostat crashes with "Floating exception (core dumped)"
« on: September 02, 2022, 01:41:54 pm »
Thanks a lot! 
So I'll reinstall the tool in a few days and see if it is working again. Or maybe I'll find another way to determine the current CPU clock.
So I'll reinstall the tool in a few days and see if it is working again. Or maybe I'll find another way to determine the current CPU clock.
3
22.7 Legacy Series / 3rd party tool turbostat crashes with "Floating exception (core dumped)"
« on: September 01, 2022, 07:53:32 pm »
For testing the current CPU clock, I have been running turbostat for many years. This has worked over many versions of FreeBSD. Since version 13 the tool stops after startup with "Floating exception (core dumped)".
Here's what I do to install and run turbostat (worked so well before FreeBSD):
Since FreeBSD 13 I now have the following output:
My questions:
Thanks for any hints.
Here's what I do to install and run turbostat (worked so well before FreeBSD):
Code: [Select]
pkg add https://pkg.freebsd.org/FreeBSD:13:amd64/latest/All/turbostat-4.17_2.pkg
rehash
kldload cpuctl
turbostat --interval 3
Since FreeBSD 13 I now have the following output:
Code: [Select]
# turbostat --interval 3
turbostat version 17.06.23 - Len Brown <lenb@kernel.org>
CPUID(0): AuthenticAMD 13 CPUID levels; family:model:stepping 0xf:30:1 (15:48:1)
CPUID(1): SSE3 MONITOR - - - TSC MSR - -
CPUID(6): APERF, No-TURBO, No-DTS, No-PTM, No-HWP, No-HWPnotify, No-HWPwindow, No-HWPepp, No-HWPpkg, No-EPB
CPUID(7): No-SGX
NSFOD /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
Floating exception (core dumped)
My questions:
- Is there any reason that turbostat should no longer run with FreeBSD 13? (When installing I get a message that the package is no longer maintained.)
- Are there alternative similar tools that show the current CPU clock?
Thanks for any hints.
4
Hardware and Performance / Re: [SOLVED] APU - Is your CPU clock stuck at low frequency after some time?
« on: February 16, 2022, 01:52:19 pm »
Originally it effectively looked like the problem was solved for quite some time.
To be sure, I just logged into the firewall again and looked.
Unfortunately, I find that despite new firmware, the problem is still there.
The BIOS developers have been informed. In the meantime better turn off Powerd or set it to maximum.
To be sure, I just logged into the firewall again and looked.
Unfortunately, I find that despite new firmware, the problem is still there.
The BIOS developers have been informed. In the meantime better turn off Powerd or set it to maximum.
5
20.7 Legacy Series / Re: Regular packet loss / latency spikes of ~30 seconds
« on: December 14, 2021, 04:24:48 pm »
Thanks for the update! 
If you wish, you could add [SOLVED] to the title then.
If you wish, you could add [SOLVED] to the title then.
6
Hardware and Performance / Re: APU - Is your CPU clock stuck at low frequency after some time?
« on: November 23, 2021, 09:28:35 am »
Update:
Since BIOS version v4.14.0.1 (June 2021) the problem seems to be fixed:
I can confirm that with the current version v4.14.0.6 I don't see the problem anymore. I.e. with the current BIOS you can turn on the powerd under OPNsense on an APU2 and leave it on highadaptive. The CPU adapts well to the load and always goes back to maximum frequency if necessary.
If you don't need gigabit internet, the APU2 is still an extremely proven and stable base for OPNsense. I have two of them.
Since BIOS version v4.14.0.1 (June 2021) the problem seems to be fixed:
Quote
with the recent v4.14.0.1 we have fixed some issues related to CPU boost and C-states which may help with the problem of idling CPUs and stuck frequencies. It should also improve the stability of the BSD systems.
coreboot didn't include the core C6 (CC6) save state memory in the memory map. OS could accidentally access this memory and overwrite core states. CC6 is required for CPU boost to work and is a lower power state for a core.
I can confirm that with the current version v4.14.0.6 I don't see the problem anymore. I.e. with the current BIOS you can turn on the powerd under OPNsense on an APU2 and leave it on highadaptive. The CPU adapts well to the load and always goes back to maximum frequency if necessary.
If you don't need gigabit internet, the APU2 is still an extremely proven and stable base for OPNsense. I have two of them.
7
Hardware and Performance / Re: PC Engines APU2 1Gbit traffic not achievable
« on: April 15, 2021, 05:42:35 pm »
I have opened the ticket with the maintainers of Coreboot for the PC Engines boards. So far, however, there has been nothing further.
I was able to solve the problem by keeping PowerD enabled but setting the mode to maximum. Since then I didn't have the problem anymore.
And if the CPU was limited to 600MHz it cost a lot of performance. In my setup I just got away with it - but had zero headroom. When the CPU is running normally the utilization is rarely more than 50%.
I was able to solve the problem by keeping PowerD enabled but setting the mode to maximum. Since then I didn't have the problem anymore.
And if the CPU was limited to 600MHz it cost a lot of performance. In my setup I just got away with it - but had zero headroom. When the CPU is running normally the utilization is rarely more than 50%.
8
Hardware and Performance / Re: PC Engines APU2 1Gbit traffic not achievable
« on: April 13, 2021, 11:45:49 am »
Something you can check: configure powerd to use "Maximum" instead of "Hiadaptive".
As discussed here: https://forum.opnsense.org/index.php?topic=21194.msg99228#msg99228
As discussed here: https://forum.opnsense.org/index.php?topic=21194.msg99228#msg99228
9
Hardware and Performance / Re: PC Engines APU2 1Gbit traffic not achievable
« on: April 13, 2021, 11:44:01 am »
Just to be sure:
- You test with iperf THROUGH the firewall. I.e. iperf is not running on the firewall but on separate hosts "on both sides" of the firewall?
- You have only set pf rules but no other services like IDS, IDP, Sensei etc.
- You test with iperf THROUGH the firewall. I.e. iperf is not running on the firewall but on separate hosts "on both sides" of the firewall?
- You have only set pf rules but no other services like IDS, IDP, Sensei etc.
10
21.1 Legacy Series / Re: DNS issues on fresh install
« on: March 22, 2021, 05:06:58 pm »
Thank you for the final good news. All's well that ends well.
This shows again that it becomes difficult to find problems when too many parts are changeable at the same time. Then you don't really know where problems come from.
Have fun and success with OPNsense! If the problem is solved, I'm happy about some karma and you can prefix the title with [SOLVED].
This shows again that it becomes difficult to find problems when too many parts are changeable at the same time. Then you don't really know where problems come from.
Have fun and success with OPNsense! If the problem is solved, I'm happy about some karma and you can prefix the title with [SOLVED].
11
21.1 Legacy Series / Re: DNS issues on fresh install
« on: March 21, 2021, 05:39:04 pm »
Well. I am a bit lost here. 
I have similar setups running, even with some APU2 (and virtual instances on Proxmox). What I have and is working perfectly:
myNetwork---------LAN|OPNsense(NAT)|WAN-----------LAN|Router(NAT)|WAN----------Provider
10.1.1.0/24 10.1.1.1 192.168.1.100 192.168.1.1 some IP
The Gateway of OPNsense is (automatically via DHCP) set to 192.168.1.1.
On OPNsense I have (manually) configured two DNS servers (e.g. OpenDNS or Google).
DHCP server on LAN of OPNsense sets Clients in myNetwork to use the Unbound DNS server running on OPNsense (10.1.1.1 as DNS server on clients). Undbound forwards to the normal DNS resolvers configured for OPNsense.
Supposed your router would do some kind of DNS blocking, one could try to set 192.168.1.1 as DNS forwarder on OPNsense. Could be done manually or should also be set automatically using DHCP from your router.
I would say, that this is a kind of standard setup that always worked for me.
I have similar setups running, even with some APU2 (and virtual instances on Proxmox). What I have and is working perfectly:
myNetwork---------LAN|OPNsense(NAT)|WAN-----------LAN|Router(NAT)|WAN----------Provider
10.1.1.0/24 10.1.1.1 192.168.1.100 192.168.1.1 some IP
The Gateway of OPNsense is (automatically via DHCP) set to 192.168.1.1.
On OPNsense I have (manually) configured two DNS servers (e.g. OpenDNS or Google).
DHCP server on LAN of OPNsense sets Clients in myNetwork to use the Unbound DNS server running on OPNsense (10.1.1.1 as DNS server on clients). Undbound forwards to the normal DNS resolvers configured for OPNsense.
Supposed your router would do some kind of DNS blocking, one could try to set 192.168.1.1 as DNS forwarder on OPNsense. Could be done manually or should also be set automatically using DHCP from your router.
I would say, that this is a kind of standard setup that always worked for me.
12
21.1 Legacy Series / Re: DNS issues on fresh install
« on: March 21, 2021, 03:47:02 pm »
Ok. Getting better... ;-)
I think it will not work like this: You can not have the same IP range on both NICs (WAN, LAN) without special subnet calculations.
I would select another range for the LAN side. E.g. 192.168.2.x or the 10.x.x.x you had before.
I think it will not work like this: You can not have the same IP range on both NICs (WAN, LAN) without special subnet calculations.
I would select another range for the LAN side. E.g. 192.168.2.x or the 10.x.x.x you had before.
13
21.1 Legacy Series / Re: DNS issues on fresh install
« on: March 21, 2021, 12:16:49 pm »
What IP address is assigned to the WAN NIC of OPNsense? And how?
With your setup you will probably need to do double NAT. There are routers rejecting routing to other internal IP addresses than the ones in their own LAN segment. (Which ist the WAN segment on your OPNsense but not the LAN segment of OPNsense).
What would I do?
Make sure its working with a notebook attached to your router.
Reset the configuration of OPNsense.
Just let the OPNsense Wizard do its work.
This SHOULD result in a working configuration.
With your setup you will probably need to do double NAT. There are routers rejecting routing to other internal IP addresses than the ones in their own LAN segment. (Which ist the WAN segment on your OPNsense but not the LAN segment of OPNsense).
What would I do?
Make sure its working with a notebook attached to your router.
Reset the configuration of OPNsense.
Just let the OPNsense Wizard do its work.
This SHOULD result in a working configuration.
14
21.1 Legacy Series / Re: DNS issues on fresh install
« on: March 21, 2021, 05:35:20 am »
Are you sure you are having a DNS problem? I mean is IP routing to the Internet working?
As your router seems to have a WAN IP 192.x.x.x this could be an internal only IP 192.168.x.x that is not routed to the Internet/WAN by default. In this case you should disable this security setting in menu Interfaces : WAN in section Generic/Block private networks.
As your router seems to have a WAN IP 192.x.x.x this could be an internal only IP 192.168.x.x that is not routed to the Internet/WAN by default. In this case you should disable this security setting in menu Interfaces : WAN in section Generic/Block private networks.
15
General Discussion / Re: 1 line into house, separate handling for owner and tenant
« on: March 13, 2021, 10:30:51 am »
I would also set up two separate network segments for this task, each with its own IP range. Then they are cleanly separated and you can set up separate firewall rules or control QoS per network.
Basically, each segment needs its own interface on the OPNsense. This can be an own physical interface (tenant port) or a VLAN interface on the normal LAN port.
If the tenant only gets cable internet, it is probably easier to provide a physical interface for him and to pull the cable to him. He can then connect a switch or his own access point. However, if he is to be supplied via the same WiFi access point as the main network but with his own SSID, then I would (if necessary additionally) connect his network with a VLAN ID to the main WiFi access point as well. Many professional or semi-professional access points (e.g. Unifi, etc.) then allow a VLAN to be assigned its own SSID.
Basically, each segment needs its own interface on the OPNsense. This can be an own physical interface (tenant port) or a VLAN interface on the normal LAN port.
If the tenant only gets cable internet, it is probably easier to provide a physical interface for him and to pull the cable to him. He can then connect a switch or his own access point. However, if he is to be supplied via the same WiFi access point as the main network but with his own SSID, then I would (if necessary additionally) connect his network with a VLAN ID to the main WiFi access point as well. Many professional or semi-professional access points (e.g. Unifi, etc.) then allow a VLAN to be assigned its own SSID.