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

    How to Read a Crash Report?

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 926 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.
    • T Offline
      tong
      last edited by

      So I upgraded to 2.2.5 within the last week. Fresh install as I always do. And ever since Sunday, it's been crashing at least once a day.  So I keep Looking at the crash log with the hope of being able to read something a miss, and I can't seem to decipher it.  I've Searched through a few of the topic sets here in the forums and in some of the sub-forums looking for clues on how to read this report and didn't seem to find anything.

      On top of that I'm a total noob when it comes to anything non-windows. I've actually relied very heavily on these forums and other instructional places to be able to install and troubleshoot any problems, so between being "unfamiliar" and now the crashes, I'm kinda at a loss.

      Is there a tutorial or info on how to read a crash report? Or maybe a certain marker I should be looking for that tells me "hey read here for what's crashing" ?

      Just in case this ends up still way too technical for me:

      here's my setup:
      Hardware - APU1D4 with a 32gig mSATA, and no wireless

      Packages: Squid3, Squidguard3, BandwidthD and Darkstat. (I had Sarg installed but removed it).

      Thanks

      CrashReport.txt

      1 Reply Last reply Reply Quote 0
      • C Offline
        cmb
        last edited by

        Your 3 crash reports are the same crash. bt since the attachment was messy:

        dynamic pcpu = 0xfffffe00bd2dd600
        curthread    = 0xfffff800cc89c490: pid 21399 "c-icap"
        curpcb       = 0xfffffe0045da3cc0
        fpcurthread  = none
        idlethread   = 0xfffff80003290920: tid 100004 "idle: cpu1"
        curpmap      = 0xfffff8009a85b2f8
        tssp         = 0xffffffff8219d1f8
        commontssp   = 0xffffffff8219d1f8
        rsp0         = 0xfffffe0045da3cc0
        gs32p        = 0xffffffff8219ec50
        ldt          = 0xffffffff8219ec90
        tss          = 0xffffffff8219ec80
        db:0:kdb.enter.default>  bt
        Tracing pid 21399 tid 100161 td 0xfffff800cc89c490
        ffs_clusteralloc() at ffs_clusteralloc+0x330/frame 0x45da3311
        db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0045da2650
        kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0045da2700
        kdb_reenter() at kdb_reenter+0x33/frame 0xfffffe0045da2710
        trap() at trap+0x54/frame 0xfffffe0045da2920
        calltrap() at calltrap+0x8/frame 0xfffffe0045da2920
        --- trap 0xc, rip = 0xffffffff80f35ba3, rsp = 0xfffffe0045da29e0, rbp = 0xfffffe0045da2a80 ---
        db_read_bytes() at db_read_bytes+0x53/frame 0xfffffe0045da2a80
        db_get_value() at db_get_value+0x38/frame 0xfffffe0045da2ad0
        db_backtrace() at db_backtrace+0x14b/frame 0xfffffe0045da2bd0
        db_trace_thread() at db_trace_thread+0x25/frame 0xfffffe0045da2bf0
        db_stack_trace() at db_stack_trace+0xf8/frame 0xfffffe0045da2c20
        db_command() at db_command+0x26d/frame 0xfffffe0045da2cf0
        db_script_exec() at db_script_exec+0x18f/frame 0xfffffe0045da2d90
        db_script_kdbenter() at db_script_kdbenter+0x56/frame 0xfffffe0045da2dd0
        db_trap() at db_trap+0xdb/frame 0xfffffe0045da2e60
        kdb_trap() at kdb_trap+0x129/frame 0xfffffe0045da2eb0
        trap_fatal() at trap_fatal+0x34c/frame 0xfffffe0045da2f10
        trap_pfault() at trap_pfault+0x308/frame 0xfffffe0045da2fb0
        trap() at trap+0x47a/frame 0xfffffe0045da31c0
        calltrap() at calltrap+0x8/frame 0xfffffe0045da31c0
        --- trap 0xc, rip = 0xffffffff80d74a00, rsp = 0xfffffe0045da3280, rbp = 0x45da3311 ---
        ffs_clusteralloc() at ffs_clusteralloc+0x330/frame 0x45da3311
        *** error reading from address 45da3319 ***
        db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0045da29c0
        kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0045da2a70
        kdb_reenter() at kdb_reenter+0x33/frame 0xfffffe0045da2a80
        db_get_value() at db_get_value+0x52/frame 0xfffffe0045da2ad0
        db_backtrace() at db_backtrace+0x14b/frame 0xfffffe0045da2bd0
        db_trace_thread() at db_trace_thread+0x25/frame 0xfffffe0045da2bf0
        db_stack_trace() at db_stack_trace+0xf8/frame 0xfffffe0045da2c20
        db_command() at db_command+0x26d/frame 0xfffffe0045da2cf0
        db_script_exec() at db_script_exec+0x18f/frame 0xfffffe0045da2d90
        db_script_kdbenter() at db_script_kdbenter+0x56/frame 0xfffffe0045da2dd0
        db_trap() at db_trap+0xdb/frame 0xfffffe0045da2e60
        kdb_trap() at kdb_trap+0x129/frame 0xfffffe0045da2eb0
        trap_fatal() at trap_fatal+0x34c/frame 0xfffffe0045da2f10
        trap_pfault() at trap_pfault+0x308/frame 0xfffffe0045da2fb0
        trap() at trap+0x47a/frame 0xfffffe0045da31c0
        calltrap() at calltrap+0x8/frame 0xfffffe0045da31c0
        --- trap 0xc, rip = 0xffffffff80d74a00, rsp = 0xfffffe0045da3280, rbp = 0x45da3311 ---
        ffs_clusteralloc() at ffs_clusteralloc+0x330/frame 0x45da3311
        Script command 'bt' returned error
        
        

        Doesn't look familiar. It's something in the filesystem code apparently. c-icap is the current thread at the time every time. Maybe try uninstalling squid to see if it stops. That'd help narrow it down at least.

        1 Reply Last reply Reply Quote 0
        • T Offline
          tong
          last edited by

          @cmb:

          Your 3 crash reports are the same crash. bt since the attachment was messy:

          Doesn't look familiar. It's something in the filesystem code apparently. c-icap is the current thread at the time every time. Maybe try uninstalling squid to see if it stops. That'd help narrow it down at least.

          That's awesome, thank you for the reply, will try that now.  Going to do a fresh re-install tomorrow anyways while no one is online and will see if that stops it.  On the other hand, what was it that helped you find it? or what should i be looking for to narrow it down?

          1 Reply Last reply Reply Quote 0
          • C Offline
            cmb
            last edited by

            That's all based on essentially just 2 lines there. ffs_clusteralloc at the beginning of the bt, and curthread being c-icap. Plus the entirety of the bt being the same functions on all 3.

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