23.01 crashing and won't reboot without console connection
-
Ah, unfortunate. Well you could try to trigger it again. That would prove its not something difficult to repeat. I'll try to replicate it here.
Steve
-
What were you renaming it to?
It works as expected for simply renaming the BE. On my test box at least.
-
@stephenw10 I noticed that the name actually stuck after the crash / reboot. renamed to 23_01-working. have since renamed it to 23_01-crashing, and no crash this time.
-
It could have been coincidental. Looking at previous similar panics they are all in pf and nothing to do with ZFS or the filesystem at all.
If you see it again we'd love to review it. -
@stephenw10 woke up to crashed pfsense again, and still won't boot after a crash without console connected. I have a much larger textdump file if I can send it to you again, would appreciate you looking at it. I see openvpn going up and down. its there any chance this could be affecting it...
https://forum.netgate.com/topic/177491/automatically-start-openvpn-server-when-my-phone-is-not-on-home-wifi-project-writeup?_=1677335639800
-
Sure if you can upload the full crashdump here I can review it:
https://nc.netgate.com/nextcloud/s/WEJQTXincHFo884Steve
-
@stephenw10 thanks. ok, uploaded. thanks. maybe I need to contact protectli about bios settings or something preventing it from rebooting unattended after a crash. I suspect it's doing something like windows does after a major crash and is asking whether to boot normally or not, but since it's a major pain when the internet is out, I just plug in the console cable and hit enter on the blank screen, and it boots.
-
Ah the backtrace may be telling here:
db:1:pfs> bt Tracing pid 63462 tid 100268 td 0xfffffe00d2cbb720 kdb_enter() at kdb_enter+0x32/frame 0xfffffe00d2a704e0 vpanic() at vpanic+0x182/frame 0xfffffe00d2a70530 panic() at panic+0x43/frame 0xfffffe00d2a70590 _mtx_lock_indefinite_check() at _mtx_lock_indefinite_check+0x68/frame 0xfffffe00d2a705a0 _mtx_lock_spin_cookie() at _mtx_lock_spin_cookie+0xd5/frame 0xfffffe00d2a70610 uart_cnputc() at uart_cnputc+0xaf/frame 0xfffffe00d2a70640 cnputc() at cnputc+0x4c/frame 0xfffffe00d2a70670 cnputsn() at cnputsn+0x6a/frame 0xfffffe00d2a706b0 putchar() at putchar+0x14a/frame 0xfffffe00d2a70740 kvprintf() at kvprintf+0xf5/frame 0xfffffe00d2a70860 _vprintf() at _vprintf+0x8c/frame 0xfffffe00d2a70950 printf() at printf+0x53/frame 0xfffffe00d2a709b0 trap_fatal() at trap_fatal+0x280/frame 0xfffffe00d2a70a10 trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00d2a70a70 calltrap() at calltrap+0x8/frame 0xfffffe00d2a70a70 --- trap 0xc, rip = 0xffffffff80f9352c, rsp = 0xfffffe00d2a70b40, rbp = 0xfffffe00d2a70b70 --- X_ip_mrouter_done() at X_ip_mrouter_done+0x31c/frame 0xfffffe00d2a70b70 rip_detach() at rip_detach+0x3f/frame 0xfffffe00d2a70ba0 sorele_locked() at sorele_locked+0x89/frame 0xfffffe00d2a70bc0 soclose() at soclose+0xeb/frame 0xfffffe00d2a70c20 _fdrop() at _fdrop+0x11/frame 0xfffffe00d2a70c40 closef() at closef+0x24b/frame 0xfffffe00d2a70cd0 fdescfree() at fdescfree+0x4b3/frame 0xfffffe00d2a70d90 --Exceeded input buffer-- exit1() at exit1+0x4c7/frame 0xfffffe00d2a70df0 sys_exit() at sys_exit+0xd/frame 0xfffffe00d2a70e00 amd64_syscall() at amd64_syscall+0x10c/frame 0xfffffe00d2a70f30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00d2a70f30 --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x8233c886a, rsp = 0x820ca3bd8, rbp = 0x820ca3bf0 ---And the panic:
Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80f9352c stack pointer = 0x28:0xfffffe00d2a70b40 frame pointer = 0x28:0xfffffe00d2a70b70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 ns8250: UART FCR is broken spin lock 0xfffff80001a9ec40 (uart_hwmtx) held by 0xfffffe0010cf6e40 (tid 100006) too long panic: spin lock held too long cpuid = 0 time = 1677315261 KDB: enter: panicAnd this could certainly be why it doesn't reboot. It looks like something is continually sending data to the UART console perhaps. That would interrupt the boot. What consoles do you have connected there and what are they connected to?
-
@stephenw10 this router is in my basement, so I have a console cable plugged in with an ethernet extension on the other end and nothing plugged in to the upstairs side, unless it goes down. don't know if that sounds clear but basically an ethernet cable plugged into the console port but open on the other side, like an extension cord. then, after a crash, I plug into that cable with a usb console cable and plug into my mac and open my terminal emulator program. do I need to go to the router and unplug the extension cable from the router side? do you think having a console cable plugged in to the protectli and open on the other end could cause this?
btw, the script that I referenced above has a php echo command in it, but that works without errors, so I don't think it shouldn't cause issues. I do have that script set up to run on a cron job every 5 minutes, but pfsense sends lots of info to the terminal in normal operation, so that php echo shouldn't hurt anything, right? did you see in the dump file that openvpn was going up down up down? that concerns me too since my custom script does exactly that.
-
Yes, I could imagine an unterminated very long console cable could generate enough random noise to send some characters.
Does it reboot normally from the gui with the console in that state? That would no different after a panic.
It may also be that something is generating the interference triggering the panic and then interrupting the reboot and doesn't apply at other times. -
@stephenw10 if you are asking if I can reboot from the gui with that cable plugged in, the answer is yes I can. but for now, I will unplug it on the router side too, just in case. then plug in both sides next time. I also need to just drag a monitor and keyboard down to the basement next time, so I can see what the message on the screen says and hopefully figure out why it hangs after a crash. I saw this post this morning that fed my suspicion that there's a message on the screen after a crash, that just needs to be acknowledged for booting to continue...
-
If it was booting fine in 22.05 you won't be hitting the specific issue described there. However by entering any character at the loader menu there you might end up at the loader prompt requiring pressing enter to continue. You might also hit something earlier in the BIOS.
