search for: 65540

...nd finnaly connecting, but cannot hear the voice at all. Is there any ideas as to why this is happening. (I don't have sound card in my linux server. I need one in my linux server ??) PS: callonhold is working but cannot hear the music too. look at my messages file: Dec 21 22:31:36 NOTICE[65540]: Request to schedule in the past?!?! Dec 21 22:31:36 WARNING[16384]: Unable to get our IP address, Skinny disabled Dec 21 22:31:36 NOTICE[65540]: Request to schedule in the past?!?! Dec 21 22:31:37 NOTICE[65540]: Request to schedule in the past?!?! Dec 21 22:31:37 WARNING[16384]: Unable to open /d...

...est [root at mail ~]# du -k --max-depth=1 /mdboxes/test/ 220 /mdboxes/test/mailboxes 6029348 /mdboxes/test/storage 6029592 /mdboxes/test/ [root at mail ~]# doveadm backup -u test mdbox:/tmp/MDBOX_TEMP/ [root at mail ~]# du -k --max-depth=1 /tmp/MDBOX_TEMP/ 16 /tmp/MDBOX_TEMP/mailboxes 65540 /tmp/MDBOX_TEMP/storage 65568 /tmp/MDBOX_TEMP/

...0 0 PCI-MSI 65537-edge virtio0-req.0 26: 0 35 0 0 PCI-MSI 65538-edge virtio0-req.1 27: 0 0 32 0 PCI-MSI 65539-edge virtio0-req.2 28: 0 0 0 0 PCI-MSI 65540-edge virtio0-req.3 ... ... In above case, there is one msix vector per queue. This is because the max number of queues is not limited by the number of possible cpus. By default, nvme (regardless about write_queues and poll_queues) and xen-blkfront limit the number of queues with num_possib...

...0 0 PCI-MSI 65537-edge virtio0-req.0 26: 0 35 0 0 PCI-MSI 65538-edge virtio0-req.1 27: 0 0 32 0 PCI-MSI 65539-edge virtio0-req.2 28: 0 0 0 0 PCI-MSI 65540-edge virtio0-req.3 ... ... In above case, there is one msix vector per queue. This is because the max number of queues is not limited by the number of possible cpus. By default, nvme (regardless about write_queues and poll_queues) and xen-blkfront limit the number of queues with num_possib...

.../mdboxes/test/mailboxes >> 6029348 /mdboxes/test/storage >> 6029592 /mdboxes/test/ >> >> [root at mail ~]# doveadm backup -u test mdbox:/tmp/MDBOX_TEMP/ >> [root at mail ~]# du -k --max-depth=1 /tmp/MDBOX_TEMP/ >> 16 /tmp/MDBOX_TEMP/mailboxes >> 65540 /tmp/MDBOX_TEMP/storage >> 65568 /tmp/MDBOX_TEMP/ >> -- Alexandros Soumplis Systems Engineer (M.Sc, RHCE, VCP, SCSA) National Documentation Center / N.H.R.F. Information Systems Department 48, Vas. Constantinou Av. 116 35 Athens, Greece phone: +30 210 7273984 fax: +30 210 725...

...0 0 PCI-MSI 65536-edge virtio0-config 25: 0 0 PCI-MSI 65537-edge virtio0-control 26: 0 0 PCI-MSI 65538-edge virtio0-event 27: 296 0 PCI-MSI 65539-edge virtio0-request 28: 0 139 PCI-MSI 65540-edge virtio0-request 29: 0 0 PCI-MSI 65541-edge virtio0-request 30: 0 0 PCI-MSI 65542-edge virtio0-request # ls /sys/block/sda/mq 0 1 2 3 ------------------------------------------------------------- Here is test result of virtio-blk:...

...mdboxes/test/storage >>>> 6029592 /mdboxes/test/ >>>> >>>> [root at mail ~]# doveadm backup -u test mdbox:/tmp/MDBOX_TEMP/ >>>> [root at mail ~]# du -k --max-depth=1 /tmp/MDBOX_TEMP/ >>>> 16 /tmp/MDBOX_TEMP/mailboxes >>>> 65540 /tmp/MDBOX_TEMP/storage >>>> 65568 /tmp/MDBOX_TEMP/ >>>> >> >>

..._latency_test.c' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:32:64-v128:32:128-a0:0:32-n32-S32" target triple = "armv4t--" define i32 @f1(i32* nocapture %p1, i32* nocapture %p2) nounwind { entry: store volatile i32 65540, i32* %p1, align 4, !tbaa !0 %0 = load volatile i32* %p2, align 4, !tbaa !0 ret i32 %0 } define i32 @f2(i32* nocapture %p1, i32* nocapture %p2) nounwind { entry: store i32 65540, i32* %p1, align 4, !tbaa !0 %0 = load i32* %p2, align 4, !tbaa !0 ret i32 %0 } !0 = metadata !{metadata !&qu...

...ith tagged BAD responses. $ COMPRESS=n /tmp/many-fetch.pl 65539 [?] C: x UID FETCH 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,? [65539 bytes] S: x OK Fetch completed (0.005 + 0.001 + 0.004 secs). C: x UID FETCH 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,? [65540 bytes] S: x BAD Error in IMAP command UID FETCH: IMAP command line too large (0.001 + 0.001 secs). C: x UID FETCH 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,? [65541 bytes] S: x BAD Error in IMAP command UID FETCH: IMAP command line too large (0.001 + 0.001 secs). With COMPR...

...I-MSI 65537-edge virtio0-req.0 >> 26: 0 35 0 0 PCI-MSI 65538-edge virtio0-req.1 >> 27: 0 0 32 0 PCI-MSI 65539-edge virtio0-req.2 >> 28: 0 0 0 0 PCI-MSI 65540-edge virtio0-req.3 >> ... ... >> >> In above case, there is one msix vector per queue. > > Please note that this is pci-specific... > >> >> >> This is because the max number of queues is not limited by the number of >> possible cpus. >&gt...

...I-MSI 65537-edge virtio0-req.0 >> 26: 0 35 0 0 PCI-MSI 65538-edge virtio0-req.1 >> 27: 0 0 32 0 PCI-MSI 65539-edge virtio0-req.2 >> 28: 0 0 0 0 PCI-MSI 65540-edge virtio0-req.3 >> ... ... >> >> In above case, there is one msix vector per queue. > > Please note that this is pci-specific... > >> >> >> This is because the max number of queues is not limited by the number of >> possible cpus. >&gt...

...0 PCI-MSI 65537-edge virtio0-req.0 > 26: 0 35 0 0 PCI-MSI 65538-edge virtio0-req.1 > 27: 0 0 32 0 PCI-MSI 65539-edge virtio0-req.2 > 28: 0 0 0 0 PCI-MSI 65540-edge virtio0-req.3 > ... ... > > In above case, there is one msix vector per queue. Please note that this is pci-specific... > > > This is because the max number of queues is not limited by the number of > possible cpus. > > By default, nvme (regardless about w...

...0 PCI-MSI 65537-edge virtio0-req.0 > 26: 0 35 0 0 PCI-MSI 65538-edge virtio0-req.1 > 27: 0 0 32 0 PCI-MSI 65539-edge virtio0-req.2 > 28: 0 0 0 0 PCI-MSI 65540-edge virtio0-req.3 > ... ... > > In above case, there is one msix vector per queue. > > > This is because the max number of queues is not limited by the number of > possible cpus. > > By default, nvme (regardless about write_queues and poll_queues) and > xen-b...

...1 /mdboxes/test/ > 220 /mdboxes/test/mailboxes > 6029348 /mdboxes/test/storage > 6029592 /mdboxes/test/ > > [root at mail ~]# doveadm backup -u test mdbox:/tmp/MDBOX_TEMP/ > [root at mail ~]# du -k --max-depth=1 /tmp/MDBOX_TEMP/ > 16 /tmp/MDBOX_TEMP/mailboxes > 65540 /tmp/MDBOX_TEMP/storage > 65568 /tmp/MDBOX_TEMP/ >

...t;>> 6029348 /mdboxes/test/storage >>> 6029592 /mdboxes/test/ >>> >>> [root at mail ~]# doveadm backup -u test mdbox:/tmp/MDBOX_TEMP/ >>> [root at mail ~]# du -k --max-depth=1 /tmp/MDBOX_TEMP/ >>> 16 /tmp/MDBOX_TEMP/mailboxes >>> 65540 /tmp/MDBOX_TEMP/storage >>> 65568 /tmp/MDBOX_TEMP/ >>> > >

...(but, of course, I'm tying up resources...not a good long term solution). Console output is as follows for problem calls: Jul 5 15:18:44 WARNING[9256]: chan_iax2.c:1477 attempt_transmit: Max retries exceeded to host xx.xx.xx.xx on IAX2/yyy@ xx.xx.xx.xx:4569/3 (type = 2, subclass = 4, ts=65540, seqno=1) Jul 5 15:18:44 WARNING[9256]: app_meetme.c:962 conf_run: Unable to write frame to channel: No child processes == Spawn extension (toll, 1001074, 5) exited non-zero on 'IAX2/ yyy@ xx.xx.xx.xx:4569/3' -- Hungup 'IAX2/yyy@ xx.xx.xx.xx:4569/3' I've experimente...

...;>>>> 6029592 /mdboxes/test/ >>>>> >>>>> [root at mail ~]# doveadm backup -u test mdbox:/tmp/MDBOX_TEMP/ >>>>> [root at mail ~]# du -k --max-depth=1 /tmp/MDBOX_TEMP/ >>>>> 16 /tmp/MDBOX_TEMP/mailboxes >>>>> 65540 /tmp/MDBOX_TEMP/storage >>>>> 65568 /tmp/MDBOX_TEMP/ >>>>> >>> >>>

...e virtio0-req.0 > >> 26: 0 35 0 0 PCI-MSI 65538-edge virtio0-req.1 > >> 27: 0 0 32 0 PCI-MSI 65539-edge virtio0-req.2 > >> 28: 0 0 0 0 PCI-MSI 65540-edge virtio0-req.3 > >> ... ... > >> > >> In above case, there is one msix vector per queue. > > > > Please note that this is pci-specific... > > > >> > >> > >> This is because the max number of queues is not limited...

...;>>>> 26: 0 35 0 0 PCI-MSI 65538-edge virtio0-req.1 >>>>> 27: 0 0 32 0 PCI-MSI 65539-edge virtio0-req.2 >>>>> 28: 0 0 0 0 PCI-MSI 65540-edge virtio0-req.3 >>>>> ... ... >>>>> >>>>> In above case, there is one msix vector per queue. >>>> Please note that this is pci-specific... >>>> >>>>> >>>>> This is because the max number o...

...29592 /mdboxes/test/ >>>>>> >>>>>> [root at mail ~]# doveadm backup -u test mdbox:/tmp/MDBOX_TEMP/ >>>>>> [root at mail ~]# du -k --max-depth=1 /tmp/MDBOX_TEMP/ >>>>>> 16 /tmp/MDBOX_TEMP/mailboxes >>>>>> 65540 /tmp/MDBOX_TEMP/storage >>>>>> 65568 /tmp/MDBOX_TEMP/ >>>>>> >>>> >>>>