Panic via pf_test



  • reinstalled with this morning's full iso.

    had ip addresses on 2 interfaces and one on the bridge they were in, which of course wasn't useful. used the console to set no address on opt1 and opt2, attached a machine via opt2, and got a panic, which i got a picture of, but nothing more yet
    panic
    mtrash_ctor
    uma_zalloc_arg
    malloc
    m_tag_alloc(+0x52)
    pf_test(+0x173)
    init_pf_mutex
    pfil_run_hooks
    ip_output
    and so on back to syscall 133 as the entry

    if i get a moment i will figure out what the source base is, check it and see if it's obvious.



  • Couldn't get a panic string, but perusing source told me this is memory use checking, so something, and given this is always the end of the backtrace probably something in pf_test, uses memory after it's been freed.

    Switching to the regular (unchecked!) kernel the issue goes away.

    I'll debug on a VM when I have more time.

    @shadow:

    reinstalled with this morning's full iso.

    had ip addresses on 2 interfaces and one on the bridge they were in, which of course wasn't useful. used the console to set no address on opt1 and opt2, attached a machine via opt2, and got a panic, which i got a picture of, but nothing more yet
    panic
    mtrash_ctor
    uma_zalloc_arg
    malloc
    m_tag_alloc(+0x52)
    pf_test(+0x173)
    init_pf_mutex
    pfil_run_hooks
    ip_output
    and so on back to syscall 133 as the entry

    if i get a moment i will figure out what the source base is, check it and see if it's obvious.


Locked