Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    pf_test: kif == NULL, if_xname on multi-WAN and "Reset all states if WAN IP Address changes"

    Scheduled Pinned Locked Moved 2.5 Development Snapshots (Retired)
    34 Posts 5 Posters 2.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ?
      A Former User @w0w
      last edited by A Former User

      @w0w The patches mentioned in 239240 (MFC 356310) and have been incorporated. If its posted in 12-stable branch of pfsense/FreeBSD-src, as of the build date, its in there .

      1 Reply Last reply Reply Quote 0
      • I
        Impatient
        last edited by

        I had that fatal trap 12: page fault message happen on a test machine with 2.5.

        I tested mb,drive,memory,switched cpu everything tested good.

        I finally swapped memory even though the previous mem passed memtest for 24 hrs
        and the machine has been running fine since.

        w0wW 1 Reply Last reply Reply Quote 0
        • w0wW
          w0w @Impatient
          last edited by w0w

          @Impatient
          I do not think it's memory, could be Intel card driver, I don't have any problem until I do known sequences on known configuration. Also 2.4.5 is not affected by this bug on the same hardware.

          1 Reply Last reply Reply Quote 0
          • I
            Impatient
            last edited by Impatient

            If it was the network card would it not mention that in the error?

            It does mention what is not in memory (supervisor read data)

            Then the result of that is the (panic: page fault).

            I run dual wan PPPoE with Reset all states if WAN IP Address changes enabled
            and get no error's running 2.5.0.a.20200313.1633 as of today on above system.
            Previously in 2.5.0.a.20200312.something.

            It has only been running for about 12 hrs. with 1 reboot.

            w0wW 1 Reply Last reply Reply Quote 0
            • w0wW
              w0w @Impatient
              last edited by w0w

              @Impatient
              My firewall is overall stable on 2.5.0, I can run it for a month until something triggers the fatal trap or "pf_test: kif == NULL", sometimes it crash on boot and 1 of 3 times crashing or/and this "pf_test: kif == NULL" message spamming, when there is the problem on the PPPoE ethernet port — for example ISP router is out of power or I have unplugged the cable or changed the link speed.
              I repeat, I do not have any of the mentioned problems on 2.4.5 version, so I think it's software problem.

              1 Reply Last reply Reply Quote 0
              • B
                BlakeThoennes
                last edited by BlakeThoennes

                Hello all,

                As was announced 2.5 to be soon mainstreamed, I jumped onto the dev branch.

                15 minutes after successful upgrade net went down, I couldnt ping or load pfsense web.
                Error streaming on screen without stop was

                igb1: TX(2) desc avail = 1024, pidx = 0

                Running 2.5.0.a.20200330.1049 (latest x64)
                Potential Solution based on power settings posted here? Not sure how to issue these commands. (from terminal at firewall, thru web, ssh...???)
                https://forum.netgate.com/topic/149643/igbx-bug-tx-1-desc-avail-no-carrier

                Bug report mentioned elsewhere here:
                https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240

                Had been running stable until now and never had a single issue.
                Only way to get the firewall working (tried ifconfig up down, bridge up down, reset web config, etc) was to reboot the firewall. Has been working for over 50 minutes now without issue...

                Heres the logs at time of event.
                Mar 30 15:15:15 kernel igb1: TX(2) desc avail = 1024, pidx = 0
                Mar 30 15:15:15 check_reload_status 356 Reloading filter
                Mar 30 15:15:15 php-fpm 343 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.1.1 )
                Mar 30 15:15:14 kernel igb1: link state changed to DOWN
                Mar 30 15:15:14 check_reload_status 356 Linkup starting $igb1
                Mar 30 15:15:14 kernel igb1: TX(1) desc avail = 42, pidx = 712

                Additional Log Hardware Information for comparison to yours if you suffer from this too...
                Mar 30 15:21:04 kernel wlan: mac acl policy registered
                Mar 30 15:21:04 kernel random: entropy device external interface
                Mar 30 15:21:04 kernel Timecounter "TSC" frequency 1600051300 Hz quality 1000
                Mar 30 15:21:04 kernel Launching APs: 3 2 1
                Mar 30 15:21:04 kernel ioapic0 <Version 2.0> irqs 0-114 on motherboard
                Mar 30 15:21:04 kernel random: unblocking device.
                Mar 30 15:21:04 kernel FreeBSD/SMP: 1 package(s) x 4 core(s)
                Mar 30 15:21:04 kernel FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
                Mar 30 15:21:04 kernel WARNING: L1 data cache covers fewer APIC IDs than a core (0 < 1)
                Mar 30 15:21:04 kernel ACPI APIC Table: <ALASKA A M I >
                Mar 30 15:21:04 kernel Event timer "LAPIC" quality 600
                Mar 30 15:21:04 kernel avail memory = 8161169408 (7783 MB)
                Mar 30 15:21:04 kernel real memory = 8589934592 (8192 MB)
                Mar 30 15:21:04 kernel TSC: P-state invariant, performance statistics
                Mar 30 15:21:04 kernel VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
                Mar 30 15:21:04 kernel Structured Extended Features3=0xc000400<IBPB,STIBP>
                Mar 30 15:21:04 kernel Structured Extended Features=0x2282<TSCADJ,SMEP,ERMS,NFPUSG>
                Mar 30 15:21:04 kernel AMD Features2=0x101<LAHF,Prefetch>
                Mar 30 15:21:04 kernel AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
                Mar 30 15:21:04 kernel Features2=0x43d8e3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,AESNI,RDRAND>
                Mar 30 15:21:04 kernel Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
                Mar 30 15:21:04 kernel Origin="GenuineIntel" Id=0x406c4 Family=0x6 Model=0x4c Stepping=4
                Mar 30 15:21:04 kernel CPU: Intel(R) Celeron(R) CPU J3160 @ 1.60GHz (1600.05-MHz K8-class CPU)
                Mar 30 15:21:04 kernel VT(efifb): resolution 800x600
                Mar 30 15:21:04 kernel FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1)
                Mar 30 15:21:04 kernel FreeBSD 12.0-RELEASE-p10 ce9563d5729(RELENG_2_5) pfSense amd64

                Suggestions? Recommend I go back to stable?

                1 Reply Last reply Reply Quote 0
                • w0wW
                  w0w
                  last edited by

                  I am waiting for 2.5.0 based on STABLE. Expected to be soon. I hope that it will be released before the end of the world. ☺

                  1 Reply Last reply Reply Quote 0
                  • B
                    BlakeThoennes
                    last edited by

                    Good news is it hasnt failed on me again since the one time 15m after original upgrade.

                    So... scary start, but stable for nearly 24hours now.

                    Hopefully that release is SOON.

                    1 Reply Last reply Reply Quote 0
                    • w0wW
                      w0w
                      last edited by

                      Re-tested on the latest build
                      2.5.0-DEVELOPMENT (amd64)
                      built on Fri Apr 03 19:36:42 EDT 2020
                      FreeBSD 12.0-RELEASE-p10
                      Don't know what exactly was merged/patched, whatever else, but I can not crash my system anymore with my test sequence. I'll check later what changes are made on github.

                      1 Reply Last reply Reply Quote 0
                      • w0wW
                        w0w
                        last edited by

                        Hmm... looks like this thing came back, after I've configured CARP and started to play with PPPoE on secondary firewall and re-plugged main ethernet cable that cames from ISP (PPPoE).

                        Crash report begins.  Anonymous machine information:

