pfSense

Do you see a kernel panic? Any sort of error log?

See: https://redmine.pfsense.org/issues/16101

it appears to be a bug with the dashboard. Once the login screen times out and I get that crash dump that I pasted in the ticket, I can navigate around the menus OK, but when I try to get to the dashboard is timeout. Are there logs I can look at for the dashboard?

I did find this in the system logs:

2025/06/09 18:21:50 [error] 98156#100316: *1 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.200.104, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.200.102", referrer: "http://192.168.200.102/"

On the kernel panic topic, when I have pfSense 2.7 or pfSense+ 24.11-RELEASE, is where I get the kernel panic.

Another related issue, I cant get the any of the QL41164 ports to do DHCP. When the system boots up it wont have a DHCP address, if i wait a bit and press return on the console it will eventually show an IP, however I cant ping it, ssh, web anything to it. Only way the NIC is accessible is if I put a static IP on it.

Adam Esslinger wrote in #note-2:

it appears to be a bug with the dashboard. Once the login screen times out and I get that crash dump that I pasted in the ticket, I can navigate around the menus OK, but when I try to get to the dashboard is timeout. Are there logs I can look at for the dashboard?

I did find this in the system logs:

2025/06/09 18:21:50 [error] 98156#100316: *1 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.200.104, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.200.102", referrer: "http://192.168.200.102/"

On the kernel panic topic, when I have pfSense 2.7 or pfSense+ 24.11-RELEASE, is where I get the kernel panic.

Another related issue, I cant get the any of the QL41164 ports to do DHCP. When the system boots up it wont have a DHCP address, if i wait a bit and press return on the console it will eventually show an IP, however I cant ping it, ssh, web anything to it. Only way the NIC is accessible is if I put a static IP on it.

I actually believe this is a bug in FreeBSD. I have a ticket opened with them and been working on it.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287445

We may have hit this while working on the other qlnxe bug.

If you run:

ifconfig -v ql0

It fails to return when trying, what appears to be, to read the SFP module data.

The dashboard interfaces widget uses that command and since it's present by default it appears to hang the dashboard.

After attempting that several times I also see logged:

ql1: [ecore_dbg_print_attn:6458(qlnx-0)]interrupt: address 0x00001d00, status 0x00000001, mask 0x00000000
ql1: [ecore_int_deassertion_aeu_bit:938(qlnx-0)]`Vaux PCI core': Fatal attention
ql3: [ecore_dbg_print_attn:6458(qlnx-0)]interrupt: address 0x00001d00, status 0x00000001, mask 0x00000000
ql3: [ecore_int_deassertion_aeu_bit:938(qlnx-0)]`Vaux PCI core': Fatal attention
ql3: [ecore_dbg_print_attn:6458(qlnx-0)]interrupt: address 0x00001d00, status 0x00000001, mask 0x00000000