All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI PCI routing problem
Date: Fri, 11 Jul 2003 17:23:45 +0100	[thread overview]
Message-ID: <200307111723.45272.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030711140227.GF22636-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>


> > Yeah, I can easily make it work by turning it off or supplying
> > pci=noacpi. However, I'm pursuing this problem to develop a fix for the
> > issue.
> >
> > The new ACPI PCI routing seems to cause other people problems as well..
> > I've seen mention on various web pages. Not really a good situation to
> > leave these problems in the OS.
>
> Forgot to say: have you also the same kind of output, but
> with ACPI?  If all (at least the 15 first one) look like XT-PIC...

Yeah, its pretty much the same, although it says IO-APIC instead of XT-PIC.

If I don't use pci=noacpi, I get the problem I'm describing (obviously), with 
IRQs 21 etc mentioned.
If I use pci=noacpi, it also says IO-APIC, but it only has 16 IRQs total.

(I can't remember the _exact_ word it uses offhand.. something like 
IO-APIC-edge I think)




-------------------------------------------------------
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

  parent reply	other threads:[~2003-07-11 16:23 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
     [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 [this message]
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=200307111723.45272.adq_dvb@lidskialf.net \
    --to=adq_dvb-fmpxvn3awwjajazl26g0sa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.