search for: queued

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 <none executed> queued test-amd64-amd64-xl-pcipt-intel <none executed> queued test-amd64-amd64-xl <none executed>...

...ve to delete a file in /var/run/dovecot or something in order to do it? The only way I tried (not successfully though) to reset it is by executing the command: for i in `doveadm user '*'` ;do doveadm replicator remove $i ; done which does empties all existing users (16), but leaves me with Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 0 Waiting 'failed' requests 0 Total number of known users 5 in mail1 server and Queued 'sy...

...[s at from-trunk:2] Wait("Zap/4-1", "4") in new stack 5. [Mar 10 16:26:03] DTMF[9274] channel.c: DTMF end '9' received on Zap/4-1, duration 0 ms 6. [Mar 10 16:26:03] DTMF[9274] channel.c: DTMF begin emulation of '9' with duration 100 queued on Zap/4-1 7. [Mar 10 16:26:03] DTMF[9274] channel.c: DTMF end emulation of '9' queued on Zap/4-1 8. [Mar 10 16:26:03] DTMF[9274] channel.c: DTMF end '3' received on Zap/4-1, duration 0 ms 9. [Mar 10 16:26:03] DTMF[9274] channel.c: DTMF begin emulation...

...local] new state Idle for Notify User xxxxxx6324 [Mar 14 12:56:18] VERBOSE[8301] logger.c: Extension Changed xxxxxx6297[ext-local] new state Idle for Notify User xxxxxx6293 [Mar 14 12:56:18] VERBOSE[8301] logger.c: Extension Changed xxxxxx6297[ext-local] new state Idle for Notify User xxxxxx6311 (queued) [Mar 14 12:56:18] VERBOSE[8301] logger.c: Extension Changed xxxxxx6297[ext-local] new state Idle for Notify User xxxxxx6315 [Mar 14 12:56:18] VERBOSE[8301] logger.c: Extension Changed xxxxxx6297[ext-local] new state Idle for Notify User xxxxxx6297 (queued) [Mar 14 12:56:18] VERBOSE[8301] logger....

...for each backend server, just run on one of the directors, which seemed to work as expected. doveadm director add x.x.x.x 0 doveadm director flush x.x.x.x The following errors on the directors that started after this went unnoticed until this AM. director: User bb host lookup failed: Timeout - queued for 30 secs (Ring synced for 36 secs) director: User cc host lookup failed: Timeout - queued for 48 secs (Ring synced for 66 secs, user refreshed 12 secs ago) director: User dd host lookup failed: Timeout - queued for 124 secs (Ring synced for 119 secs, weak user, user refreshed 155 secs ago) di...

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 0x409 (media error) <F> ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5...

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 0x409 (media error) <F> ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5...

...ssthrough '1' on Zap/1-1 Scheduling timer at 0 sample intervals Set channel Zap/1-1 to write format ulaw Oooh, got something to jump out with ('1')! DTMF digit: 1 on Zap/1-1 DTMF end '1' received on Zap/1-1, duration 0 ms DTMF begin emulation of '1' with duration 100 queued on Zap/1-1 DTMF end emulation of '1' queued on Zap/1-1 DTMF digit: 1 on Zap/1-1 DTMF end '1' received on Zap/1-1, duration 0 ms DTMF begin emulation of '1' with duration 100 queued on Zap/1-1 DTMF end emulation of '1' queued on Zap/1-1 == CDR updated on Zap/1-1 Lau...

...struct kthread_worker *worker, + struct kthread_work *work); +void kthread_unblock_work_queuing(struct kthread_worker *worker, + struct kthread_work *work); void kthread_destroy_worker(struct kthread_worker *worker); +/** + * kthread_work_queuable - whether or not a kthread work can be queued + * @work: The kthread work to check + * + * Checks whether or not queuing @work is currently blocked from queuing, + * either by kthread_cancel_work_sync() and friends or + * kthread_block_work_queuing(). + * + * Returns: whether or not the @work may be queued. + */ +static inline bool kthread_wor...

...d work which use kthread_work, since it means we'd need to drop any spinlocks for new delayed work implementations before we can actually call kthread_flush_work(). In the time between dropping locks and calling kthread_flush_work(), the work might have already executed once and have gotten re-queued by the time we're ready. This would mean that once the user finally executes kthread_flush_work(), we'd accidentally wait for someone else's queued work instead of our own. For DRM vblank works it's preferable that we just return immediately during such races, instead of blocking o...

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 curious why that is. I figure there are X possibilities: 1. The info

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 cause? Incidentally, I c...

...(basically putting myself in place of SendDTMF). Immediately I saw doubled up an missed digits. I turned on DTMF debugging on the second Asterisk box, and doubled-up digits always seem to take this form: [Aug 17 10:50:05] DTMF[25160] channel.c: DTMF begin emulation of '4' with duration 90 queued on SIP/5060-08da0d70 [Aug 17 10:50:05] DTMF[25160] channel.c: DTMF end emulation of '4' queued on SIP/5060-08da0d70 [Aug 17 10:50:05] DTMF[25160] channel.c: DTMF end '4' received on SIP/5060-08da0d70, duration 70 ms [Aug 17 10:50:05] DTMF[25160] channel.c: DTMF begin emulation of ...

...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 playing until five seconds later and it plays for six seconds. Then the last '5' is played. The DTMF is coming in as only 'end' packets and we can't change that. For this reason we have turned on rfc2833compensate. Using Asterisk 1.4.11. Any ideas?...

Although rare, it is possible that nbd_internal_run(cmd_issue) will report failure (perhaps because the server disconnected at the wrong time), even though we have queued the user's command. If we have a valid cookie, we MUST return it for the sake of users that will be calling nbd_aio_command_complete, as otherwise the user has no idea what cookie to wait on. Ignoring the state machine failure is okay; the whole idea of an asynch command is that the user will...

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:

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 and just check whether there is a message queued and handle it if t...

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 and just check whether there is a message queued and handle it if t...

...t to avoid too many workers to keep the process count down. I''m now working on a new scheme that pushes this example. Basically, I have some long 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 s...

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 and just check whether there is a message queued and handle it if t...