amd64
12.1-STABLE
FreeBSD 12.1-STABLE f1de4082be8(devel-12) pfSense

Crash report details:

No PHP errors found.

..........................................
<118>Starting CRON... done.
<118> Starting package Cron...done.
<118> Starting package System Patches...done.
<118> Starting package Service Watchdog...done.
<118> Starting package nut...done.
<118> Starting package Shellcmd...done.
<118> Starting package Backup...done.
<118> Starting package iperf...done.
<118> Starting /usr/local/etc/rc.d/shutdown.nut.sh...done.
<118>pfSense 2.5.0-DEVELOPMENT amd64 Fri May 22 07:43:46 EDT 2020
<118>Bootup complete
<6>ix0: link state changed to DOWN
<6>ix0: link state changed to UP
<6>ix0: link state changed to DOWN
<6>ix0: link state changed to UP
<6>gif0: link state changed to DOWN
<6>ng0: changing name to 'pppoe0'
<6>gif0: link state changed to DOWN
<6>gif0: link state changed to UP
<6>gif0: link state changed to DOWN
<6>gif0: link state changed to UP
<6>gif0: link state changed to DOWN
pf_test: kif == NULL, if_xname 
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname @��
<6>ng0: changing name to 'pppoe0'
pf_test: kif == NULL, if_xname @��
pf_test: kif == NULL, if_xname 
<6>gif0: link state changed to DOWN
<6>gif0: link state changed to UP


Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 04
fault virtual address	= 0x70
fault code		= supervisor read data, page not present
instruction pointer	= 0x20:0xffffffff80f25037
stack pointer	        = 0x28:0xfffffe0095dd2370
frame pointer	        = 0x28:0xfffffe0095dd23b0
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		= 80273 (unbound)
trap number		= 12
panic: page fault
cpuid = 2
time = 1590480096
KDB: enter: panic

                        The crash occurs only on primary firewall.
                        Full log is here

                        1 Reply Last reply Reply Quote 0
                        • w0wW
                          w0w
                          last edited by w0w

                          Got those topic messages on backup firewall also, when experimented with PPPoE (same link)

                          May 26 19:34:51 	kernel 		
