similar to: Deadlock problem with agents, queues and PRI (stop accepting incoming calls in PRI line)

Hi: I want to have conference call with asterisknow and need 2 ports E1.Which Digium card is better?TE212 or TE220.I haven't problem with motherboard. Regards. --------------------------------- Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I'm trying to get a TE212 working on a Dell PowerEdge 1850 running Debian etch using the latest release of libpri (1.4.0), zaptel (1.4.2.1) and asterisk (1.4.4). The initilization of the Octasic echo canceller seems to fail when the wct4xxp module is loaded. [...] VPM450: echo cancellation for 64 channels Failed to open chip, code 00103017! VPM450: Failed to initialize [...] By looking

Hello. I have a TE212 configured in E1 mode. This is shown in a cat /proc/zaptel/2 and 3 (where the card is configured): cat /proc/zaptel/2 Span 2: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" HDB3/CCS/CRC4 RED NOTOPEN 25 TE2/0/1/1 Clear 26 TE2/0/1/2 Clear 27 TE2/0/1/3 Clear 28 TE2/0/1/4 Clear 29 TE2/0/1/5 Clear 30 TE2/0/1/6 Clear

---------- Forwarded message ---------- From: Juan Carlos Huerta <juancarloshuerta at gmail.com> Date: 07-abr-2009 13:41 Subject: Re: [asterisk-r2] MFCR2 With Unicall - can unicall affect zaptel commands? To: asterisk-r2 at lists.digium.com Please wirte to asterisk-users at lists.digium.com to get help about this problem. Juan Carlos ~ Lo que no te mata te fortalece ~ On Tue, Apr 7,

Hi Guys, I'm working on some integration project with Ruby, Rack, Apache, Phusion Passenger and Xapian. I've been having intermittent issues with the flintlock code - it seems that the function FlintLock::lock is never returning and this is locking up the Ruby process. My guess is that Xapian is locking up in a system call and Ruby can't schedule its green threads. I've done

For FreeBSD 4.7 I've discovered the cause of the deadlock, but I can't figure out how to fix it. See below for traces. If the vnode limit has been reached, the vnlru process is kicked and the requestor goes to sleep to wait for the vnlru process to signal that vnodes are available (10% of the vnodes need to be freed). Under our test, none of the nodes meet the criteria for freeing,

I''m using RailsCron, and it''s working out very well for me. However, I''m having one problem right now. I use the acts_as_background on one of my model objects. In order to get it to add the cron job to the table, I have to make sure the model is loaded in environment.rb. MyObject.load However, I''m running 2-3 fcgi process on my server. Most of the time when

Hi, I'm having what looks like a deadlock using kernel 2.4.18 + ext3 + quota on a pretty loaded system. meanwhile, i moved back to ext2 again. I'm using mount-2.11g and Quota utilities version 3.05 (I also tried with 3.06). I also tried with kernel 2.4.16 just in case, but the problem exists anyway. Anything I can do? JP

Hello, I've been looking at ocfs2_rename() and I think there are two possible deadlocks: 1) ocfs2_double_lock() locks directories in the inode number order. But for a directory structure like: d1 / \ f1 d2 / f2 if you do 'mv f1 f2' and in parallel do something like 'rmdir d2' then ocfs2_double_lock() can try locking directories in order

Hi, I've found some possible deadlock in fs/ocfs2/dlm/dlmmaster.c - version 2.6.28 (probably this code is in newer versions too). Could someone confirm this? Thank you. fs/ocfs2/dlm/dlmmaster.c ================== function dlm_master_request_handler: (res->spinlock <- dlm->master_lock) ----------------------------------- spin_lock(&res->spinlock); at line 1427

There would seem to be a potential deadlock in the netfront accelerator plugin support. When the configured accelerator changes in xenstore, netfront tries to load the new plugin using request_module(). It does this from a workqueue work item. request_module() will invoke modprobe which in some circumstances (I''m not sure exactly what - I''ve not managed to reproduce it myself)

May 15 14:14:07 twittle winbindd[2635]: [2009/05/15 14:14:07, 0] nsswitch/idmap.c:idmap_init(772) May 15 14:14:07 twittle winbindd[2635]: ERROR: Initialization failed for alloc backend tdb, deferred! May 15 14:14:07 twittle winbindd[2598]: [2009/05/15 14:14:07, 0] nsswitch/winbindd_passdb.c:sid_to_name(126) May 15 14:14:07 twittle winbindd[2598]: Possible deadlock: Trying to lookup SID

Version is cvs checkout today at approx 0900 CET. Running on a debian/unstable box with dist-upgrade as of 0830 CET today, and with no windows installed. Problem can easily be reproduced, and deadloc happens everytime I do this. Open database, everything is fine, open document.. wait a few seconds and wine hangs. output from wine: -- err:win32:_EnterSysLevel (0x4075062c, level 2): Holding

Hello! I clear remarks in Makefile: DEBUG_THREADS = -DDEBUG_THREADS -DDETECT_DEADLOCKS But same things in CLI: Aug 30 18:16:31 WARNING[22292]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82f2fe0', 9 retries! -- Zap/32-1 is proceeding passing it to Zap/31-1 -- Zap/32-1 is ringing -- Accepting call from '2177' to '7141278' on channel

Author: nk151552 Repository: /hg/zfs-crypto/gate Revision: 046c28d2b15fae39e9ac18b188525af874b9dbe9 Log message: 6301766 deadlock in nis_cachemgr when addressing request to itself Files: update: usr/src/cmd/rpcsvc/nis/cachemgr/cachemgr.c update: usr/src/lib/libnsl/nis/cache/cache_api.cc update: usr/src/lib/libnsl/nis/cache/mgr_cache.cc update: usr/src/lib/libnsl/nis/cache/mgr_cache.h

We calculate timeout (either 1 or MAX_SCHEDULE_TIMEOUT) based on whether num_writers > 1 or should_grow at the top of the loop. Then, much much later, we wait for that timeout if either num_writers or should_grow is true. However, it''s possible for a racing process (calling btrfs_end_transaction()) to decrement num_writers such that we wait forever instead of for 1. Fix this by

Hi All, I am running squid as reverse proxy on FreeBSD 7.0-R amd64. After running for a while (~ 8 hours), the throughput degrades to very very low rate. I found the squid is in "zoneli" state and is already a bug report on http://www.freebsd.org/cgi/query-pr.cgi?pr=106317 But after more investigation, I found there are lots of TCP Connections in FIN_WAIT_1 and never close. # netstat

The way some DBs work is by having a separate lock monitor thread that runs every few seconds. This thread inspects a list of waiting locks for any cycles, which would indicate a circular relationship between processes holding locks & processes waiting for locks. The db then chooses a victim & kills one of the processes. (See "Inside MS SQL Server" by Delaney, pp778 for

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: 81369c96cb78f5d0d43b3f267deb0c8477aeca83 Log message: 6300246 nfs4_delegation_accept(): Deadlock: cycle in blocking chain 6321564 r_statev4_lock shouldn''t be held over dnlc_update() Files: update: usr/src/uts/common/fs/nfs/nfs4_callback.c update: usr/src/uts/common/fs/nfs/nfs4_vnops.c