From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] ehci/uhci interrupts
Date: Fri, 2 May 2014 11:26:35 -0400 [thread overview]
Message-ID: <cc8299f61d4bb42cdff9112af57eeacb@brasstown.quanstro.net> (raw)
it appears that uhci is causing spurious ehci interrupts, or at least
ehci/uhci are causing each other to ring. i haven't tracked down
the fundamental issue yet. but this appears to be related to the
ehci/uhci subordinate issue, and the Callmine setting.
hacking details for the interested:
when i limit one particular machine to 5 uhci controllers, everything
is fine. one suspects that this is luck due to whatever it is that triggers
the excitement being connected to the 6th controller. the 6th controller
does indeed share an interrupt with ehci. if it were enabled it would be
70.1/10.
(nix uses vector.mach notation for /dev/irqalloc. since the amd64
port of the nix kernel has settled on physical interrupt addressing,
a machine may have nmach*nvector available vectors.)
juno# grep usb /dev/irqalloc
68.0 15 0 0 ioapic usbuhci
68.1 7 0 0 ioapic usbuhci
68.2 11 0 0 ioapic usbuhci
68.2 11 0 0 ioapic usbuhci
> 68.3 6 2 11136 ioapic usbehci
> 68.3 6 0 0 ioapic usbuhci
70.1 10 0 0 ioapic usbehci
- erik
next reply other threads:[~2014-05-02 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 15:26 erik quanstrom [this message]
2014-05-02 18:34 ` erik quanstrom
2014-05-03 5:14 ` lucio
2014-05-03 9:42 ` tlaronde
2014-05-03 19:45 ` erik quanstrom
2014-05-04 5:12 ` lucio
2014-05-04 10:41 ` tlaronde
2014-05-04 19:29 ` erik quanstrom
2014-05-05 10:50 ` tlaronde
2014-05-04 17:14 ` erik quanstrom
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=cc8299f61d4bb42cdff9112af57eeacb@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).