I2c producing crazy console messages [[Re: insanely-high interrupt rates -- PARTIAL resolution (Pi2)]]

[Ian Lepore]

On Thu, 2019-04-18 at 16:51 -0500, Karl Denninger wrote:
> Up until 12.0 this code both worked and did *not* generate complaints
> about unhandled interrupts.  It still runs fine and returns valid
> data
> BUT if there are any analog endpoints actually on the bus that the
> code
> can read then it generates a lot of these:
> 
> local_intc0: Spurious interrupt detected
> local_intc0: Spurious interrupt detected
> intc0: Spurious interrupt detected
> 
> .....
> 
> If I do not connect the I2c device then there are no messages.  If I
> stop the code that is running (e.g. no accesses to the i2c bus) then
> the
> messages stop as well, so it's not something that happens but remains
> active after the code halts; it's happening on the actual accesses to
> the bus from those ioctl's.

Hmm, another interesting question occurred to me:  Can you tell whether
you are getting multiple spurious interrupt messages per single
transfer your code does, or is it one per transfer, or more
intermittent, like not on every transfer?

-- Ian