search for: interrrupting

Hi all, I have dom0 and a guest on the same cpu: cpu0. However, when I look at interrupts and ipis (with Xenperf) I get the following. There is nothing going on Cpu3 so why the high number of IPIs? I have done a reset of the counters, but after I run my workload on the guest cpu3 IPIS go from 0 to 210276 (Dom- has only 1 cpu and xm vcpu-list shows the other 3 cpus in blocked state. The

Hi all, Which is the practical (from your experience) limit of the number of X100P cards installed in a single Asterisk box? Asterisk can work reliable with 6 X100P cards in the same box? Anyone know when the 4 ports FXO Digium card will be available on the market? Many thanks, Dan P.S. Please do not aswer with RTFG ...tried before without success...:-))

The following is mainly a capture of parts of multiple off-line discussions within members of the Crossbow team (Gopi, Thiru, Roamer, May-Lin, Thirumailai, Nitin, KB, ...), I thought I''d open it up to other participants. Crossbow''s core scheduling involves switching a NIC (or individual Rx rings on the NIC) to polling mode. The receive interrupt will become not only rarer,

Hi Konrad, Due to a 2.6.37-merge-window kernel now being able to boot under Xen i was able to test my xhci controller under dom0 which i previously couldn''t. The results: A) 2.6.37-merge-window kernel baremetal: Videograbbing while doing 20 iterations of make -j6 of kernel works. B) Xen + 2.6.37-merge-window kernel as Dom0: Videograbbing while doing 20 iterations of make -j6 of kernel

The delay scheduler dequeue routine has some code cut&pasted from the TBF scheduler that caused a race with E1000 when ring got full. It looks like net schedulers should never be calling netif_queue_stopped because the queue may get unstopped by interrrupt or receive soft irq (NAPI) which races with the dequeue in the transmit scheduler. Also, if requeuing the packet fails, it is probably

yes, the cause of BSOD 0x101 is that watchdog time interrupt was not received by the vcpu in a certain timeout in Windows kernel . this is taken place especially in vista kernel. Generally speaking, we have some ways to fix this, one is that we an write a programme whitch can intercept the trigger of BSOD 0x101, on the other word, we make kernel don''t care the watchdog time interrrupt.

...'s, and they also are experiencing the issues. Server is a Dell Poweredge 2850, 2 x 2.8GHz Zeons, 4GB RAM, 73GB x 2 u320 hard drives in RAID-1, with a hotspare. Running a stock Fedora Core 4 install, with only mysql and apache running. Disabled ACPI and framebuffer, and have the Sangoma card interrrupting on CPU0 only, all other devices interrupting on CPU1. Using onboard gig-E NIC with current drivers. We are connected to the PSTN through a Sangoma A104D (current firmware), using E&M Wink signalling. Sangoma drivers are the current 2.3.4-betadrivers recommended by Sangoma. I have spent the...

I'm confused by the page documenting tryCatch and friends. I think it describes 3 separate mechanisms: tryCatch (in which control returns to the invoking tryCatch), withCallHandlers (in which control goes up to the calling handler/s but then continues from the point at which signalCondition() was invoked), and withRestarts (I can't tell where control ends up). For tryCatch the docs say

Hi All I am using version 0.3.13.3 and since there is no logging support for win32 application. I was wondering if it was possible to get any kind of logging at all. I have tried to these two options 1. Stream redirection using "mongrel_rails start -c C:/myspace/snapshot -p 4111 -t 70 -e production -P log/mongrel-1.pid > C:\temp\mongrel-1.log" The console print the output stream