[Crash Report] - Crash after update from 2.6.0 to 2.7.0
-
Hello everyone - I am not sure where to post crash reports, as there is no specific forum for bugs in general, but I experienced a crash today after updating from 2.6.0 to 2.7.0.
Earlier today I also upgraded the BIOS on my router from Coreboot v4.12.0.5. to v4.17.0.3, I did that in the morning, the only noticeable issue after that was that it couldn't figure out how to route to WAN anymore, which I fixed by setting a default gateway, which had never been set, I wondered how it had worked up until then but oh well, I had also thought about that years ago when I set it up that it seemed weird that it didn't need that, but I guess I did add Wireguard a few months ago, but that gateway was disabled as I was done testing what I had to do.
Anyway, when I came home after work I also wanted to update from 2.6.0 to 2.7.0, that completed successfully and there seems to be no routing or connectivity issues.
But after that I saw that there were two new branches available 2.7.1 and 2.7.2, but it gets stuck retrieving the updates and sometimes it says "Unable to check for updates" on the dashboard.
I am going to try and see if I can resolve that last issue on my own, and while I was checking stuff it just crashed, I wasn't even doing anything in particular other than having a few browser tabs open on the System Update page where it could never finish "Retrieving".
It's my first crash and crash report so I hope I've done everything properly. I didn't see any personal information in the text or dumped archive.
Edit: I just noticed that I am not supposed to post this here, but in the general questions forum, so if you are a staff member reading this feel free to move it, as I am getting some lack of privilegies error when trying to delete this.
Edit 2:
After the crash I tried to see if I could get it to update to 2.7.2, and this time it worked, but there was still the crash, I don't know if that is fixed in the new version I've upgraded to, but I'll let you know if it happens again.
-
Backtrace:
db:0:kdb.enter.default> bt Tracing pid 2 tid 100041 td 0xfffffe0008d3c740 kdb_enter() at kdb_enter+0x32/frame 0xfffffe0062a399f0 vpanic() at vpanic+0x183/frame 0xfffffe0062a39a40 panic() at panic+0x43/frame 0xfffffe0062a39aa0 trap_fatal() at trap_fatal+0x409/frame 0xfffffe0062a39b00 trap_pfault() at trap_pfault+0x4f/frame 0xfffffe0062a39b60 calltrap() at calltrap+0x8/frame 0xfffffe0062a39b60 --- trap 0xc, rip = 0xffffffff80f45173, rsp = 0xfffffe0062a39c30, rbp = 0xfffffe0062a39c80 --- in6_unlink_ifa() at in6_unlink_ifa+0x63/frame 0xfffffe0062a39c80 in6_purgeaddr() at in6_purgeaddr+0x368/frame 0xfffffe0062a39da0 nd6_timer() at nd6_timer+0xdf/frame 0xfffffe0062a39e10 softclock_call_cc() at softclock_call_cc+0x13c/frame 0xfffffe0062a39ec0 softclock_thread() at softclock_thread+0xe9/frame 0xfffffe0062a39ef0 fork_exit() at fork_exit+0x7d/frame 0xfffffe0062a39f30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0062a39f30 --- trap 0, rip = 0, rsp = 0, rbp = 0 ---Looks like this: https://redmine.pfsense.org/issues/14164
Which is fixed in 2.7.2.
-
S stephenw10 moved this topic from Problems Installing or Upgrading pfSense Software on
-
@stephenw10 said in [Crash Report] - Crash after update from 2.6.0 to 2.7.0:
Which is fixed in 2.7.2.
Cool - thank you. As I just wrote in my edit I managed to upgrade it to 2.7.2, so it probably won't happen again.