9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

Harald Schmalzbauer-7
 Hello,

unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to this
panic:

panic: blockable sleep lock (sleep mutex) 16 @
/usr/local/share/deploy-tools/RELENG_9_2/src/sys/vm/uma_core.c:2553
cpuid = 1
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,4c45522f,5f474e45,2f325f39,2f637273,...)
at db_trace_self_wrapper+0x26/frame 0xf00709cc
kdb_backtrace(c0a84539,1,c0a4124d,f0070a60,1,...) at
kdb_backtrace+0x2a/frame 0xf0070a28
panic(c0a4124d,c0a73003,c09e67b9,c0a71b3c,9f9,...) at panic+0x16f/frame
0xf0070a54
witness_checkorder(c15a5788,9,c0a71b3c,9f9,0,...) at
witness_checkorder+0xaa/frame 0xf0070aac
_mtx_lock_flags(c15a5788,0,c0a71b3c,9f9,0,...) at
_mtx_lock_flags+0xb1/frame 0xf0070ad8
uma_zfree_arg(c15a4a80,c7549320,c7549cb8,c7549320,c7549320,...) at
uma_zfree_arg+0x59/frame 0xf0070b1c
free(c7549320,c85d1680,c85cedce,2f7,c743b180,...) at free+0xd8/frame
0xf0070b40
dahdi_unregister_echocan_factory(c85ce60c,c0a36b31,108,0,c743b180,...)
at dahdi_unregister_echocan_factory+0xbd/frame 0xf0070b60
dahdi_cleanup(0,f0070ba4,c06ded93,c743b180,1,...) at
dahdi_cleanup+0x13/frame 0xf0070b7c
_linux_module_modevent(c743b180,1,c85d10a0,108,0,...) at
_linux_module_modevent+0x50/frame 0xf0070b88
module_unload(c743b180,c0a34a5c,284,292,2a7,...) at
module_unload+0x43/frame 0xf0070ba4
linker_file_unload(c78e3000,0,c0a34a5c,2a7,0,...) at
linker_file_unload+0x15e/frame 0xf0070bd4
linker_file_unload(c78e3200,0,c0a34a5c,449,c85a9000,...) at
linker_file_unload+0x444/frame 0xf0070c04
kern_kldunload(c865b2f0,3,0,f0070cfc,c09bd39b,...) at
kern_kldunload+0xd1/frame 0xf0070c30
sys_kldunloadf(c865b2f0,f0070ccc,c0a85bb4,c0a428ae,c0a87198,...) at
sys_kldunloadf+0x2b/frame 0xf0070c44
syscall(f0070d08) at syscall+0x2bb/frame 0xf0070cfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf0070cfc
--- syscall (444, FreeBSD ELF32, sys_kldunloadf), eip = 0x280c088b, esp
= 0xbfbfd27c, ebp = 0xbfbfdac8 ---
KDB: enter: panic

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Loading the wcb4xxp kernel module leads to some hundred of these:

