similar to: qemu/kvm: "spurious APIC interrupt"

Hi all, Im using qemu 0.12.3 .I have come to a point where i have developed a small kernel (setting up the IDT, GDT n all) Im disabling 8259 and enabling Local APIC but im unable to write into Local APIC registers . can anyone tell me is there something which im missing ? Here is my piece of code SVR EQU 0FEE000F0H ; define the Spurious interrupt vector APIC_ENABLE

Hi all, Im using qemu 0.12.3 .I have come to a point where i have developed a small kernel (setting up the IDT, GDT n all) Im disabling 8259 and enabling Local APIC but im unable to write into Local APIC registers . can anyone tell me is there something which im missing ? Here is my piece of code SVR EQU 0FEE000F0H ; define the Spurious interrupt vector APIC_ENABLE

Hi all, I'm Initializing the Local and IO APIC for a propeitary operating system running in Virtualized Environment . Im facing some problem with qemu-kvm but the code runs fine with qemu. when i run my kernel image with qemu-kvm it gives emulation error failure trying to execute the code outside ROM or RAM at fec00000(IO APIC base address) but the same code runs fine with qemu. can

Hi all, I'm Initializing the Local and IO APIC for a propeitary operating system running in Virtualized Environment . Im facing some problem with qemu-kvm but the code runs fine with qemu. when i run my kernel image with qemu-kvm it gives emulation error failure trying to execute the code outside ROM or RAM at fec00000(IO APIC base address) but the same code runs fine with qemu. can

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. _mask_and_ack_8259A_irq()

The VMCS includes controls that enable the virtualization of interrupts and the Advanced Programmable Interrupt Controller (APIC). When these controls are used, the processor will emulate many accesses to the APIC, track the state of the virtual APIC, and deliver virtual interrupts - all in VMX non-root operation without a VM exit. You can refer to Chapter 29 of the latest SDM. This series of

I have a lot of this errors in my Centos stock 4.3 version in an Intel D945gnt motherboard with a Pentium D (dual core) and kernel 2.6.9-34.ELsmp If I disable apic in the grub.conf (apic=off) will I get a performance hit? Im running Asterisk on that machine. 40 is Received Illegal Vector 20 is Send Illegal Vector 60 means you're getting both errors at the same time. Basically it means that

I have a lot of this errors in my Centos stock 4.3 version in an Intel D945gnt motherboard with a Pentium D (dual core) If I disable apic in the grub.conf (apic=off) will I get a performance hit? Im running Asterisk on that machine. 40 is Received Illegal Vector 20 is Send Illegal Vector 60 means you're getting both errors at the same time. Basically it means that the APIC bus messages are

On Sun, Sep 6, 2020 at 8:52 PM Marc MERLIN <marc_nouveau at merlins.org> wrote: > > Ok, I have an update to this problem. I added the nouveau list because > I can't quite tell if the issue is: > - the PCIe changes that went in 5.6 I think (or 5.5?), referenced below > > - a new issue with thunderbold on thinkpad P73, that seems to be > triggered if I have a USB-C

Hi All, I am trying to run a RTOS as a guest on a OMAP5432 evm and am seeing a spurious interrupt problem when programming the virtual timer interrupts. My RTOS test case uses the A15 Virtual timer to create a timer instance. Once programmed, the virtual timer interrupt is injected into my guest's virtual CPU interface as expected and the interrupt is also forwarded to my guest. At this

Move APIC read / write accessors to sub-arch layer. Note that we don't bother to implement apic_write_atomic any different, as it is only present to work around old processor erratums (Pentium Processor Spec update 11AP), and VMI kernels do not offer support for this class of processor. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Daniel Arai <arai@vmware.com>

Move APIC read / write accessors to sub-arch layer. Note that we don't bother to implement apic_write_atomic any different, as it is only present to work around old processor erratums (Pentium Processor Spec update 11AP), and VMI kernels do not offer support for this class of processor. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Daniel Arai <arai@vmware.com>

On Mon, Sep 7, 2020 at 10:58 PM Marc MERLIN <marc_nouveau at merlins.org> wrote: > > On Mon, Sep 07, 2020 at 09:14:03PM +0200, Karol Herbst wrote: > > > - changes in the nouveau driver. Mika told me the PCIe regression > > > "pcieport 0000:00:01.0: PME: Spurious native interrupt!" is supposed > > > to be fixed in 5.8, but I still get a 4mn hang

Hello all- I have a Digium TE410P in an HP DL145 G2 dual processor server that generates well over 100,000 interrupts per second (sometimes I?ve counted 160,000+ per second) generally resulting in either the system becoming swamped and unusable or the kernel disabling the IRQ the TE410P is on resulting in the spans on that card being unusable. I have confirmed that the card is good by placing it

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information

Running FreeBSD 8.3 -- and updating sources on a daily base and building everything -- I found a new APIC/ACPI problem introduced in the past week. I have a Toshiba Satellite U205 with an Intel Core Duo (not a Core 2). It used to work fine with both cores but then sometime in on the road to BSD 8.0 the machine began hanging. So I added to /boot/loader.conf hint.apic.0.disabled="1"

Christian, the question for you is towards the end... On 09/10/2015 15:39, Denis V. Lunev wrote: > diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c > index 62cf8c9..15c3c02 100644 > --- a/arch/x86/kvm/hyperv.c > +++ b/arch/x86/kvm/hyperv.c > @@ -23,13 +23,265 @@ > > #include "x86.h" > #include "lapic.h" > +#include "ioapic.h"

Christian, the question for you is towards the end... On 09/10/2015 15:39, Denis V. Lunev wrote: > diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c > index 62cf8c9..15c3c02 100644 > --- a/arch/x86/kvm/hyperv.c > +++ b/arch/x86/kvm/hyperv.c > @@ -23,13 +23,265 @@ > > #include "x86.h" > #include "lapic.h" > +#include "ioapic.h"

Hi, Here is the patch fixing crash when apic=debug is used and APIC is not properly initialized. This issue appears during Xen Dom0 kernel boot (git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git, xen/stable-2.6.32.x head), however I think that patch is rather generic and should be applied to mainline kernel (it applies to Linux Kernel Ver. 2.6.35 and Ver. 2.6.32.19 with small fuzz).

On Mon, Sep 07, 2020 at 05:29:35PM -0700, Marc MERLIN wrote: > On Tue, Sep 08, 2020 at 01:51:19AM +0200, Karol Herbst wrote: > > oh, I somehow missed that "disp ctor failed" message. I think that > > might explain why things are a bit hanging. From the top of my head I > > am not sure if that's something known or something new. But just in > > case I CCed