Crash report



  • Hello,

    Total noob so excuse my ignorance. My pfSense 2.3.1 has been crashing about once a day for about a couple of days now.  Can some one help me figure out if it's a software or hardware issue? Reviewing the crash report I found these lines that may or may not be relevant:

    Timecounter "TSC" frequency 1750043421 Hz quality 1000
    Trying to mount root from ufs:/dev/ufsid/55493d304b14f899 [rw]…
    WARNING: / was not properly dismounted
    WARNING: /: TRIM flag on fs but disk does not support TRIM
    <118>Configuring crash dumps...
    <118>Using /dev/label/swap0 for dump device.
    <118>/dev/ufsid/55493d304b14f899: UNREF FILE I=240769  OWNER=root MODE=100666
    <118>/dev/ufsid/55493d304b14f899: SIZE=0 MTIME=Jun  8 16:31 2016  (CLEARED)
    <118>/dev/ufsid/55493d304b14f899: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED)
    <118>/dev/ufsid/55493d304b14f899: SUMMARY INFORMATION BAD (SALVAGED)
    <118>/dev/ufsid/55493d304b14f899: BLK(S) MISSING IN BIT MAPS (SALVAGED)
    <118>/dev/ufsid/55493d304b14f899: 17424 files, 253324 used, 421816 free (1832 frags, 52498 blocks, 0.3% fragmentation)

    Thanks in advance for any advice.



  • There's also this which may be relevant:

    Fatal trap 9: general protection fault while in kernel mode
    cpuid = 1; apic id = 02
    instruction pointer = 0x20:0xffffffff80b82b40
    stack pointer         = 0x28:0xfffffe001a3ba050
    frame pointer         = 0x28:0xfffffe001a3ba060
    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 (irq260: igb1:que 1)



  • Neither of those show anything useful to determine the source of the issue, only the second has anything to do with the crash at all. Did you submit the crash report? Don't see any from an IP that's even close to the IP you're using to reach this site. Let me know what IP it would have come from (it'll be IPv6 if your system's dual stack) and I can check it.



  • Yes, the IP is a different than mine.
    96.95.216.50
    2601:645:400:7e00:208:a2ff:fe09:2d2a

    Thank you!



  • I have submitted several crash reports.



  • Looks like you're using the traffic shaper with CODEL, which has a couple open tickets on crashes caused by it. The crashes are those.



  • Thank you for reviewing the crash report. All of the schedulers in my traffic shaper are set to CBQ and none of them have the "CoDel active queue" setting enabled. How do I determine if CoDel is being used and how do I disable it if it is?


Log in to reply