Kernel Panic in 2.7.0
-
@hecsa hi
I ping yahoo.com usingping -c 5 yahoo.com, the output isPING6(56=40+8+8 bytes) 2***************4 --> 2001:4998:24:120d::1:1 16 bytes from 2001:4998:24:120d::1:1, icmp_seq=0 hlim=46 time=263.204 ms 16 bytes from 2001:4998:24:120d::1:1, icmp_seq=1 hlim=47 time=263.954 ms 16 bytes from 2001:4998:24:120d::1:1, icmp_seq=2 hlim=47 time=261.079 ms 16 bytes from 2001:4998:24:120d::1:1, icmp_seq=3 hlim=46 time=259.364 ms 16 bytes from 2001:4998:24:120d::1:1, icmp_seq=4 hlim=47 time=257.564 ms --- yahoo.com ping6 statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 257.564/261.033/263.954/2.369 msit seems not the network problem~~
-
@pfsss
Hi,
Take a look at this thread, looks something like what you are experiencing: https://forum.netgate.com/topic/121783/solved-update-2-3-4-to-2-4-failed-unable-to-check-for-updates/3
Thanks, and best regards,
HeCSa. -
@hecsa I tried to
ls -al /var/pkg/cachethere is no such directory.. -
Try:
pkg-static -d updateThat should give a more useful error.
-
You probably need to run:
certctl rehash -
@stephenw10 hi
after running commandcertctl rehashandpng-static -d updateI get the following hintsNewer FreeBSD version for package xxd: To ignore this error set IGNORE_OSVERSION=yes - package: 1400094 - running kernel: 1400085 Ignore the mismatch and continue? [y/N]: pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:14:amd64 Processing entries... done Unable to update repository pfSense Error updating repositories!I think it is close to the right way
-
Yes, it must be seeing the pkgs to be able to throw that error so try to upgrade again.
-
@stephenw10
ok, I'm upgrading the system now. I wonder whether upgrading the system affects the packages I've installed. I have a Wireguard package installed in the 2.7.0 version os, after upgrading, it should be ok or I will reconfigured it? thanks~ -
Should be fine. The packages will be upgraded and the config retained.
-
@stephenw10
as your previous replys, how to do memtest, is there a simple instruction to run memtest? thanks -
@stephenw10 thanks to your guide, I've upgrade my os to 2.7.2 successfully! I'll watch whether the crash occurs again.
-
@stephenw10 sadly, the gateway crashes again few hours after upgrade. the crash information is
Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 04 fault virtual address = 0xfffffe00483bdc90 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff81159b45 stack pointer = 0x28:0xfffffe00862abc08 frame pointer = 0x28:0xfffffe00862abc10 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 current process = 54985 (netstat) rdi: ffffffff830dbf00 rsi: fffffe00083bdc20 rdx: 0000000000000001 rcx: 0000000005010018 r8: ffffffff830dbf28 r9: 0000000005ff0008 rax: fffffe0001611c50 rbx: fffffe00483bdc90 rbp: fffffe00862abc10 r10: fffffe00483bdc90 r11: fffffe00483bdc88 r12: ffffffff830dbf00 r13: fffffe00098fd400 r14: 0000000000000001 r15: 0000000000000006 trap number = 12 panic: page fault cpuid = 2 time = 1704523671 KDB: enter: panicbt is
db:0:kdb.enter.default> bt Tracing pid 54985 tid 100246 td 0xfffffe006cc34020 kdb_enter() at kdb_enter+0x32/frame 0xfffffe00862ab8e0 vpanic() at vpanic+0x163/frame 0xfffffe00862aba10 panic() at panic+0x43/frame 0xfffffe00862aba70 trap_fatal() at trap_fatal+0x40c/frame 0xfffffe00862abad0 trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00862abb30 calltrap() at calltrap+0x8/frame 0xfffffe00862abb30 --- trap 0xc, rip = 0xffffffff81159b45, rsp = 0xfffffe00862abc08, rbp = 0xfffffe00862abc10 --- vm_pqbatch_process_page() at vm_pqbatch_process_page+0xb5/frame 0xfffffe00862abc10 vm_page_pqbatch_submit() at vm_page_pqbatch_submit+0x200/frame 0xfffffe00862abc60 vm_page_free_prep() at vm_page_free_prep+0x9c/frame 0xfffffe00862abc80 vm_page_free_toq() at vm_page_free_toq+0x12/frame 0xfffffe00862abcb0 vm_object_terminate() at vm_object_terminate+0x11a/frame 0xfffffe00862abcd0 vm_object_deallocate() at vm_object_deallocate+0x1af/frame 0xfffffe00862abd10 vm_map_process_deferred() at vm_map_process_deferred+0x92/frame 0xfffffe00862abd30 vm_map_remove() at vm_map_remove+0xff/frame 0xfffffe00862abd60 vmspace_exit() at vmspace_exit+0xab/frame 0xfffffe00862abd90 exit1() at exit1+0x53a/frame 0xfffffe00862abdf0 sys_exit() at sys_exit+0xd/frame 0xfffffe00862abe00 amd64_syscall() at amd64_syscall+0x109/frame 0xfffffe00862abf30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00862abf30 --- syscall (1, FreeBSD ELF64, exit), rip = 0x33c88f91140a, rsp = 0x33c88b1d4378, rbp = 0x33c88b1d4390 --- db:0:kdb.enter.default> ps -
Hmm, same crash too. I would definitely run some passes through memtest to check the RAM.
-
@stephenw10 I've run a memtest to the memory, report this
it is actually bad RAM!
thanks for your guides! -
@stephenw10
excellent. Solved my issue with missing packages.
Up to this point I was getting:DBG(1)[97341]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[97341]> PkgRepo: verifying update for pfSense-core DBG(1)[97341]> PkgRepo: need forced update of pfSense-core DBG(1)[97341]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite' DBG(1)[97341]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf DBG(1)[97341]> curl_open DBG(1)[97341]> Fetch: fetcher used: pkg+https DBG(1)[97341]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf DBG(1)[97341]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults * Trying 208.123.73.207:443... * Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL certificate problem: self-signed certificate in certificate chain * Closing connection DBG(1)[97341]> CURL> attempting to fetch from , left retry 2After the rehash, this was fixed and the packages re-appeared in the GUI.
Many thanks.
