From: Josh McKinney <forming@charter.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [ACPI] acpi problem with nforce motherboards and ethernet
Date: Sat, 7 Feb 2004 01:39:06 -0500 [thread overview]
Message-ID: <20040207063906.GA2188@forming> (raw)
In-Reply-To: <20040207035018.33ce01dc.ak@suse.de>
On approximately Sat, Feb 07, 2004 at 03:50:18AM +0100, Andi Kleen wrote:
> On Sat, 7 Feb 2004 00:33:04 +0100 (CET)
> "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:
>
>
> > That's not the right fix. There's a bug in Linux's ACPI IRQ setup as
> > I've discovered by comparing the code to the spec. Here's a patch I sent
> > in December both to the LKML and the ACPI maintainer. The feedback from
> > the list was positive, but the maintainer didn't bother to comment.
>
> Thanks. I added the patch to the x86-64 sources and it indeed seems to fix
> the Nforce3.
>
I tried the patch against 2.6.3-rc1 and it doesn't seem to fix
anything, timer is still on XT-PIC. This is on a A7N8X Deluxe rev2,
nforce2.
CPU0
0: 524366 XT-PIC timer
1: 1727 IO-APIC-edge i8042
2: 0 XT-PIC cascade
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
14: 913 IO-APIC-edge ide0
15: 22792 IO-APIC-edge ide1
19: 23559 IO-APIC-level nvidia
20: 52452 IO-APIC-level ohci_hcd, eth0
21: 0 IO-APIC-level ehci_hcd, NVidia nForce2
22: 354 IO-APIC-level ohci_hcd
NMI: 0
LOC: 524223
ERR: 0
MIS: 0
--
Josh McKinney | Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
| They that can give up essential liberty
Linux, the choice -o) | to obtain a little temporary safety deserve
of the GNU generation /\ | neither liberty or safety.
_\_v | -Benjamin Franklin
next prev parent reply other threads:[~2004-02-07 6:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 19:25 [ACPI] acpi problem with nforce motherboards and ethernet Luis Miguel García
2004-02-05 19:44 ` David Ford
2004-02-05 21:27 ` Luis Miguel García
2004-02-05 23:40 ` Andrew Morton
2004-02-06 0:08 ` Prakash K. Cheemplavam
2004-02-06 0:14 ` Craig Bradney
2004-02-06 0:22 ` Luis Miguel García
2004-02-06 0:38 ` Prakash K. Cheemplavam
2004-02-06 0:46 ` Luis Miguel García
2004-02-06 0:58 ` Prakash K. Cheemplavam
2004-02-06 1:01 ` Craig Bradney
2004-02-06 1:09 ` Luis Miguel García
2004-02-06 9:28 ` Prakash K. Cheemplavam
2004-02-06 9:26 ` Prakash K. Cheemplavam
2004-02-06 10:07 ` Craig Bradney
2004-02-06 10:40 ` Prakash K. Cheemplavam
2004-02-06 9:44 ` Daniel Drake
2004-02-06 11:04 ` Prakash K. Cheemplavam
2004-02-06 11:15 ` Prakash K. Cheemplavam
2004-02-06 12:51 ` Craig Bradney
2004-02-06 13:10 ` Arjen Verweij
2004-02-06 13:20 ` Prakash K. Cheemplavam
2004-02-06 13:34 ` Arjen Verweij
2004-02-06 13:41 ` Prakash K. Cheemplavam
2004-02-06 13:43 ` Prakash K. Cheemplavam
2004-02-06 11:08 ` Craig Bradney
2004-02-06 0:59 ` Craig Bradney
2004-02-06 0:56 ` Craig Bradney
2004-02-06 23:33 ` Maciej W. Rozycki
2004-02-07 2:50 ` Andi Kleen
2004-02-07 6:39 ` Josh McKinney [this message]
2004-02-07 10:04 ` Maciej W. Rozycki
2004-02-07 6:29 ` Luis Miguel García
2004-02-06 9:47 ` Daniel Drake
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 17:41 Luis Miguel García
2004-02-05 18:41 ` [ACPI] " Arjen Verweij
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=20040207063906.GA2188@forming \
--to=forming@charter.net \
--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