search for: queuing

flight 11929 xen-unstable running [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/11929/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-i386-i386-xl-qemuu-winxpsp3 <none executed> queued test-amd64-amd64-xl-qemuu-winxpsp3 <none executed> queued test-amd64-amd64-xl-qemuu-win7-amd64

Hello, I am using Dovecot version 2.2.10. I am quite familiar with ssh replication and I managed to set it up correctly. The only problem I see is that when i run the command: doveadm replicator status I get a wrong "Total number of known users" which is a) is different between the two (2) replicated dovecot servers, i.e. in mail1 I get a total of 21 users and in mail2 I get a total of

Hi, I have connected a TDM400P to my asterisk, I have enabled DTMF CID, the data is arriving to the asterisk but asterisk isn't interpretating it: its my full log: 1. Mar 10 16:26:03] DEBUG[8715] dsp.c: dsp busy pattern set to 0,0 2. [Mar 10 16:26:03] VERBOSE[9274] logger.c: -- Starting simple switch on 'Zap/4-1' 3. [Mar 10 16:26:03] VERBOSE[9274]

Hi, We've implemented a 'page-all' function for some of our customers, and we've noticed that on occasion the page-all will cause asterisk to crash (safe_asterisk then restarts it again). The particular customer has about 20 phones, and also has 5 Linksys 932 to monitor the state of these extensions. I'm not sure whether it is the page-all that causes the crash, or the

Timo - I upgraded to 2.1.10 on our director servers two nights ago and apart from errors associated with the directors processes restarting everything looked great for ~24 hours until I failed our the real servers last night to update the nfs mount options for the spools. I followed the suggested procedure for each backend server, just run on one of the directors, which seemed to work as

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask

-------------------------------------------------------------------------------------------- Originally posted at http://forums.digium.com/viewtopic.php?t=18045 -------------------------------------------------------------------------------------------- Hi! I'm trying to configure a DISA setup (Asterisk 1.4.11). Only, executing DISA seems to prevent any DTMF detection capability when using

Add some simple wrappers around incrementing/decrementing kthread_work.cancelling under lock, along with checking whether queuing is currently allowed on a given kthread_work, which we'll use want to implement work cancelling with DRM's vblank work helpers. Cc: Daniel Vetter <daniel at ffwll.ch> Cc: Tejun Heo <tj at kernel.org> Cc: Ville Syrj?l? <ville.syrjala at linux.intel.com> Cc: dri-devel at li...

...n cancelled at any point (e.g. before or after it's actually been queued on the kthread_worker). So, let's make all of these things possible by exposing struct kthread_flush_work, and then splitting kthread_flush_work() into two functions: kthread_queue_flush_work(); which handles possibly queuing up the kthread_flush_work on the work's respective kthread_worker, and kthread_flush_work(); which performs a simple synchronous flush just like before. We also add a DEFINE_KTHREAD_FLUSH_WORK() macro, which simply initializes a kthread_flush_work struct inline (I can't see anyone needing t...

I'm working with * and queuing and while things are mostly-working, they don't work quite as well as the docs on the wiki indicate they should. Things like leavewhenempty, the h option to queue, stuff like that. I search the archives and it seems that very few of the queuing questions are answered on the list. I'm cur...

I see that mail sent from a remote computer never leaves the computer, the last entry in /var/log/maillog being "Queued mail for delivery". 1. What is likely to cause this message? I know I registered with my remote mail server with a different name to my name on the computer. Is that likely to be the cause of my problem? And if so, what is the solution? Or is there any other likely

I'm hoping people can suggest some ideas for debugging a problem that I'm having with DTMF. Unlike most of the DTMF problems reported here, it has nothing to do with Asterisk interpreting DTMF. My problem is with the synthesis of DTMF tones on outbound calls on a PRI connected to a TE412P card. I'm running * 1.4.10.1 with Zaptel 1.4.4. It is important to note that these problems

We are having an issue where DTMF is not being sent out right away and the tone duration is inconsistent. For a test we send a '5', then a second later we send a '9', and then five seconds later we send a '5'. If you look at the logs below you can see the first '5' is played right away, then the '9' comes in and gets queued, but it doesn't start

...ndle *h, /* Add the command to the end of the queue. Kick the state machine * if there is no other command being processed, otherwise, it will * be handled automatically on a future cycle around to READY. + * Beyond this point, we have to return a cookie to the user, since + * we are queuing the command, even if kicking the state machine + * detects a failure. Not reporting a state machine failure here is + * okay - any caller of an async command will be calling more API to + * await results, and will eventually learn that the machine has + * moved on to DEAD at that time....

Alright, well it's apparently no surprise to folks that ATA tag queuing is broken at the moment. Are there any objections to me adding a few cautious words to ata(4) and tuning(7) that advise _against_ the use of ata tag queuing given that they're likely the fastest way to reboot a -STABLE box? Here's a PR that I tacked a tad bit of info into: http://www.Fre...

I encountered while stresstesting the reclocking code, that rarely (1 out of 20.000+ requests) we don't get any IRQ in nvkm_pmu_intr. This means we have a queued message on the pmu, but nouveau doesn't read it and waits infinitely in nvkm_pmu_send: if (reply) { wait_event(pmu->recv.wait, (pmu->recv.process == 0)); therefore let us use wait_event_timeout with a 1s timeout frame

I encountered while stresstesting the reclocking code, that rarely (1 out of 20.000+ requests) we don't get any IRQ in nvkm_pmu_intr. This means we have a queued message on the pmu, but nouveau doesn't read it and waits infinitely in nvkm_pmu_send: if (reply) { wait_event(pmu->recv.wait, (pmu->recv.process == 0)); therefore let us use wait_event_timeout with a 1s timeout frame

...ng running, saved searches that are triggered by various events throughout the site. All I want my site to do is update a status that the job is queued and have it picked up from there. Here is where I run into trouble, possibly because I''ve built too many systems like this that use real queuing packages. Here is what I want: Dispatch method (usually one thread is necessary): 1. Find the oldest ''queued'' record (make sure to find with :lock => true) 1a. If none, goto step 5 2. Update status to ''processing'' 3. Send to search method 4. Repeat 1 5. Done...

I encountered while stresstesting the reclocking code, that rarely (1 out of 20.000+ requests) we don't get any IRQ in nvkm_pmu_intr. This means we have a queued message on the pmu, but nouveau doesn't read it and waits infinitely in nvkm_pmu_send: if (reply) { wait_event(pmu->recv.wait, (pmu->recv.process == 0)); therefore let us use wait_event_timeout with a 1s timeout frame