May 26 19:34:51 	root 	54561 	PPPoE put down
May 26 19:34:51 	kernel 		
May 26 19:34:50 	kernel 		
May 26 19:34:50 	kernel 		
May 26 19:34:49 	kernel 		
May 26 19:34:49 	kernel 		
May 26 19:34:48 	kernel 		
May 26 19:34:48 	kernel 		
May 26 19:34:47 	kernel 		
May 26 19:34:47 	kernel 		
May 26 19:34:47 	kernel 		
May 26 19:34:46 	kernel 		
May 26 19:34:46 	kernel 		
May 26 19:34:46 	kernel 		
May 26 19:34:45 	kernel 		
May 26 19:34:45 	kernel 		
May 26 19:34:44 	kernel 		pf_test: kif == NULL, if_xname
May 26 19:34:44 	kernel 		pf_test: kif == NULL, if_xname
May 26 19:34:43 	kernel 		pf_test: kif == NULL, if_xname
May 26 19:34:43 	kernel 		pf_test: kif == NULL, if_xname
May 26 19:34:42 	kernel 		
May 26 19:34:42 	kernel 		
May 26 19:34:42 	kernel 		pf_test: kif == NULL, if_xname

                          Crashdump

                          1 Reply Last reply Reply Quote 0
                          • w0wW
                            w0w
                            last edited by

                            May be it's https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230498

                            1 Reply Last reply Reply Quote 0
                            • w0wW
                              w0w
                              last edited by w0w

                              I've played around a bit and the result is that 2.4.5-RELEASE is still not affected, and 2.5 is crashing not every time but mostly, when I issue 'killall mpd5' or even 'rc.linkup stop wan'
                              The configuration is the same. PPPoE as WAN, DHCP as WAN2, no IPv6, only failover is configured. PPPoE as tier1 and DHCP as tier2.
                              I don't think that unbound is the real cause of crash... just because I've tried to stop unbound service and repeat the sequence (multiple times disconnected and connected WAN port cable) and got another dump. crash00.txt

                              Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 06
fault virtual address	= 0x0
fault code		= supervisor read instruction, page not present
instruction pointer	= 0x20:0x0
stack pointer	        = 0x28:0xfffffe0074d614a8
frame pointer	        = 0x28:0xfffffe0074d615f0
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		= 12 (swi4: clock (0))
trap number		= 12
panic: page fault
cpuid = 3
time = 1590747377
KDB: enter: panic
����������������

                              https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234296 looks very similar.

                              1 Reply Last reply Reply Quote 0
                              • w0wW
                                w0w
                                last edited by

                                Do we have patch provided in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234296 enabled on pfSense latest 2.5 version? I mean https://svnweb.freebsd.org/base?view=revision&revision=343787

                                1 Reply Last reply Reply Quote 0
                                • jimpJ
                                  jimp Rebel Alliance Developer Netgate
                                  last edited by

                                  If it was marked fixed in 12.0-RELEASE then yes, that would be in 2.5.0. 2.5.0 snapshots are on 12.1-STABLE now, so well past that point.

                                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                  Need help fast? Netgate Global Support!

                                  Do not Chat/PM for help!

                                  w0wW 1 Reply Last reply Reply Quote 0
                                  • w0wW
                                    w0w @jimp
                                    last edited by w0w

                                    @jimp
                                    Can you suggest me something?

                                    1 Reply Last reply Reply Quote 0
                                    • jimpJ
                                      jimp Rebel Alliance Developer Netgate
                                      last edited by

                                      Nothing I'm aware of for that, I'm afraid.

                                      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                      Need help fast? Netgate Global Support!

                                      Do not Chat/PM for help!

                                      w0wW 1 Reply Last reply Reply Quote 0
                                      • w0wW
                                        w0w @jimp
                                        last edited by

                                        @jimp
                                        What do you think, сould this fatal trap be due to the radix_mpath option enabled in the kernel?
                                        Any chances to get some snapshot with this option disabled?

                                        1 Reply Last reply Reply Quote 0
                                        • jimpJ
                                          jimp Rebel Alliance Developer Netgate
                                          last edited by

                                          It's possible. There are other problems with RADIX_MPATH as well but I'm not sure if we're going to look into fixing them or back that out.

                                          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                          Need help fast? Netgate Global Support!

                                          Do not Chat/PM for help!

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.