From: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Possible quick fix for ACPI routing problem on Nforce2
Date: Sun, 13 Jul 2003 02:18:44 +0100 [thread overview]
Message-ID: <200307130218.44398.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <200307122352.45704.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Hi, I've been playing about with this, and I've found what is happening.
I've not yet tracked down the reason yet, but if anyone else has this
problem, can they try please this fix to see if it is consistent.
Anyway, IRQs > 15 get set to Active low/Level Sensitive in the IO-APIC on
my board.
The fix (No patch as this is NOT a proper fix):
Edit arch/i386/kernel/io_apic.c
Find the function io_apic_set_pci_routing() (its the last one in 2.5.74).
Change the line:
entry.polarity = 1; /* Low active */
To:
entry.polarity = 0; /* High active */
For me, this makes everything work fine. Originally, I also forced these
IRQs to be edge sensitive, but leaving them at level seems to work fine as
well.
Now, I assume one of the other functions in io_apic.c is _meant_ to be
called to set this correctly. My next step is to track down why this is not
occurring.
A question: Why are these set to level/activelow in a function which is
labelled to be setting up PCI IRQs? I'd assumed they were always
edge/active high.. or is this not necessarily the case?
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
next parent reply other threads:[~2003-07-13 1:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200307122352.45704.adq_dvb@lidskialf.net>
[not found] ` <200307122352.45704.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-13 1:18 ` Andrew de Quincey [this message]
[not found] ` <200307130218.44398.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-13 5:39 ` Re: Possible quick fix for ACPI routing problem on Nforce2 Jurriaan
[not found] ` <20030713053913.GB1284-4cpIIuwL6H0O5nXqB3HebLNAH6kLmebB@public.gmane.org>
2003-07-13 16:52 ` Andrew de Quincey
2003-07-13 19:35 ` Andrew de Quincey
2003-07-13 23:51 ` Andrew de Quincey
[not found] ` <200307140051.29231.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-14 1:08 ` Located the problem with the VIA KT400 board Andrew de Quincey
[not found] ` <200307140208.07975.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-14 15:32 ` hgfelger-9nAOAgdJVo4b1SvskN2V4Q
[not found] ` <Pine.LNX.4.33.0307141730001.1166-100000-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2003-07-14 15:53 ` Andrew de Quincey
2003-07-13 9:19 ` Re: Possible quick fix for ACPI routing problem on Nforce2 liste-9nAOAgdJVo4b1SvskN2V4Q
[not found] ` <Pine.LNX.4.33.0307131118210.561-100000-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2003-07-13 13:11 ` Andrew de Quincey
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=200307130218.44398.adq_dvb@lidskialf.net \
--to=adq_dvb-fmpxvn3awwjajazl26g0sa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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