Hi Thomas,
Do you have some news about this issue?
Thanks,
Michael.
> -----Original Message-----
> From: Thomas Gleixner [mailto:tglx@xxxxxxxxxxxxx]
> Sent: Thursday, November 8, 2018 2:39 PM
> To: Holger Schurig <holgerschurig@xxxxxxxxx>
> Cc: Michael Shych <michaelsh@xxxxxxxxxxxx>; x86@xxxxxxxxxx; Vadim
> Pasternak <vadimp@xxxxxxxxxxxx>; Ido Schimmel
> <idosch@xxxxxxxxxxxx>; Ohad Oz <ohado@xxxxxxxxxxxx>; Greg KH
> <gregkh@xxxxxxxxxxxxxxxxxxx>; linux-serial@xxxxxxxxxxxxxxx
> Subject: Re: "No irq handler for vector" problem
>
> Holger,
>
> On Thu, 8 Nov 2018, Holger Schurig wrote:
> > > Yet another thing which would be interesting. Load the i915 module and
> run
> > > the userland graphics stack. Open the serial port for read, which should
> > > not result in any interrupts. Check /proc/interrupts for the number of
> > > interrupts for the serial port,
> >
> > Hmm, the 8250 driver will generate one interrupt even when just reading.
>
> the one is ok. That's an initial TX empty or state change. Nothing to worry
> about.
>
> > > wait 10 seconds and check again. In theory the numbers should be the
> > > same. My crystal ball tells me they are not.
> > What I'm wondering is about the massive number of ERR interrupts ...
> >
> > root@test:~# while sleep 1; do grep ERR: /proc/interrupts ; done
> > ERR: 25786
> > ERR: 25809
> > ERR: 25837
> > ERR: 25861
> > ERR: 25890
> > ERR: 25912
> > ^C
> >
> > This is specific to nolapic=1, with "noapic=1" the ERR interrupt number
> > stays at 51. But I guess this is a red herring, too, because who runs
> > his box with nolapic=1 in the first place :-)
>
> Could you do the same test without nolapic please?
>
> Thanks,
>
> tglx
