Re: 6.0-BETA3 and Asterisk

From: Jason George (lists_at_masterplan.org)
Date: 09/02/05

  • Next message: Antony Mawer: "Re: FreeBSD6.0 and VMWare 5.0.. No go"
    Date: Thu, 1 Sep 2005 17:15:27 -0600 (MDT)
    To: Boris Samorodov <bsam@ipt.ru>
    
    

    On Thu, 1 Sep 2005, Boris Samorodov wrote:

    > On Thu, 1 Sep 2005 14:07:19 +0100 Brian Candler wrote:
    > > Can mismatched library versions really cause kernel panics??
    >
    > Can't say for sure. But lets solve problems by steps. Using different
    > system libraries simultaneously is not right (we don't have compat-5x).
    >
    > If the case remain after rebuilding ports, we'll ask kernel gurus to
    > help us.
    >

    It isn't the libraries... it's the kernel... kldunload is causing a panic
    in this case for the Zaptel driver. I'm not even getting as far as
    starting up Asterisk.

    Kernel and full buildworld:
    FreeBSD 6.0-BETA3 #3: Thu Sep 1 16:33:06 MDT 2005

    Running "/usr/local/etc/rc.d/zaptel.sh start"

    Zapata Telephony Interface Registered on major 196
    ZapTel device: vendor=e159 device=1 subvendor=8086
    wcfxo0: <Generic Clone> port 0x2400-0x24ff mem 0x42000000-0x42000fff irq
    11 at device 14.0 on pci0
    ZapTel Attach for wcfxo0: deviceID : 0xe159
    wcfxo0: [GIANT-LOCKED]
    wcfxo: DAA mode is 'FCC'
    Found a Wildcard FXO: Generic Clone
    ZapTel device loaded.

    Running "/usr/local/etc/rc.d/zaptel.sh stop"

    lock order reversal
     1st 0xc106c8c8 mt_zone (UMA zone) @ vm/uma_core.c:2461
     2nd 0xc18c3044 user map (user map) @ vm/vm_map.c:2997
    KDB: stack backtrace:
    kdb_backtrace(0,ffffffff,c09334f8,c0933408,c08bf06c) at kdb_backtrace+0x29
    witness_checkorder(c18c3044,9,c08741f6,bb5) at witness_checkorder+0x564
    _sx_xlock(c18c3044,c08741ed,bb5) at _sx_xlock+0x50
    _vm_map_lock_read(c18c3000,c08741ed,bb5,1000016,c18c5480) at
    _vm_map_lock_read+0x37
    vm_map_lookup(ccb03b1c,0,1,ccb03b20,ccb03b10) at vm_map_lookup+0x28
    vm_fault(c18c3000,0,1,0,c16b2d80) at vm_fault+0x66
    trap_pfault(ccb03be4,0,15) at trap_pfault+0xee
    trap(c0870008,ccb00028,c0620028,0,c106c8c0) at trap+0x341
    calltrap() at calltrap+0x5
    --- trap 0xc, eip = 0xc07833d4, esp = 0xccb03c24, ebp = 0xccb03c30 ---
    uma_zfree_internal(c1061960,c1945800,0,1,3) at uma_zfree_internal+0xd4
    uma_zfree_arg(c1061960,c1945800,0) at uma_zfree_arg+0x2ed
    malloc_uninit(c194cce0) at malloc_uninit+0x95
    linker_file_sysuninit(c16d6300,0,2,c16d6300,c18c5418) at
    linker_file_sysuninit+0x7d
    linker_file_unload(c16d6300,0,0,c16b2d80,ccb03cdc) at
    linker_file_unload+0x116
    kern_kldunload(c16b2d80,3,0,ccb03d30,c07f167b) at kern_kldunload+0x7c
    kldunloadf(c16b2d80,ccb03d04,2,2,292) at kldunloadf+0x1e
    syscall(3b,3b,3b,3,bfbfee04) at syscall+0x22f
    Xint0x80_syscall() at Xint0x80_syscall+0x1f
    --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280b45b7, esp =
    0xbfbfe85c, ebp = 0xbfbfecc8 ---

    Fatal trap 12: page fault while in kernel mode
    cpuid = 0; apic id = 00
    fault virtual address = 0x15
    fault code = supervisor read, page not present
    instruction pointer = 0x20:0xc07833d4
    stack pointer = 0x28:0xccb03c24
    frame pointer = 0x28:0xccb03c30
    code segment = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags = interrupt enabled, resume, IOPL = 0
    current process = 921 (kldunload)
    [thread pid 921 tid 100100 ]
    Stopped at uma_zfree_internal+0xd4: movzbl 0x15(%ebx),%eax
    db>
    db>

    db> trace
    Tracing pid 921 tid 100100 td 0xc16b2d80
    uma_zfree_internal(c1061960,c1945800,0,1,3) at uma_zfree_internal+0xd4
    uma_zfree_arg(c1061960,c1945800,0) at uma_zfree_arg+0x2ed
    malloc_uninit(c194cce0) at malloc_uninit+0x95
    linker_file_sysuninit(c16d6300,0,2,c16d6300,c18c5418) at
    linker_file_sysuninit+0x7d
    linker_file_unload(c16d6300,0,0,c16b2d80,ccb03cdc) at
    linker_file_unload+0x116
    kern_kldunload(c16b2d80,3,0,ccb03d30,c07f167b) at kern_kldunload+0x7c
    kldunloadf(c16b2d80,ccb03d04,2,2,292) at kldunloadf+0x1e
    syscall(3b,3b,3b,3,bfbfee04) at syscall+0x22f
    Xint0x80_syscall() at Xint0x80_syscall+0x1f
    --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280b45b7, esp =
    0xbfbfe85c, ebp = 0xbfbfecc8 ---
    db>
    db> ps
      pid proc uid ppid pgrp flag stat wmesg wchan cmd
      921 c18c5418 0 920 920 0004002 [CPU 0] kldunload
    [snip]
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Antony Mawer: "Re: FreeBSD6.0 and VMWare 5.0.. No go"

    Relevant Pages

    • Panics at boot, (page fault)
      ... My FreeBSD keeps giving me kernel panics at boot, ... acpi0: on motherboard ... 2 ports with 2 removable, ...
      (comp.unix.bsd.freebsd.misc)
    • Re: kernel panic with aol
      ... >>> uses it with aol, 10.3, on dialup. ... it is probably the AOL software inducing the panic. ... Kernel panics should not ...
      (comp.sys.mac.system)
    • Minimal boot CD
      ... I knew I needed some kind of sane working environment for the kernel to ... does the initrd have to be a specific ... but it still kernel panics. ... I included RAM disk support Default RAM disk size) and ...
      (comp.os.linux.embedded)
    • RE: kernel panic [linux 2.2.19-7] on UDP scan CP4.1-SP5
      ... kernel panic [linux 2.2.19-7] on UDP scan CP4.1-SP5 ... kernel panics only when firewall-1 is running. ...
      (Vuln-Dev)
    • Re: VPC Compatibility with Tiger
      ... Due to the nature of the kernel panics and some rumors, I suspect this may be addressed by Apple... ... And HFS Journaling doesn't help when the panic occurs... ...
      (microsoft.public.mac.virtualpc)