From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI PCI routing problem
Date: Fri, 11 Jul 2003 12:14:41 +0200 [thread overview]
Message-ID: <20030711101441.GO7796@poupinou.org> (raw)
In-Reply-To: <200307110022.29512.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
On Fri, Jul 11, 2003 at 12:22:29AM +0100, Andrew de Quincey wrote:
> Hi, I have an Epox 8RDA+ NForce2-based motherboard (uniprocessor, Athlon XP).
> This board has an IO-APIC with 0x17 pins. I can't tell you much more specific
> about it, as it is in the nforce2 chipset to which I do not have docs. I'm
> using kernel 2.5.74, with APIC, IO-APIC, ACPI turned on.
>
> First of all, here are the symptoms:
>
> Kernel boots OK, devices with IRQs <=15 are fine. However, the system attempts
> to allocate some devices (e.g. USB) to IRQs 20 and 21, as told by the AML
> code in my BIOS (more on this later).
>
How look /proc/interrupts with IO-APIC, but without ACPI (I mean, no
acpi at all at compile time)?
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
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 prev parent reply other threads:[~2003-07-11 10:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 23:22 ACPI PCI routing problem Andrew de Quincey
[not found] ` <200307110022.29512.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-11 0:14 ` Andrew de Quincey
2003-07-11 10:14 ` Ducrot Bruno [this message]
[not found] ` <20030711101441.GO7796-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-07-11 11:43 ` Andrew de Quincey
[not found] ` <200307111243.34695.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-11 12:51 ` Ducrot Bruno
[not found] ` <20030711125126.GA22636-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-07-11 12:56 ` Andrew de Quincey
[not found] ` <200307111356.22376.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-11 14:02 ` Ducrot Bruno
[not found] ` <20030711140227.GF22636-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-07-11 16:23 ` Andrew de Quincey
2003-07-11 17:06 ` Instability without ACPI Andrew de Quincey
[not found] ` <200307111806.57883.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-11 17:26 ` Ducrot Bruno
[not found] ` <20030711172639.GL22636-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-07-11 18:17 ` Sérgio Monteiro Basto
[not found] ` <1057947446.1451.51.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-07-11 18:46 ` Ducrot Bruno
[not found] ` <20030711184648.GN22636-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-07-12 3:25 ` Instability without ACPI and quirks Sérgio Monteiro Basto
[not found] ` <1057980324.1470.61.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-07-12 12:39 ` Andrew de Quincey
2003-07-11 14:09 ` ACPI PCI routing problem Alan Cox
[not found] ` <1057932596.20629.0.camel-2MMpYkNvuYAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-07-11 16:29 ` 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=20030711101441.GO7796@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=adq_dvb-fmPXVN3awWJAJAzL26g0SA@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