uma_zalloc_arg: zone "256" with the following non-sleepable locks held:
exclusive sleep mutex registration_mutex (registration_mutex) r = 0
(0xc85e08ac) locked @
/usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...)
at db_trace_self_wrapper+0x26/frame 0xf002e674
kdb_backtrace(c0730080,1,ffffffff,c0c72e74,f002e720,...) at
kdb_backtrace+0x2a/frame 0xf002e6d0
_witness_debugger(c0a40d44,f002e734,4,1,0,...) at
_witness_debugger+0x25/frame 0xf002e6e8
witness_warn(5,0,c0a7210b,c0a667f3,f002e768,...) at
witness_warn+0x20d/frame 0xf002e720
uma_zalloc_arg(c159d840,0,502,2,c861df34,...) at
uma_zalloc_arg+0x34/frame 0xf002e780
malloc(ec,c0aafc2c,502,c84ace00,f002e7c4,...) at malloc+0x115/frame
0xf002e7a4
devfs_alloc(0,c852f5e0,f002e7e0,246,c85c60e0,...) at
devfs_alloc+0x31/frame 0xf002e7c4
make_dev_credv(b,0,0,0,1a4,...) at make_dev_credv+0x38/frame 0xf002e7f8
make_dev(c85c60e0,b,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824
_dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at
_dahdi_assign_span+0x39e/frame 0xf002e860
dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at
dahdi_register_device+0xd0/frame 0xf002e884
b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at
b4xxp_register+0x367/frame 0xf002e8b4
b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,80000003,...) at
b4xxp_device_attach+0x141/frame 0xf002e8e0
device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame
0xf002e920
device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at
device_probe_and_attach+0x4e/frame 0xf002e93c
pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at
pci_driver_added+0xe6/frame 0xf002e964
devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at
devclass_driver_added+0x74/frame 0xf002e988
devclass_add_driver(c6e96e00,c85a49c0,7fffffff,c85a4f40,c85a49f4,...) at
devclass_add_driver+0x156/frame 0xf002e9a8
driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at
driver_module_handler+0x85/frame 0xf002e9d4
module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at
module_register_init+0xa7/frame 0xf002e9fc
linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at
linker_load_module+0xa36/frame 0xf002ebec
kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at
kern_kldload+0xca/frame 0xf002ec1c
sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at
sys_kldload+0x74/frame 0xf002ec44
syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc
--- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp =
0xbfbfd92c, ebp = 0xbfbfde18 ---
uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
exclusive sleep mutex registration_mutex (registration_mutex) r = 0
(0xc85e08ac) locked @
/usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...)
at db_trace_self_wrapper+0x26/frame 0xf002e65c
kdb_backtrace(c0730080,1,ffffffff,c0c72e74,f002e708,...) at
kdb_backtrace+0x2a/frame 0xf002e6b8
_witness_debugger(c0a40d44,f002e71c,4,1,0,...) at
_witness_debugger+0x25/frame 0xf002e6d0
witness_warn(5,0,c0a7210b,c09e67b9,c0b1ed18,...) at
witness_warn+0x20d/frame 0xf002e708
uma_zalloc_arg(c15a4d80,0,2,2,2,...) at uma_zalloc_arg+0x34/frame 0xf002e768
malloc(e,c0ac06e0,2,c06a8d9b,c0b26144,...) at malloc+0x115/frame 0xf002e78c
notify(f002e7f8,c06aa0b1,c6e76ac0,c852f5e0,f002e7e0,...) at
notify+0x58/frame 0xf002e7bc
notify_create(c6e76ac0,c852f5e0,f002e7e0,246,c85c60e0,...) at
notify_create+0xf/frame 0xf002e7c4
make_dev_credv(b,0,0,0,1a4,...) at make_dev_credv+0x1f1/frame 0xf002e7f8
make_dev(c85c60e0,b,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824
_dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at
_dahdi_assign_span+0x39e/frame 0xf002e860
dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at
dahdi_register_device+0xd0/frame 0xf002e884
b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at
b4xxp_register+0x367/frame 0xf002e8b4
b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,80000003,...) at
b4xxp_device_attach+0x141/frame 0xf002e8e0
device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame
0xf002e920
device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at
device_probe_and_attach+0x4e/frame 0xf002e93c
pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at
pci_driver_added+0xe6/frame 0xf002e964
devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at
devclass_driver_added+0x74/frame 0xf002e988
devclass_add_driver(c6e96e00,c85a49c0,7fffffff,c85a4f40,c85a49f4,...) at
devclass_add_driver+0x156/frame 0xf002e9a8
driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at
driver_module_handler+0x85/frame 0xf002e9d4
module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at
module_register_init+0xa7/frame 0xf002e9fc
linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at
linker_load_module+0xa36/frame 0xf002ebec
kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at
kern_kldload+0xca/frame 0xf002ec1c
sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at
sys_kldload+0x74/frame 0xf002ec44
syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc
--- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp =
0xbfbfd92c, ebp = 0xbfbfde18 ---
uma_zalloc_arg: zone "64" with the following non-sleepable locks held:
exclusive sleep mutex registration_mutex (registration_mutex) r = 0
(0xc85e08ac) locked @
/usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...)
at db_trace_self_wrapper+0x26/frame 0xf002e624
kdb_backtrace(c0730080,1,ffffffff,c0c72e74,f002e6d0,...) at
kdb_backtrace+0x2a/frame 0xf002e680
_witness_debugger(c0a40d44,f002e6e4,4,1,0,...) at
_witness_debugger+0x25/frame 0xf002e698
witness_warn(5,0,c0a7210b,c0a203f0,4,...) at witness_warn+0x20d/frame
0xf002e6d0
uma_zalloc_arg(c159f840,0,2,2,38,...) at uma_zalloc_arg+0x34/frame
0xf002e730
malloc(38,c0ac7088,2,f002e78c,c06dccdd,...) at malloc+0x115/frame 0xf002e754
devctl_notify_f(c0a1f42b,c0a24fe0,c0a30866,c6e51930,2,...) at
devctl_notify_f+0xb6/frame 0xf002e78c
notify(f002e7f8,c06aa0b1,c6e76ac0,c852f5e0,f002e7e0,...) at
notify+0xb5/frame 0xf002e7bc
notify_create(c6e76ac0,c852f5e0,f002e7e0,246,c85c60e0,...) at
notify_create+0xf/frame 0xf002e7c4
make_dev_credv(b,0,0,0,1a4,...) at make_dev_credv+0x1f1/frame 0xf002e7f8
make_dev(c85c60e0,b,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824
_dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at
_dahdi_assign_span+0x39e/frame 0xf002e860
dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at
dahdi_register_device+0xd0/frame 0xf002e884
b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at
b4xxp_register+0x367/frame 0xf002e8b4
b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,80000003,...) at
b4xxp_device_attach+0x141/frame 0xf002e8e0
device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame
0xf002e920
device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at
device_probe_and_attach+0x4e/frame 0xf002e93c
pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at
pci_driver_added+0xe6/frame 0xf002e964
devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at
devclass_driver_added+0x74/frame 0xf002e988
devclass_add_driver(c6e96e00,c85a49c0,7fffffff,c85a4f40,c85a49f4,...) at
devclass_add_driver+0x156/frame 0xf002e9a8
driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at
driver_module_handler+0x85/frame 0xf002e9d4
module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at
module_register_init+0xa7/frame 0xf002e9fc
linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at
linker_load_module+0xa36/frame 0xf002ebec
kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at
kern_kldload+0xca/frame 0xf002ec1c
sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at
sys_kldload+0x74/frame 0xf002ec44
syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc
--- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp =
0xbfbfd92c, ebp = 0xbfbfde18 ---
uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
exclusive sleep mutex registration_mutex (registration_mutex) r = 0
(0xc85e08ac) locked @
/usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...)
at db_trace_self_wrapper+0x26/frame 0xf002e604
kdb_backtrace(c0730080,1,ffffffff,c0c72e74,f002e6b0,...) at
kdb_backtrace+0x2a/frame 0xf002e660
_witness_debugger(c0a40d44,f002e6c4,4,1,0,...) at
_witness_debugger+0x25/frame 0xf002e678
witness_warn(5,0,c0a7210b,c09e67b9,2,...) at witness_warn+0x20d/frame
0xf002e6b0
uma_zalloc_arg(c15a4b40,0,2,2,c6e97840,...) at uma_zalloc_arg+0x34/frame
0xf002e710
malloc(c,c0ac7088,2,c0a3c6d8,38,...) at malloc+0x115/frame 0xf002e734
devctl_queue_data_f(c6e97840,2,c0a3c6d8,c0a1f42b,c0a24fe0,c0a30866,c6e51930,8,5)
at devctl_queue_data_f+0x43/frame 0xf002e754
devctl_notify_f(c0a1f42b,c0a24fe0,c0a30866,c6e51930,2,...) at
devctl_notify_f+0x12f/frame 0xf002e78c
notify(f002e7f8,c06aa0b1,c6e76ac0,c852f5e0,f002e7e0,...) at
notify+0xb5/frame 0xf002e7bc
notify_create(c6e76ac0,c852f5e0,f002e7e0,246,c85c60e0,...) at
notify_create+0xf/frame 0xf002e7c4
make_dev_credv(b,0,0,0,1a4,...) at make_dev_credv+0x1f1/frame 0xf002e7f8
make_dev(c85c60e0,b,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824
_dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at
_dahdi_assign_span+0x39e/frame 0xf002e860
dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at
dahdi_register_device+0xd0/frame 0xf002e884
b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at
b4xxp_register+0x367/frame 0xf002e8b4
b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,80000003,...) at
b4xxp_device_attach+0x141/frame 0xf002e8e0
device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame
0xf002e920
device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at
device_probe_and_attach+0x4e/frame 0xf002e93c
pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at
pci_driver_added+0xe6/frame 0xf002e964
devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at
devclass_driver_added+0x74/frame 0xf002e988
devclass_add_driver(c6e96e00,c85a49c0,7fffffff,c85a4f40,c85a49f4,...) at
devclass_add_driver+0x156/frame 0xf002e9a8
driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at
driver_module_handler+0x85/frame 0xf002e9d4
module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at
module_register_init+0xa7/frame 0xf002e9fc
linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at
linker_load_module+0xa36/frame 0xf002ebec
kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at
kern_kldload+0xca/frame 0xf002ec1c
sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at
sys_kldload+0x74/frame 0xf002ec44
syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc
--- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp =
0xbfbfd92c, ebp = 0xbfbfde18 ---
uma_zalloc_arg: zone "256" with the following non-sleepable locks held:
exclusive sleep mutex registration_mutex (registration_mutex) r = 0
(0xc85e08ac) locked @
/usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...)
at db_trace_self_wrapper+0x26/frame 0xf002e674
kdb_backtrace(c0730080,1,ffffffff,c0c72e74,f002e720,...) at
kdb_backtrace+0x2a/frame 0xf002e6d0
_witness_debugger(c0a40d44,f002e734,4,1,0,...) at
_witness_debugger+0x25/frame 0xf002e6e8
witness_warn(5,0,c0a7210b,c0a667f3,f002e768,...) at
witness_warn+0x20d/frame 0xf002e720
uma_zalloc_arg(c159d840,0,502,2,c861e768,...) at
uma_zalloc_arg+0x34/frame 0xf002e780
malloc(ec,c0aafc2c,502,c84acd00,f002e7c4,...) at malloc+0x115/frame
0xf002e7a4
devfs_alloc(0,c852f5e0,f002e7e0,246,c85c60e0,...) at
devfs_alloc+0x31/frame 0xf002e7c4
make_dev_credv(c,0,0,0,1a4,...) at make_dev_credv+0x38/frame 0xf002e7f8
make_dev(c85c60e0,c,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824
_dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at
_dahdi_assign_span+0x39e/frame 0xf002e860
dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at
dahdi_register_device+0xd0/frame 0xf002e884
b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at
b4xxp_register+0x367/frame 0xf002e8b4
b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,80000003,...) at
b4xxp_device_attach+0x141/frame 0xf002e8e0
device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame
0xf002e920
device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at
device_probe_and_attach+0x4e/frame 0xf002e93c
pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at
pci_driver_added+0xe6/frame 0xf002e964
devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at
devclass_driver_added+0x74/frame 0xf002e988
devclass_add_driver(c6e96e00,c85a49c0,7fffffff,c85a4f40,c85a49f4,...) at
devclass_add_driver+0x156/frame 0xf002e9a8
driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at
driver_module_handler+0x85/frame 0xf002e9d4
module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at
module_register_init+0xa7/frame 0xf002e9fc
linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at
linker_load_module+0xa36/frame 0xf002ebec
kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at
kern_kldload+0xca/frame 0xf002ec1c
sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at
sys_kldload+0x74/frame 0xf002ec44
syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc
--- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp =
0xbfbfd92c, ebp = 0xbfbfde18 ---
uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
exclusive sleep mutex registration_mutex (registration_mutex) r = 0
(0xc85e08ac) locked @
/usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...)
at db_trace_self_wrapper+0x26/frame 0xf002e65c
kdb_backtrace(c0730080,1,ffffffff,c0c72e74,f002e708,...) at
kdb_backtrace+0x2a/frame 0xf002e6b8
_witness_debugger(c0a40d44,f002e71c,4,1,0,...) at
_witness_debugger+0x25/frame 0xf002e6d0
witness_warn(5,0,c0a7210b,c09e67b9,c0b1ed18,...) at
witness_warn+0x20d/frame 0xf002e708
uma_zalloc_arg(c15a4d80,0,2,2,2,...) at uma_zalloc_arg+0x34/frame 0xf002e768
malloc(e,c0ac06e0,2,c06a8d9b,c0b26144,...) at malloc+0x115/frame 0xf002e78c
notify(f002e7f8,c06aa0b1,c6e76ac0,c852f5e0,f002e7e0,...) at
notify+0x58/frame 0xf002e7bc
notify_create(c6e76ac0,c852f5e0,f002e7e0,246,c85c60e0,...) at
notify_create+0xf/frame 0xf002e7c4
make_dev_credv(c,0,0,0,1a4,...) at make_dev_credv+0x1f1/frame 0xf002e7f8
make_dev(c85c60e0,c,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824
_dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at
_dahdi_assign_span+0x39e/frame 0xf002e860
dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at
dahdi_register_device+0xd0/frame 0xf002e884
b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at
b4xxp_register+0x367/frame 0xf002e8b4
b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,80000003,...) at
b4xxp_device_attach+0x141/frame 0xf002e8e0
device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame
0xf002e920
device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at
device_probe_and_attach+0x4e/frame 0xf002e93c
pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at
pci_driver_added+0xe6/frame 0xf002e964
devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at
devclass_driver_added+0x74/frame 0xf002e988
devclass_add_driver(c6e96e00,c85a49c0,7fffffff,c85a4f40,c85a49f4,...) at
devclass_add_driver+0x156/frame 0xf002e9a8
driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at
driver_module_handler+0x85/frame 0xf002e9d4
module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at
module_register_init+0xa7/frame 0xf002e9fc
linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at
linker_load_module+0xa36/frame 0xf002ebec
kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at
kern_kldload+0xca/frame 0xf002ec1c
sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at
sys_kldload+0x74/frame 0xf002ec44
syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc
--- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp =
0xbfbfd92c, ebp = 0xbfbfde18 ---
uma_zalloc_arg: zone "64" with the following non-sleepable locks held:
exclusive sleep mutex registration_mutex (registration_mutex) r = 0
(0xc85e08ac) locked @
/usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...)
at db_trace_self_wrapper+0x26/frame 0xf002e624
kdb_backtrace(c0730080,1,ffffffff,c0c72e74,f002e6d0,...) at
kdb_backtrace+0x2a/frame 0xf002e680
_witness_debugger(c0a40d44,f002e6e4,4,1,0,...) at
_witness_debugger+0x25/frame 0xf002e698
witness_warn(5,0,c0a7210b,c0a203f0,4,...) at witness_warn+0x20d/frame
0xf002e6d0
uma_zalloc_arg(c159f840,0,2,2,38,...) at uma_zalloc_arg+0x34/frame
0xf002e730
malloc(38,c0ac7088,2,f002e78c,c06dccdd,...) at malloc+0x115/frame 0xf002e754
devctl_notify_f(c0a1f42b,c0a24fe0,c0a30866,c6e51920,2,...) at
devctl_notify_f+0xb6/frame 0xf002e78c
notify(f002e7f8,c06aa0b1,c6e76ac0,c852f5e0,f002e7e0,...) at
notify+0xb5/frame 0xf002e7bc
notify_create(c6e76ac0,c852f5e0,f002e7e0,246,c85c60e0,...) at
notify_create+0xf/frame 0xf002e7c4
make_dev_credv(c,0,0,0,1a4,...) at make_dev_credv+0x1f1/frame 0xf002e7f8
make_dev(c85c60e0,c,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824
_dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at
_dahdi_assign_span+0x39e/frame 0xf002e860
dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at
dahdi_register_device+0xd0/frame 0xf002e884
b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at
b4xxp_register+0x367/frame 0xf002e8b4
b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,80000003,...) at
b4xxp_device_attach+0x141/frame 0xf002e8e0
device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame
0xf002e920
device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at
device_probe_and_attach+0x4e/frame 0xf002e93c
pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at
pci_driver_added+0xe6/frame 0xf002e964
devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at
devclass_driver_added+0x74/frame 0xf002e988
devclass_add_driver(c6e96e00,c85a49c0,7fffffff,c85a4f40,c85a49f4,...) at
devclass_add_driver+0x156/frame 0xf002e9a8
driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at
driver_module_handler+0x85/frame 0xf002e9d4
module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at
module_register_init+0xa7/frame 0xf002e9fc
linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at
linker_load_module+0xa36/frame 0xf002ebec
kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at
kern_kldload+0xca/frame 0xf002ec1c
sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at
sys_kldload+0x74/frame 0xf002ec44
syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc
--- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp =
0xbfbfd92c, ebp = 0xbfbfde18 ---
uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
exclusive sleep mutex registration_mutex (registration_mutex) r = 0
(0xc85e08ac) locked @
/usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296
KDB: stack backtrace:
db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...)
at db_trace_self_wrapper+0x26/frame 0xf002e604
kdb_backtrace(c0730080,1,ffffffff,c0c72e74,f002e6b0,...) at
kdb_backtrace+0x2a/frame 0xf002e660
_witness_debugger(c0a40d44,f002e6c4,4,1,0,...) at
_witness_debugger+0x25/frame 0xf002e678
witness_warn(5,0,c0a7210b,c09e67b9,2,...) at witness_warn+0x20d/frame
0xf002e6b0
uma_zalloc_arg(c15a4b40,0,2,2,c744b240,...) at uma_zalloc_arg+0x34/frame
0xf002e710
malloc(c,c0ac7088,2,c0a3c6d8,38,...) at malloc+0x115/frame 0xf002e734
devctl_queue_data_f(c744b240,2,c0a3c6d8,c0a1f42b,c0a24fe0,c0a30866,c6e51920,8,5)
at devctl_queue_data_f+0x43/frame 0xf002e754
devctl_notify_f(c0a1f42b,c0a24fe0,c0a30866,c6e51920,2,...) at
devctl_notify_f+0x12f/frame 0xf002e78c
notify(f002e7f8,c06aa0b1,c6e76ac0,c852f5e0,f002e7e0,...) at
notify+0xb5/frame 0xf002e7bc
notify_create(c6e76ac0,c852f5e0,f002e7e0,246,c85c60e0,...) at
notify_create+0xf/frame 0xf002e7c4
make_dev_credv(c,0,0,0,1a4,...) at make_dev_credv+0x1f1/frame 0xf002e7f8
make_dev(c85c60e0,c,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824
_dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at
_dahdi_assign_span+0x39e/frame 0xf002e860
dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at
dahdi_register_device+0xd0/frame 0xf002e884
b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at
b4xxp_register+0x367/frame 0xf002e8b4
b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,80000003,...) at
b4xxp_device_attach+0x141/frame 0xf002e8e0
device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame
0xf002e920
device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at
device_probe_and_attach+0x4e/frame 0xf002e93c
pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at
pci_driver_added+0xe6/frame 0xf002e964
devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at
devclass_driver_added+0x74/frame 0xf002e988
devclass_add_driver(c6e96e00,c85a49c0,7fffffff,c85a4f40,c85a49f4,...) at
devclass_add_driver+0x156/frame 0xf002e9a8
driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at
driver_module_handler+0x85/frame 0xf002e9d4
module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at
module_register_init+0xa7/frame 0xf002e9fc
linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at
linker_load_module+0xa36/frame 0xf002ebec
kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at
kern_kldload+0xca/frame 0xf002ec1c
sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at
sys_kldload+0x74/frame 0xf002ec44
syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc
--- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp =
0xbfbfd92c, ebp = 0xbfbfde18 ---
wcb4xxp0: <6>Did not do the highestorder stuff
<6>dahdi: Detected time shift.
<5>dahdi_echocan_mg2: Registered echo canceler 'MG2'

