search for: irq

...kernel working with Xen 3.4 but with no success. I have been at this for 2 weeks now with different problems. Initially I could not get dom0 to boot when using LVM, so I reinstalled and didn''t use LVM. Now I am getting stack overran or currupted errors. Here is the boot log; From <IRQ 0> to the last line keeps on repeating until I power-off the machine. [ 0.000000] Reserving virtual address space above 0xf5800000 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.30-rc3-tip (root@nickamon-laptop)...

...is being reported as there? > From /var/log/dmesg, when NIC is detected and working: grep ixgbe dmesg [??? 0.999078] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 5.1.0-k-rh7.6 [??? 0.999081] ixgbe: Copyright (c) 1999-2016 Intel Corporation. [??? 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X [??? 1.720563] ixgbe 0000:01:00.0: irq 139 for MSI/MSI-X [??? 1.720568] ixgbe 0000:01:00.0: irq 140 for MSI/MSI-X [??? 1.720573] ixgbe 0000:01:00.0: irq 141 for MSI/MSI-X [??? 1.720578] ixgbe 0000:01:00.0: irq 142 for MSI/MSI-X [??? 1.720602] ixgbe 0000:01:00.0: Multiqueue Enabled...

The main change from the patches I sent out earlier this week is support for guests that use the PIC. A callback for PIC irq ack handling is also introduced. Currently, there's no mechanism to register/unregister callers to the irq ack callbacks, but they can be added when there's more than one user for the functionality. Please review.

The main change from the patches I sent out earlier this week is support for guests that use the PIC. A callback for PIC irq ack handling is also introduced. Currently, there's no mechanism to register/unregister callers to the irq ack callbacks, but they can be added when there's more than one user for the functionality. Please review.

...gt; > From /var/log/dmesg, when NIC is detected and working: > grep ixgbe dmesg > [ 0.999078] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - > version 5.1.0-k-rh7.6 > [ 0.999081] ixgbe: Copyright (c) 1999-2016 Intel Corporation. > [ 1.720556] ixgbe 0000:01:00.0: irq 138 for MSI/MSI-X > [ 1.720563] ixgbe 0000:01:00.0: irq 139 for MSI/MSI-X > [ 1.720568] ixgbe 0000:01:00.0: irq 140 for MSI/MSI-X > [ 1.720573] ixgbe 0000:01:00.0: irq 141 for MSI/MSI-X > [ 1.720578] ixgbe 0000:01:00.0: irq 142 for MSI/MSI-X > [ 1.720602] ixgbe 0000:01...

Hello, I had noticed strange crackling sound on my phone calls going through my zaptel device (TDM400P), so i decided to check on possible timer issue, and found lots of issues on forums concerning the sensibility of zaptel with IRQs, and tried about everything: moving PCI slots, noapic and acpi=off boot options, play with different kernel options: iosched/preemption/timer/..., play with BIOS PCI options, change priorities, PCI latencies, IRQ balance, smp_afinity, ................ but impossible to come up with anything co...

I setup a CentOS 6 server to use with KVM/QEMU, and I am getting the following error a good bit, granted it doesn't seem to be causing any trouble. I figured I would post and see if anyone has any ideas on the issue, or if I can just dismiss it. If I look at my logging/dmesg, I see: do_IRQ: 19.217 No irq handler for vector (irq -1) do_IRQ: 3.178 No irq handler for vector (irq -1) do_IRQ: 19.179 No irq handler for vector (irq -1) do_IRQ: 3.220 No irq handler for vector (irq -1) do_IRQ: 18.213 No irq handler for vector (irq -1) do_IRQ: 18.79 No irq handler for vector (irq -1) do_IRQ: 3...

...e Please provide description about what this refactoring is? Also does other architecture also need similar refactoring ? Thanks -Bharat > > Signed-off-by: Yijing Wang <wangyijing at huawei.com> > --- > arch/x86/include/asm/io_apic.h | 2 +- > arch/x86/include/asm/irq_remapping.h | 4 +- > arch/x86/include/asm/pci.h | 6 ++-- > arch/x86/include/asm/x86_init.h | 10 +++--- > arch/x86/kernel/apic/io_apic.c | 23 +++++++-------- > arch/x86/kernel/x86_init.c | 12 ++++---- > drivers/iommu/amd_iommu.c...

...e Please provide description about what this refactoring is? Also does other architecture also need similar refactoring ? Thanks -Bharat > > Signed-off-by: Yijing Wang <wangyijing at huawei.com> > --- > arch/x86/include/asm/io_apic.h | 2 +- > arch/x86/include/asm/irq_remapping.h | 4 +- > arch/x86/include/asm/pci.h | 6 ++-- > arch/x86/include/asm/x86_init.h | 10 +++--- > arch/x86/kernel/apic/io_apic.c | 23 +++++++-------- > arch/x86/kernel/x86_init.c | 12 ++++---- > drivers/iommu/amd_iommu.c...

On 2014/11/6 17:34, Michael S. Tsirkin wrote: > On Tue, Nov 04, 2014 at 05:35:12PM +0800, Shannon Zhao wrote: >> As the current virtio-mmio only support single irq, >> so some advanced features such as vhost-net with irqfd >> are not supported. And the net performance is not >> the best without vhost-net and irqfd supporting. >> >> This patch support virtio-mmio to request multiple >> irqs like virtio-pci. With this patch a...

On 2014/11/6 17:34, Michael S. Tsirkin wrote: > On Tue, Nov 04, 2014 at 05:35:12PM +0800, Shannon Zhao wrote: >> As the current virtio-mmio only support single irq, >> so some advanced features such as vhost-net with irqfd >> are not supported. And the net performance is not >> the best without vhost-net and irqfd supporting. >> >> This patch support virtio-mmio to request multiple >> irqs like virtio-pci. With this patch a...

Signed-off-by: Yijing Wang <wangyijing at huawei.com> --- arch/x86/include/asm/io_apic.h | 2 +- arch/x86/include/asm/irq_remapping.h | 4 +- arch/x86/include/asm/pci.h | 6 ++-- arch/x86/include/asm/x86_init.h | 10 +++--- arch/x86/kernel/apic/io_apic.c | 23 +++++++-------- arch/x86/kernel/x86_init.c | 12 ++++---- drivers/iommu/amd_iommu.c | 16 ++++++---- dri...

irq: Exclude percpu IRQs from being fixed up Xen spin unlock uses spurious ipi "lock_kicker_irq" to wake up blocked vCPUs waiting on that lock. This irq should always be disabled. However, when Dom0 is shuting down, function fixup_irqs is called which unmasks all irqs. Function unmask_irq ef...

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not

I have brand new PC with this components: CPU Intel? Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1) When I restart the machine sometimes enp1s0 is missing. It is not

