Important parts of that are: The backtrace: db:0:kdb.enter.default> bt Tracing pid 41110 tid 100731 td 0xfffff8039f557740 kdb_enter() at kdb_enter+0x37/frame 0xfffffe00a7eb7eb0 vpanic() at vpanic+0x197/frame 0xfffffe00a7eb7f00 panic() at panic+0x43/frame 0xfffffe00a7eb7f60 propagate_priority() at propagate_priority+0x282/frame 0xfffffe00a7eb7f90 turnstile_wait() at turnstile_wait+0x30c/frame 0xfffffe00a7eb7fe0 __mtx_lock_sleep() at __mtx_lock_sleep+0x199/frame 0xfffffe00a7eb8070 qlnx_ioctl() at qlnx_ioctl+0x528/frame 0xfffffe00a7eb80d0 ifhwioctl() at ifhwioctl+0x596/frame 0xfffffe00a7eb8150 ifioctl() at ifioctl+0x4bc/frame 0xfffffe00a7eb8210 kern_ioctl() at kern_ioctl+0x2b7/frame 0xfffffe00a7eb8270 sys_ioctl() at sys_ioctl+0x101/frame 0xfffffe00a7eb8340 amd64_syscall() at amd64_syscall+0x387/frame 0xfffffe00a7eb8470 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00a7eb8470 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x800b54d4a, rsp = 0x7fffffffd198, rbp = 0x7fffffffd210 --- The panic strings: Sleeping thread (tid 100919, pid 62482) owns a non-sleepable lock KDB: stack backtrace of thread 100919: sched_switch() at sched_switch+0x630/frame 0xfffffe00c741ddf0 mi_switch() at mi_switch+0xd4/frame 0xfffffe00c741de20 sleepq_timedwait() at sleepq_timedwait+0x2f/frame 0xfffffe00c741de60 _sleep() at _sleep+0x1c8/frame 0xfffffe00c741dee0 pause_sbt() at pause_sbt+0xf1/frame 0xfffffe00c741df10 qlnx_stop() at qlnx_stop+0x4b5/frame 0xfffffe00c741dfa0 qlnx_init_locked() at qlnx_init_locked+0x2a/frame 0xfffffe00c741e070 qlnx_ioctl() at qlnx_ioctl+0x53a/frame 0xfffffe00c741e0d0 ifhwioctl() at ifhwioctl+0x596/frame 0xfffffe00c741e150 ifioctl() at ifioctl+0x4bc/frame 0xfffffe00c741e210 kern_ioctl() at kern_ioctl+0x2b7/frame 0xfffffe00c741e270 sys_ioctl() at sys_ioctl+0x101/frame 0xfffffe00c741e340 amd64_syscall() at amd64_syscall+0x387/frame 0xfffffe00c741e470 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00c741e470 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x800b54d4a, rsp = 0x7fffffffd198, rbp = 0x7fffffffd210 --- panic: sleeping thread cpuid = 3 time = 1663318115 KDB: enter: panic There is a bug report open for this: https://redmine.pfsense.org/issues/13028 And it looks like you've opened a bug upstream: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266480 Steve

@keyser A bit late but answered for the records too. APU6B4 might be the best choice together with the SG-6100.

Ok now after reboot the message with the Intel licenses are not any more to see at the boot prompt. Thank you all.

Well.... that could be fun!

The public 2.7 snapshots were built on FreeBSD 12 but will be rebased soon. We are testing internally to find and fix all the show stopping issues before making them public again. Steve

This works for me! Thank you. APU2C4 is running v4.17.0.3 Coreboot with the bios watchdog timer set to 300, amdsbwd loaded, and watchdogd -t 128. Kill -9 watchdogd process does indeed cause the system to reboot once the timer expires. Otherwise, the system stays up.

