search for: sirq

Hi to all, I'm trying to run Battery3 with Wine, but I'm experiencing some problems. 1. When I launch Battery (command line) I see these messages: --- fixme:win:RegisterDeviceNotificationW (hwnd=0x50062, filter=0x32fcb0,flags=0x00000004) returns a fake device notification handle! JackActivationCount::Signal value = 0 ref = 5 JackActivationCount::Signal value = 0 ref = 5

...fter 5 mins the result of "ps" is the same. The result of "top" shows below. The load average is VERY HIGHT and CPU is busy for io. # top Mem: 366504K used, 143900K free, 0K shrd, 14216K buff, 293224K cached CPU: 1.7% usr 3.5% sys 0.0% nic 0.0% idle 92.9% io 1.7% irq 0.0% sirq Load average: 103.10 103.03 102.65 1/149 5614 PID PPID USER STAT VSZ %MEM %CPU COMMAND 5532 3325 root R 3000 0.5 3.5 top 2421 1 simon D 20712 4.0 0.0 /sbin/smbd -D 594 1 simon D 20712 4.0 0.0 /sbin/smbd -D 4130 1 simon D 20712 4.0 0.0 /sbin/smbd...

Hi, Today I migrated a server form C6 to C7. The machine is dedicated for a couple of redis daemons. given the traffic etc, we see cpu0 being 100% in use immediately. No problem, had the same thing on the C6 server. So I pinned certain processes/irq's to other CPU's and made irqbalance was monitoring things. That did solve the issue in C6, but not this time. The links below contain the

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

....000000] hard-irqs-on + irq-safe-A/12: ok | ok | ok | [ 0.000000] soft-irqs-on + irq-safe-A/12: ok | ok | ok | [ 0.000000] hard-irqs-on + irq-safe-A/21: ok | ok | ok | [ 0.000000] soft-irqs-on + irq-safe-A/21: ok | ok | ok | [ 0.000000] sirq-safe-A => hirqs-on/12: ok | ok | ok | [ 0.000000] sirq-safe-A => hirqs-on/21: ok | ok | ok | [ 0.000000] hard-safe-A + irqs-on/12: ok | ok | ok | [ 0.000000] soft-safe-A + irqs-on/12: ok | ok | ok | [ 0.000000] hard-safe-A...

....000000] hard-irqs-on + irq-safe-A/12: ok | ok | ok | [ 0.000000] soft-irqs-on + irq-safe-A/12: ok | ok | ok | [ 0.000000] hard-irqs-on + irq-safe-A/21: ok | ok | ok | [ 0.000000] soft-irqs-on + irq-safe-A/21: ok | ok | ok | [ 0.000000] sirq-safe-A => hirqs-on/12: ok | ok | ok | [ 0.000000] sirq-safe-A => hirqs-on/21: ok | ok | ok | [ 0.000000] hard-safe-A + irqs-on/12: ok | ok | ok | [ 0.000000] soft-safe-A + irqs-on/12: ok | ok | ok | [ 0.000000] hard-safe-A...

On Sun, Nov 07 2010 at 6:05pm -0500, Andi Kleen <andi@firstfloor.org> wrote: > On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote: > > On 11/07/2010 08:45 PM, Andi Kleen wrote: > > >> I read about barrier-problems and data getting to the partition when > > >> using dm-crypt and several layers so I don''t know if that could be > >