Recently our automated testing system has caught a curious assertion while testing Xen 4.1.5 on a HaswellDT system. (XEN) Assertion ''(sp == 0) || (peoi[sp-1].vector < vector)'' failed at irq.c:1030 (XEN) ----[ Xen-4.1.5 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82c48016b2b4>] do_IRQ+0x514/0x750 (XEN) RFLAGS: 0000000000010093 CONTEXT: hypervisor (XEN) rax: 000000000000002f rbx: ffff830249841e80 rcx: ffff82c4803127c0 (XEN) rdx: 0000000000000...

Hello I just installed a TE110P in a Dell Poweredge 750 (rackmount), which is connected via crossover T1 cable to a adit 600. Anyway, I've encountered an array of errors, which I believe I have narrowed down to the 22 IRQ misses I encounter on zttool. I've noticed that the te110p and the usb device share an IRQ. Could that be the source of my woes? Would disabling the usb device in the bios solve my problems or could it be my configuration? -- Errors generated by asterisk chan_zap.c:7970 pri_dchannel: PRI Erro...

...] xen_swiotlb_fixup: buf=ffff880008e77000 size=32768 [ 0.146621] Placing 64MB Xen software IO TLB between ffff880004e17000 - ffff880008e17000 [ 0.146623] Xen software IO TLB at phys 0x4e17000 - 0x8e17000 [ 0.158797] xen: registering gsi 0 triggering 1 polarity 0 [ 0.158804] xen: --> irq=0 [ 0.158806] xen_set_ioapic_routing: irq 0 gsi 0 vector 240 ioapic 0 pin 0 triggering 0 polarity 0 [ 0.158818] xen: registering gsi 1 triggering 1 polarity 0 [ 0.158821] xen: --> irq=1 [ 0.158823] xen_set_ioapic_routing: irq 1 gsi 1 vector 32 ioapic 0 pin 1 triggering 0 polarity 0...

On Thu, Nov 06, 2014 at 05:54:54PM +0800, Shannon Zhao wrote: > On 2014/11/6 17:34, Michael S. Tsirkin wrote: > > On Tue, Nov 04, 2014 at 05:35:12PM +0800, Shannon Zhao wrote: > >> As the current virtio-mmio only support single irq, > >> so some advanced features such as vhost-net with irqfd > >> are not supported. And the net performance is not > >> the best without vhost-net and irqfd supporting. > >> > >> This patch support virtio-mmio to request multiple > >> irqs like...

c/s 25336:edd7c7ad1ad2 introduced the concept of a bogus vector, for in irqs delivered through the i8259 PIC after IO-APICs had been set up. However, if supurious PIC vectors are received, many "No irq handler for vector" log messages can be seen on the console. This patch adds to the bogus vector logic to detect spurious PIC vectors and simply ignore them. _m...