From: John R Lenton <john@grulic.org.ar>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: different IRQ settings for different MPS settings?
Date: Tue, 6 Feb 2001 05:46:47 -0300 [thread overview]
Message-ID: <20010206054647.C692@grulic.org.ar> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1337 bytes --]
With a MPS setting of 1.4 USB doesn't work on me; it timeouts,
constantly. With MPS setting of 1.1 everything is OK.
a dirty diff of lspci -vvvxx gives
62c62
< Interrupt: pin D routed to IRQ 5
---
> Interrupt: pin D routed to IRQ 19
77c77
< Interrupt: pin D routed to IRQ 5
---
> Interrupt: pin D routed to IRQ 19
103c103
< Interrupt: pin A routed to IRQ 11
---
> Interrupt: pin A routed to IRQ 18
124c124
< Interrupt: pin A routed to IRQ 5
---
> Interrupt: pin A routed to IRQ 19
140c140
< Interrupt: pin A routed to IRQ 10
---
> Interrupt: pin A routed to IRQ 16
157c157
< Interrupt: pin A routed to IRQ 12
---
> Interrupt: pin A routed to IRQ 17
186c186
< Interrupt: pin A routed to IRQ 10
---
> Interrupt: pin A routed to IRQ 16
(I've attached both lspci -vvvxx's, so you can diff -u that if
you want).
My question(s) is(are) is this a known bug, is this correct
behaviour, am I missing something, and why is USB the only
subsystem affected.
Phew.
--
John Lenton (john@grulic.org.ar) -- Random fortune:
Se Deus é amor e o amor é cego, Ray Charles é Deus?
[-- Attachment #2: lspci_mps1.1.gz --]
[-- Type: application/octet-stream, Size: 2091 bytes --]
[-- Attachment #3: lspci_mps1.4.gz --]
[-- Type: application/octet-stream, Size: 2091 bytes --]
next reply other threads:[~2001-02-06 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 8:46 John R Lenton [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-07 16:32 different IRQ settings for different MPS settings? Dunlap, Randy
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=20010206054647.C692@grulic.org.ar \
--to=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.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