Re: "No irq handler for vector" problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 25 Jun 2019, Gleixner, Thomas wrote:

>
> The thing is that the interrupt is in edge mode which my tried brain did
> not notice yesterday evening.
>
> In edge mode the remote-irr bit meaning is undefined and as the docs are
> unclear it might eventually give the wrong answer. From a hardware view
> this makes sense because edge will just fire and forget, while level needs
> the explicit ack before sending it again (if still raised at the pin)
>
> So for edge the issue is different. The spurious interrupt is harmless as
> it does not leave stale state in the IO-APIC around.
>
> I'm working on a clean fix for both the level and the edge problems. Just
> at the point to start testing. Will post the result in a couple of hours.
>
> Thanks,
>
> 	tglx
>
>
Hmm, good point. Checking the IO-APIC datasheet again, it's clearly written.

Thanks,

Robert



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux