From: "DPR" <info-IGm5bqYn3xwb1SvskN2V4Q@public.gmane.org>
To: "'Cagle,
John (ISS-Houston)'" <john.cagle-VXdhtT5mjnY@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: APIC, USB mouse and errors
Date: Sat, 1 Mar 2003 03:45:48 +0100 [thread overview]
Message-ID: <000001c2df9c$ab20f030$0200a8c0@brutzler> (raw)
In-Reply-To: <C50AB9511EE59B49B2A503CB7AE1ABD10440E418-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
Hi John,
YOU GOT IT - GREAT JOB !!!
I made an ugly but working hack in "mp_config_acpi_legacy_irqs" - I simply forced the trigger
mode to "level" for my USB-IRQs. And now everything works fine !!! If you find another way to
fix it - let me know ;)
Besides, do you know why the high IRQs (>17) are not used at all ? I'm just wondering why M$
Windows produces such a different IRQ-mapping - take a look at the attached file (IRQs
0,1,4,6,8,9,13,15-19,21,23 are used).
Thanks for your professional help,
HOLGER
> Holger,
>
> I think that your APIC IRQs (0..15) aren't getting programmed
> properly.
>
> PCI is using IRQs 10, 11, 12 & 14, but I think the kernel has made an
> incorrect assumption that these are ISA IRQs and set them to be
> edge-triggered. PCI IRQs are always level-triggered.
>
> Take a look at arch/i386/kernel/mpparse.c in the
> mp_config_acpi_legacy_irqs() routine. It sets interrupts
> 0..15 to ISA
> bus conforming behavior (edge).
>
> You might try forcing the kernel to do the right thing and see what
> happens.
>
> Regards,
> John
[-- Attachment #2: I-O APIC.txt --]
[-- Type: text/plain, Size: 3245 bytes --]
I/O APIC
--------------------------------------------------------------------------------
APIC ID : 2
Implementation Version : 3
Arbitration ID : 1
Base Address : FEC00000h
IRQ Assertion Register : Supported
+--------+-------------+----------+----------+---------+--------+----------------------------------+
| APIC | Interrupt | Delivery | Polarity | Trigger | Remote | Destination |
| INTIN# | Vector | Mode | Active- | Mode | IRR | |
+--------+-------------+----------+----------+---------+--------+----------------------------------+
| 00h | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 01h | 93h | Lowest | High | Level | 0 | Processors = 0 |
| 02h | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 03h | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 04h | 92h | Lowest | High | Level | 0 | Processors = 0 |
| 05h | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 06h | B3h (Masked)| Lowest | High | Level | 0 | Processors = 0 |
| 07h | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 08h | D1h | Fixed | High | Level | 0 | Processors = 0 |
| 09h | B1h | Lowest | Low | Edge | 0 | Processors = 0 |
| 0Ah | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 0Bh | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 0Ch | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 0Dh | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 0Eh | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 0Fh | 82h | Lowest | High | Level | 0 | Processors = 0 |
| 10h | 63h | Lowest | Low | Edge | 0 | Processors = 0 |
| 11h | 73h | Lowest | Low | Edge | 0 | Processors = 0 |
| 12h | B4h | Lowest | Low | Edge | 0 | Processors = 0 |
| 13h | 83h | Lowest | Low | Edge | 0 | Processors = 0 |
| 14h | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 15h | A4h | Lowest | Low | Edge | 0 | Processors = 0 |
| 16h | FFh (Masked)| Fixed | High | Level | 0 | APIC ID = 0 |
| 17h | 94h | Lowest | Low | Edge | 0 | Processors = 0 |
+--------+-------------+----------+----------+---------+--------+----------------------------------+
next prev parent reply other threads:[~2003-03-01 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 23:47 APIC, USB mouse and errors Cagle, John (ISS-Houston)
[not found] ` <C50AB9511EE59B49B2A503CB7AE1ABD10440E418-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
2003-03-01 2:45 ` DPR [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-27 13:39 Cagle, John (ISS-Houston)
[not found] ` <C50AB9511EE59B49B2A503CB7AE1ABD10476BF94-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
2003-02-27 15:22 ` DPR
2003-02-28 22:47 ` DPR
2003-02-27 13:13 DPR
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='000001c2df9c$ab20f030$0200a8c0@brutzler' \
--to=info-igm5bqyn3xwb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=john.cagle-VXdhtT5mjnY@public.gmane.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