@sledge said in Thunderbolt PCie enclosere and Intel NIC: Also, looking at your signature (assume it's somewhat current today in 2022) I see you switched to a Lenovo M93p. Did the Mac Mini slow down, or did you run into another issue. I got a great deal on the Lenovo and since I could up the RAM to 32GB. I decided to re-purpose the Mac Mini to an Adobe suite server. The thing about the Mac Mini it’s awesome but since Apple OS runs the fan, FreeBSD may not have the driver and one has to wait around making a request for FreeBSD to include and that can be nightmare. Alternatively, one can compile the driver but that was over my head and would have loved the challenge but time didn't permit.

@sledge said in Tehuti 10 Gbe NIC (TN9710P) Supported?: Temporarily I could install pfSense on the Mac Mini and use the Apple ethernet adapter to confirm if it can obtain a DHCP lease or not. You can just install with only the on-board NIC. As a test you only need one NIC to be WAN and try to pull a lease. It will do that in the default setup after installing. No idea on the SM NICs unfortunately. Not something I've ever looked into. The one I have here (AOC-SGP-i4) doesn't appear to have any sort of date on it directly. Steve

Looks like it's a rebadged Supermicro. So probably. Steve

@stephenw10 Thank you very much for that information.

I would expect any of those to work. We fitted the T520-SO-CR ourselves so I know that works. They do run hot though so be sure your cooling is sufficient. I would choose an Intel NIC if you have a choice. Steve

I just got my pfSense running with the following hardware.... HP Prodesk 6200 i3-2100 with 8 gb RAM (came with an HDD I didn't use): $50 second hand from a private seller. (Just the box, no peripherals) Two, TP-Link TG-3468 NICs (one for LAN and one for OPT); ~$12/ea from Amazon. One, Silicone Power 128 gb SSD: ~$17 from Amazon. I used a keyboard and monitor I had to get it set up, but now it's freestanding. I don't know how many VLANs you're talking about, but I run a LAN for security and the OPT interface is for multiple Static IPs from Google Fiber. I have it attached to a Netgear Gigabit 8-port switch I got off Amazon for ~$19 The built-in NIC on the HP Prodesk provides the WAN. I get full speed 1 GBs through the Fiber Jack. So, outside of my time I spent a total of about ~$125 and it seems to work just fine.

@cgi2099 said in HP T730 help please: @stephenw10 Ended up getting it fixed by flashing my old firmware and then upgrading. Was rather painless after that, installed my packages and did a config restore. I guess this x710 goes in the tech cabinet until there is a fix. Got an i350-4 ready to install tomorrow. For Fiber connection you could try out the Allied Telesis AT-29M2/SC M.2 module, it is nice cheap for something around ~$30 in the usa. So you will be having fiber and copper based NICs. If they are supported by FreeBSD (pfSense) you will be able to set up one more network connection.

Or in this case just that the kernel module is not compatible with the kernel. You could just use the appropriate module for the version you have but you should really upgrade to 2.6 for the reasons mentioned. Steve

@sledge said in early 2011 macbook pro i7 model. screen won't turn off and function keys don't work!: Any reason the 2012 is your sweet spot? It was only if you didn't already have the 2014 decked out with 16GB RAM, since those RAM is soldered...in your case, hallelujah. Yes, both device and thunderbolt to Ethernet adapter used Broadcom which is not compatible with Netmap. The thunderbolt two enclosure worked like a charm with Intel NIC, and I had no problem running Suricata on WAN and Snort on LAN both in-line mode despite that not recommended by the package maintainer. I just love the idea, and it works great as long as one is not using the same rules feed with both. I was lucky to find the thunderbolt PCI enclosure on eBay for close to $100 used (Akitio) and if you're unable to find one, I maybe able to help you out. I believe the current version of FreeBSD should have the fan driver but could be added and recompiled although I had not done it.

@stephenw10 Thanks for te tip, i do have a 10G switch, what i dont have is a monochannel fiber device to test, i will have to experiment staright with the fiber that the ISP provides ;)

@sledge All good advice. Here's my plan. I already upgraded the modem. I also found a problem with the cable coming in and fixed it - the copper wire had clipped off and was barely making a connection. My speeds are better and I now have a spare modem - I like having spare things, not hoarding. I'm thinking of a 6 port pc with 2.5Gbit ports. 1 port will be a VLAN. The other 3 will be for the full pipe, whatever it is - likely 900 mbits for a long time. Someday I suspect 2 Gbits will be fairly common. I started out with 50 and ended up with 900 so far, and most upgrades were free and just given to me. My Shuttle DS68U will be a spare router. Sometime this year. I'm retired and need a hobby. This one includes bragging rights.

Check the output of: kenv Make sure the BIOS is current. The broken DMI table is being passed by the BIOS so ask Dell. It's probably not hurting anything though. Steve