Spurious irq 95: 0xffffffdf, please flush posted write for irq...

Colman Lai

I got some "Spurious irq 95: 0xffffffdf, please flush posted write for irq 12", for irq 37 and for irq 94 message when I run the iperf test on a SDIO wifi attached to mmc3.

I have searched the web about this. It suggests to read back the last written device register in the interrupt handler. I have found the irq 12 is for dma.c, irq 37 is for time-gp.c and irq 94 is for omap_hsmmc.c, I try to do it but the message still reporting.

How to fix this? Can I just ignore the message?

Regards,

Colman

over 14 years ago

0 Vaibhav Hiremath over 14 years ago

TI__Expert 8180 points

With the kernel 2.6.29 I had seen similar issue and had a discussion with community on this, please refer to the mail-thread - http://permalink.gmane.org/gmane.linux.ports.arm.omap/15280

If I remember correctly, I just added extra status read in ISP-camera/DSS ISR routine to get rid of this.

Thanks,

Vaibhav

0 Vaibhav Hiremath over 14 years ago

TI__Expert 8180 points

Please refer to another thread posted by you on the same issue - http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/416/p/100963/355283.aspx#355283

Thanks,

Vaibhav

0 Colman Lai over 14 years ago in reply to Vaibhav Hiremath

Intellectual 830 points

I have already read the the post you mentioned about, I have follow it to fix for irq 56 successfully. But the same technique does not fix for irq 12, 37 and 94. These irq handlers call to an external function pointer before return from interrupt. So I cannot know what is the last written register. If I just ignore this message, what will happen? Or can you provide a exact method to fix for these irq?

Regards,

Colman

Processors

Processors forum

Spurious irq 95: 0xffffffdf, please flush posted write for irq...