From: Oliver Neukum <oliver@neukum.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question on odd APIC behavior
Date: Thu, 15 Nov 2007 19:05:02 +0100 [thread overview]
Message-ID: <200711151905.03005.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0711151637220.19041@blysk.ds.pg.gda.pl>
Am Donnerstag 15 November 2007 schrieb Maciej W. Rozycki:
> On Thu, 15 Nov 2007, Oliver Neukum wrote:
> > I am seeing an interrupt for an UHCI on #20 CPU1 also arriving on
> > #19 CPU0, triggering the spurious interrupt detection.
>
> Well, if you see spurious interrupt detection triggered, then it is not a
> problem with the interrupt being delivered multiple times (that's handled
> silently by the interrupt dispatched), but likely the interrupt line being
> deasserted too late. Does it happen frequently? If your ERR counter in
> /proc/interrupts increments quite fast, then perhaps a driver does not
> handle interrupts well enough for your system. Or there is noise on an
> interrupt line.
>
> You would have to provide more information to get more accurate feedback.
On irq 20, there's an UHCI, on irq 19 is an EHCI. For every interrupt on 20
there's a spurious interrupt on 19. USB devices on bus of the controller on 20
work. So I know all interrupts are seen. ERR does not increase. Interrupts
for devices on the bus of the controller on 19 arrive at 19 only.
As far as I can determine there are really interrupts on both CPUs on
different vectors for one physical interrupt request.
Regards
Oliver
next prev parent reply other threads:[~2007-11-15 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 23:54 Oliver Neukum
2007-11-15 13:16 ` Maciej W. Rozycki
2007-11-15 15:27 ` Oliver Neukum
2007-11-15 16:44 ` Maciej W. Rozycki
2007-11-15 18:05 ` Oliver Neukum [this message]
2007-11-16 10:02 ` Maciej W. Rozycki
2007-11-16 11:03 ` Oliver Neukum
2007-11-16 11:20 ` Maciej W. Rozycki
2007-11-16 21:34 ` Oliver Neukum
2007-11-19 15:09 ` Maciej W. Rozycki
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=200711151905.03005.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®