Starting asterisk afterwards also leads to panic.
I guess dahdi development stalled, but I wanted to try it because I'd
prefer freeswitch and need BRI support...
Is somebody familiar with dahdi and interested in making it work with
FreeBSD 9.2?

Thanks,

-Harry (not subscribed to isdn@)



signature.asc (203 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

Amitabh Kant
On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer <
[hidden email]> wrote:

>  Hello,
>
> unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to this
> panic:
>
>
 <snip>

wcb4xxp0: <6>Did not do the highestorder stuff

> <6>dahdi: Detected time shift.
> <5>dahdi_echocan_mg2: Registered echo canceler 'MG2'
>
> Starting asterisk afterwards also leads to panic.
> I guess dahdi development stalled, but I wanted to try it because I'd
> prefer freeswitch and need BRI support...
> Is somebody familiar with dahdi and interested in making it work with
> FreeBSD 9.2?
>
> Thanks,
>
> -Harry (not subscribed to isdn@)
>
>
>
Have you been able to solve the problem? I am running Freeswitch (from git,
not port) and dahdi/dahdi-kmod26 (from port) with PRI line (Digium 8 span
and single span) without any problems on 9.1.  Will test it on 9.2 and get
back to you if I see a panic .

Amitabh
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

Harald Schmalzbauer-7
 Bezüglich Amitabh Kant's Nachricht vom 21.09.2013 03:24 (localtime):

> On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     Hello,
>
>     unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to this
>     panic:
>
>
> <snip>
>
>     wcb4xxp0: <6>Did not do the highestorder stuff
>     <6>dahdi: Detected time shift.
>     <5>dahdi_echocan_mg2: Registered echo canceler 'MG2'
>
>     Starting asterisk afterwards also leads to panic.
>     I guess dahdi development stalled, but I wanted to try it because I'd
>     prefer freeswitch and need BRI support...
>     Is somebody familiar with dahdi and interested in making it work with
>     FreeBSD 9.2?
>
>     Thanks,
>
>     -Harry (not subscribed to isdn@)
>
>
>
> Have you been able to solve the problem? I am running Freeswitch (from
> git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line
> (Digium 8 span and single span) without any problems on 9.1. Will test
> it on 9.2 and get back to you if I see a panic .
Hello Amitabh,

couldn't solve my problem.
First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2 ports in NT mode, so trying anything else with dahdi before my settings get correctly recognized is probably not worth the time.
Also I have to investigate if it is still true that libpri doesn't support ptmp in NT mode!?!
In general, the freebsd dahdi port doesn't seem to be in good shape; Couldn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d' shows nothing :-( ), no man page – hard to find out anything about dahdi in FreeBSD, not even the supported hardwhere seems to be documentend anywhere...

Any hints highly appreciated, although I think the better way was to teach FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN hardware supported by i4b (ISDN4BSD)!
Or to make chan_capi work with asterisk11 – the lesser evil than fighting dahid...

Thanks,

-Harry



signature.asc (203 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

Amitabh Kant
On Mon, Sep 23, 2013 at 8:30 PM, Harald Schmalzbauer <
[hidden email]> wrote:

>  Bezüglich Amitabh Kant's Nachricht vom 21.09.2013 03:24 (localtime):
> > On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer
> > <[hidden email] <mailto:[hidden email]>> wrote:
> >
> >     Hello,
> >
> >     unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to
> this
> >     panic:
> >
> >
> > <snip>
> >
> >     wcb4xxp0: <6>Did not do the highestorder stuff
> >     <6>dahdi: Detected time shift.
> >     <5>dahdi_echocan_mg2: Registered echo canceler 'MG2'
> >
> >     Starting asterisk afterwards also leads to panic.
> >     I guess dahdi development stalled, but I wanted to try it because I'd
> >     prefer freeswitch and need BRI support...
> >     Is somebody familiar with dahdi and interested in making it work with
> >     FreeBSD 9.2?
> >
> >     Thanks,
> >
> >     -Harry (not subscribed to isdn@)
> >
> >
> >
> > Have you been able to solve the problem? I am running Freeswitch (from
> > git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line
> > (Digium 8 span and single span) without any problems on 9.1. Will test
> > it on 9.2 and get back to you if I see a panic .
> Hello Amitabh,
>
> couldn't solve my problem.
> First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2 ports
> in NT mode, so trying anything else with dahdi before my settings get
> correctly recognized is probably not worth the time.
> Also I have to investigate if it is still true that libpri doesn't support
> ptmp in NT mode!?!
> In general, the freebsd dahdi port doesn't seem to be in good shape;
> Couldn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d' shows
> nothing :-( ), no man page – hard to find out anything about dahdi in
> FreeBSD, not even the supported hardwhere seems to be documentend
> anywhere...
>
> Any hints highly appreciated, although I think the better way was to teach
> FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN
> hardware supported by i4b (ISDN4BSD)!
> Or to make chan_capi work with asterisk11 – the lesser evil than fighting
> dahid...
>
> Thanks,
>
> -Harry
>
>
>
Hello Harry

Sadly, there is not much help while installing/using dahdi on FreeBSD.
There does not seem to by any sysctls defined for dahdi which are needed to
set for certain cards. Infact, for the 8 span card, to change the default
T1  to E1, I had to make changes in the code directly.


Amitabh
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

Max Khon
Amitabh,

I suppose you are wrong about missing sysctls. Almost all dahdi module
parameters are settable using kenv and then (after the driver is
loaded) are visible via sysctl.

Max

On Tue, Sep 24, 2013 at 7:45 AM, Amitabh Kant <[hidden email]> wrote:

> On Mon, Sep 23, 2013 at 8:30 PM, Harald Schmalzbauer <
> [hidden email]> wrote:
>
>>  Bezüglich Amitabh Kant's Nachricht vom 21.09.2013 03:24 (localtime):
>> > On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer
>> > <[hidden email] <mailto:[hidden email]>> wrote:
>> >
>> >     Hello,
>> >
>> >     unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to
>> this
>> >     panic:
>> >
>> >
>> > <snip>
>> >
>> >     wcb4xxp0: <6>Did not do the highestorder stuff
>> >     <6>dahdi: Detected time shift.
>> >     <5>dahdi_echocan_mg2: Registered echo canceler 'MG2'
>> >
>> >     Starting asterisk afterwards also leads to panic.
>> >     I guess dahdi development stalled, but I wanted to try it because I'd
>> >     prefer freeswitch and need BRI support...
>> >     Is somebody familiar with dahdi and interested in making it work with
>> >     FreeBSD 9.2?
>> >
>> >     Thanks,
>> >
>> >     -Harry (not subscribed to isdn@)
>> >
>> >
>> >
>> > Have you been able to solve the problem? I am running Freeswitch (from
>> > git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line
>> > (Digium 8 span and single span) without any problems on 9.1. Will test
>> > it on 9.2 and get back to you if I see a panic .
>> Hello Amitabh,
>>
>> couldn't solve my problem.
>> First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2 ports
>> in NT mode, so trying anything else with dahdi before my settings get
>> correctly recognized is probably not worth the time.
>> Also I have to investigate if it is still true that libpri doesn't support
>> ptmp in NT mode!?!
>> In general, the freebsd dahdi port doesn't seem to be in good shape;
>> Couldn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d' shows
>> nothing :-( ), no man page – hard to find out anything about dahdi in
>> FreeBSD, not even the supported hardwhere seems to be documentend
>> anywhere...
>>
>> Any hints highly appreciated, although I think the better way was to teach
>> FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN
>> hardware supported by i4b (ISDN4BSD)!
>> Or to make chan_capi work with asterisk11 – the lesser evil than fighting
>> dahid...
>>
>> Thanks,
>>
>> -Harry
>>
>>
>>
> Hello Harry
>
> Sadly, there is not much help while installing/using dahdi on FreeBSD.
> There does not seem to by any sysctls defined for dahdi which are needed to
> set for certain cards. Infact, for the 8 span card, to change the default
> T1  to E1, I had to make changes in the code directly.
>
>
> Amitabh
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[hidden email]"
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

Amitabh Kant
Max

I could not find any info on setting those module parameters. Is there a
place where I can more info on how to set those supported parameters in
FreeBSD


Amitabh


On Mon, Nov 18, 2013 at 6:02 PM, Max Khon <[hidden email]> wrote:

> Amitabh,
>
> I suppose you are wrong about missing sysctls. Almost all dahdi module
> parameters are settable using kenv and then (after the driver is
> loaded) are visible via sysctl.
>
> Max
>
> On Tue, Sep 24, 2013 at 7:45 AM, Amitabh Kant <[hidden email]>
> wrote:
> > On Mon, Sep 23, 2013 at 8:30 PM, Harald Schmalzbauer <
> > [hidden email]> wrote:
> >
> >>  Bezüglich Amitabh Kant's Nachricht vom 21.09.2013 03:24 (localtime):
> >> > On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer
> >> > <[hidden email] <mailto:[hidden email]>> wrote:
> >> >
> >> >     Hello,
> >> >
> >> >     unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to
> >> this
> >> >     panic:
> >> >
> >> >
> >> > <snip>
> >> >
> >> >     wcb4xxp0: <6>Did not do the highestorder stuff
> >> >     <6>dahdi: Detected time shift.
> >> >     <5>dahdi_echocan_mg2: Registered echo canceler 'MG2'
> >> >
> >> >     Starting asterisk afterwards also leads to panic.
> >> >     I guess dahdi development stalled, but I wanted to try it because
> I'd
> >> >     prefer freeswitch and need BRI support...
> >> >     Is somebody familiar with dahdi and interested in making it work
> with
> >> >     FreeBSD 9.2?
> >> >
> >> >     Thanks,
> >> >
> >> >     -Harry (not subscribed to isdn@)
> >> >
> >> >
> >> >
> >> > Have you been able to solve the problem? I am running Freeswitch (from
> >> > git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line
> >> > (Digium 8 span and single span) without any problems on 9.1. Will test
> >> > it on 9.2 and get back to you if I see a panic .
> >> Hello Amitabh,
> >>
> >> couldn't solve my problem.
> >> First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2
> ports
> >> in NT mode, so trying anything else with dahdi before my settings get
> >> correctly recognized is probably not worth the time.
> >> Also I have to investigate if it is still true that libpri doesn't
> support
> >> ptmp in NT mode!?!
> >> In general, the freebsd dahdi port doesn't seem to be in good shape;
> >> Couldn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d'
> shows
> >> nothing :-( ), no man page – hard to find out anything about dahdi in
> >> FreeBSD, not even the supported hardwhere seems to be documentend
> >> anywhere...
> >>
> >> Any hints highly appreciated, although I think the better way was to
> teach
> >> FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN
> >> hardware supported by i4b (ISDN4BSD)!
> >> Or to make chan_capi work with asterisk11 – the lesser evil than
> fighting
> >> dahid...
> >>
> >> Thanks,
> >>
> >> -Harry
> >>
> >>
> >>
> > Hello Harry
> >
> > Sadly, there is not much help while installing/using dahdi on FreeBSD.
> > There does not seem to by any sysctls defined for dahdi which are needed
> to
> > set for certain cards. Infact, for the 8 span card, to change the default
> > T1  to E1, I had to make changes in the code directly.
> >
> >
> > Amitabh
> > _______________________________________________
> > [hidden email] mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "[hidden email]
> "
>
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

Max Khon
Amitabh,

You are right, the documentation about DAHDI configuration on FreeBSD
does not exist.

All parameters are visible after modules are loaded:
sysctl -a | grep dahdi

Parameter names (and values) are the same as in DAHDI/Linux - you can
refer to DAHDI/Linux documentation about specific parameters and
values you can use.

Some parameters affect driver initialization (like linemode
auto/E1/T1) so they can only be set prior to loading the driver using
kenv:

kenv dahdi.wct4xxp.default_linemode=E1

Some parameters are applied after channel reconfiguration (dahdi_cfg)
but I would suggest to use kenv or /boot/loader.conf for that.

You can also find information about DAHDI/FreeBSD in asterisk-bed
mailing list archives. E.g. this:
http://marc.info/?l=asterisk-bsd&m=128333754614913&w=2

Max

On Tue, Nov 19, 2013 at 3:18 PM, Amitabh Kant <[hidden email]> wrote:

> Max
>
> I could not find any info on setting those module parameters. Is there a
> place where I can more info on how to set those supported parameters in
> FreeBSD
>
>
> Amitabh
>
>
> On Mon, Nov 18, 2013 at 6:02 PM, Max Khon <[hidden email]> wrote:
>>
>> Amitabh,
>>
>> I suppose you are wrong about missing sysctls. Almost all dahdi module
>> parameters are settable using kenv and then (after the driver is
>> loaded) are visible via sysctl.
>>
>> Max
>>
>> On Tue, Sep 24, 2013 at 7:45 AM, Amitabh Kant <[hidden email]>
>> wrote:
>> > On Mon, Sep 23, 2013 at 8:30 PM, Harald Schmalzbauer <
>> > [hidden email]> wrote:
>> >
>> >>  Bezüglich Amitabh Kant's Nachricht vom 21.09.2013 03:24 (localtime):
>> >> > On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer
>> >> > <[hidden email] <mailto:[hidden email]>> wrote:
>> >> >
>> >> >     Hello,
>> >> >
>> >> >     unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to
>> >> this
>> >> >     panic:
>> >> >
>> >> >
>> >> > <snip>
>> >> >
>> >> >     wcb4xxp0: <6>Did not do the highestorder stuff
>> >> >     <6>dahdi: Detected time shift.
>> >> >     <5>dahdi_echocan_mg2: Registered echo canceler 'MG2'
>> >> >
>> >> >     Starting asterisk afterwards also leads to panic.
>> >> >     I guess dahdi development stalled, but I wanted to try it because
>> >> > I'd
>> >> >     prefer freeswitch and need BRI support...
>> >> >     Is somebody familiar with dahdi and interested in making it work
>> >> > with
>> >> >     FreeBSD 9.2?
>> >> >
>> >> >     Thanks,
>> >> >
>> >> >     -Harry (not subscribed to isdn@)
>> >> >
>> >> >
>> >> >
>> >> > Have you been able to solve the problem? I am running Freeswitch
>> >> > (from
>> >> > git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line
>> >> > (Digium 8 span and single span) without any problems on 9.1. Will
>> >> > test
>> >> > it on 9.2 and get back to you if I see a panic .
>> >> Hello Amitabh,
>> >>
>> >> couldn't solve my problem.
>> >> First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2
>> >> ports
>> >> in NT mode, so trying anything else with dahdi before my settings get
>> >> correctly recognized is probably not worth the time.
>> >> Also I have to investigate if it is still true that libpri doesn't
>> >> support
>> >> ptmp in NT mode!?!
>> >> In general, the freebsd dahdi port doesn't seem to be in good shape;
>> >> Couldn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d'
>> >> shows
>> >> nothing :-( ), no man page – hard to find out anything about dahdi in
>> >> FreeBSD, not even the supported hardwhere seems to be documentend
>> >> anywhere...
>> >>
>> >> Any hints highly appreciated, although I think the better way was to
>> >> teach
>> >> FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN
>> >> hardware supported by i4b (ISDN4BSD)!
>> >> Or to make chan_capi work with asterisk11 – the lesser evil than
>> >> fighting
>> >> dahid...
>> >>
>> >> Thanks,
>> >>
>> >> -Harry
>> >>
>> >>
>> >>
>> > Hello Harry
>> >
>> > Sadly, there is not much help while installing/using dahdi on FreeBSD.
>> > There does not seem to by any sysctls defined for dahdi which are needed
>> > to
>> > set for certain cards. Infact, for the 8 span card, to change the
>> > default
>> > T1  to E1, I had to make changes in the code directly.
>> >
>> >
>> > Amitabh
>> > _______________________________________________
>> > [hidden email] mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> > To unsubscribe, send any mail to
>> > "[hidden email]"
>
>
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)

Amitabh Kant
Max

Thanks for the info. Makes it much easier to work on it.

Just for my info, is there any work going on to get cards from Sangoma or
others working on FreeBSD. Digium works very well, but just wanted to know
the options.

With regards

Amitabh


On Wed, Nov 20, 2013 at 5:55 PM, Max Khon <[hidden email]> wrote:

> Amitabh,
>
> You are right, the documentation about DAHDI configuration on FreeBSD
> does not exist.
>
> All parameters are visible after modules are loaded:
> sysctl -a | grep dahdi
>
> Parameter names (and values) are the same as in DAHDI/Linux - you can
> refer to DAHDI/Linux documentation about specific parameters and
> values you can use.
>
> Some parameters affect driver initialization (like linemode
> auto/E1/T1) so they can only be set prior to loading the driver using
> kenv:
>
> kenv dahdi.wct4xxp.default_linemode=E1
>
> Some parameters are applied after channel reconfiguration (dahdi_cfg)
> but I would suggest to use kenv or /boot/loader.conf for that.
>
> You can also find information about DAHDI/FreeBSD in asterisk-bed
> mailing list archives. E.g. this:
> http://marc.info/?l=asterisk-bsd&m=128333754614913&w=2
>
> Max
>
> On Tue, Nov 19, 2013 at 3:18 PM, Amitabh Kant <[hidden email]>
> wrote:
> > Max
> >
> > I could not find any info on setting those module parameters. Is there a
> > place where I can more info on how to set those supported parameters in
> > FreeBSD
> >
> >
> > Amitabh
> >
> >
> > On Mon, Nov 18, 2013 at 6:02 PM, Max Khon <[hidden email]> wrote:
> >>
> >> Amitabh,
> >>
> >> I suppose you are wrong about missing sysctls. Almost all dahdi module
> >> parameters are settable using kenv and then (after the driver is
> >> loaded) are visible via sysctl.
> >>
> >> Max
> >>
> >> On Tue, Sep 24, 2013 at 7:45 AM, Amitabh Kant <[hidden email]>
> >> wrote:
> >> > On Mon, Sep 23, 2013 at 8:30 PM, Harald Schmalzbauer <
> >> > [hidden email]> wrote:
> >> >
> >> >>  Bezüglich Amitabh Kant's Nachricht vom 21.09.2013 03:24
> (localtime):
> >> >> > On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer
> >> >> > <[hidden email] <mailto:[hidden email]>>
> wrote:
> >> >> >
> >> >> >     Hello,
> >> >> >
> >> >> >     unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads
> to
> >> >> this
> >> >> >     panic:
> >> >> >
> >> >> >
> >> >> > <snip>
> >> >> >
> >> >> >     wcb4xxp0: <6>Did not do the highestorder stuff
> >> >> >     <6>dahdi: Detected time shift.
> >> >> >     <5>dahdi_echocan_mg2: Registered echo canceler 'MG2'
> >> >> >
> >> >> >     Starting asterisk afterwards also leads to panic.
> >> >> >     I guess dahdi development stalled, but I wanted to try it
> because
> >> >> > I'd
> >> >> >     prefer freeswitch and need BRI support...
> >> >> >     Is somebody familiar with dahdi and interested in making it
> work
> >> >> > with
> >> >> >     FreeBSD 9.2?
> >> >> >
> >> >> >     Thanks,
> >> >> >
> >> >> >     -Harry (not subscribed to isdn@)
> >> >> >
> >> >> >
> >> >> >
> >> >> > Have you been able to solve the problem? I am running Freeswitch
> >> >> > (from
> >> >> > git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line
> >> >> > (Digium 8 span and single span) without any problems on 9.1. Will
> >> >> > test
> >> >> > it on 9.2 and get back to you if I see a panic .
> >> >> Hello Amitabh,
> >> >>
> >> >> couldn't solve my problem.
> >> >> First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2
> >> >> ports
> >> >> in NT mode, so trying anything else with dahdi before my settings get
> >> >> correctly recognized is probably not worth the time.
> >> >> Also I have to investigate if it is still true that libpri doesn't
> >> >> support
> >> >> ptmp in NT mode!?!
> >> >> In general, the freebsd dahdi port doesn't seem to be in good shape;
> >> >> Couldn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d'
> >> >> shows
> >> >> nothing :-( ), no man page – hard to find out anything about dahdi in
> >> >> FreeBSD, not even the supported hardwhere seems to be documentend
> >> >> anywhere...
> >> >>
> >> >> Any hints highly appreciated, although I think the better way was to
> >> >> teach
> >> >> FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN
> >> >> hardware supported by i4b (ISDN4BSD)!
> >> >> Or to make chan_capi work with asterisk11 – the lesser evil than
> >> >> fighting
> >> >> dahid...
> >> >>
> >> >> Thanks,
> >> >>
> >> >> -Harry
> >> >>
> >> >>
> >> >>
> >> > Hello Harry
> >> >
> >> > Sadly, there is not much help while installing/using dahdi on FreeBSD.
> >> > There does not seem to by any sysctls defined for dahdi which are
> needed
> >> > to
> >> > set for certain cards. Infact, for the 8 span card, to change the
> >> > default
> >> > T1  to E1, I had to make changes in the code directly.
> >> >
> >> >
> >> > Amitabh
> >> > _______________________________________________
> >> > [hidden email] mailing list
> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> >> > To unsubscribe, send any mail to
> >> > "[hidden email]"
> >
> >
>
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
To unsubscribe, send any mail to "[hidden email]"