All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Manfred <manfred@student.ethz.ch>
Cc: linux-omap@vger.kernel.org
Subject: Re: linux-omap3-2.6.39: spurious irq 95, during heavy SD card load
Date: Thu, 3 Nov 2011 12:37:32 -0700	[thread overview]
Message-ID: <20111103193732.GY31337@atomide.com> (raw)
In-Reply-To: <loom.20111103T103055-675@post.gmane.org>

* Manfred <manfred@student.ethz.ch> [111103 02:15]:
> Dear users/developers, 
> 
> I am trying to install the xenomai real-time linux on a gumstix overo fire with
> an omap3530. 
> After some starting problems, I succeed to patch the 2.6.33 kernel and run some
> latency tests
>  with normal worst case latencies ~60us. However, the overall worst case latency
> is very bad (5ms), 
> because i occasionally get spurious interrupt errors like this:
> Spurious irq 95: 0xffffffdf, please flush posted write for irq 86
> Spurious irq 95: 0xffffffdf, please flush posted write for irq 86
...

> Or is there a specific patch to resolve this?
> I was not able to reproduce this on the NAND-flash, 
> but it is also to small to make large continous data transfers. 

What the warnings mean is that the ack for irq86 did not reach
the hardware before that interrupt got unmasked again.

To fix this, find the irq handler for irq86, and add a readback
of the interrupt status register or revision register to the
interrupt handler right after the write acking the interrupt.

To see some examples, please do:

$ grep -ri "flush posted write" drivers/

Regards,

Tony

      reply	other threads:[~2011-11-03 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03  9:46 linux-omap3-2.6.39: spurious irq 95, during heavy SD card load Manfred
2011-11-03 19:37 ` Tony Lindgren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111103193732.GY31337@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=manfred@student.ethz.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.