public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-acpi@vger.kernel.org
Subject: Re: SCSI behind PCIE bridge only detected using pci=noacpi
Date: Thu, 09 Mar 2006 09:09:53 +0800	[thread overview]
Message-ID: <440F8061.7030502@intel.com> (raw)
In-Reply-To: <200603081954.44195.trenn@suse.de>

Thomas Renninger wrote:
> Should this work or is this really not supported via ACPI?
> 
> I expect this is the relevant output:
> 
> ACPI: PCI Root Bridge [PCI1] (0001:40)
> PCI: Multiple domains not supported
> ACPI Error (pci_root-0279): Bus 0001:40 not present in PCI 
> namespace<7>Losing some ticks... checking if CPU frequency changed.
> 
>  [20060127]
> ACPI Exception (pci_bind-0156): AE_NOT_FOUND, Invalid ACPI-PCI context 
> for parent device PCI1 [20060127]
> ACPI Exception (pci_bind-0156): AE_NOT_FOUND, Invalid ACPI-PCI context 
> for parent device PCI1 [20060127]
> ACPI: PCI Root Bridge [PCI2] (0002:80)
> PCI: Multiple domains not supported
> ACPI Error (pci_root-0279): Bus 0002:80 not present in PCI namespace 
> [20060127]
> ACPI Exception (pci_bind-0156): AE_NOT_FOUND, Invalid ACPI-PCI context 
> for parent device PCI2 [20060127]
> ACPI Exception (pci_bind-0156): AE_NOT_FOUND, Invalid ACPI-PCI context 
> for parent device PCI2 [20060127]
> 
> With pci=noacpi the SCSI disk/controller works fine.
> Without even the controller is not recognised.
IIRC, -mm tree has the x86 multiple domains support patch. Without that
patch all pci devices of non-zero domains can't be found.

Thanks,
Shaohua

      reply	other threads:[~2006-03-09  1:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 18:54 SCSI behind PCIE bridge only detected using pci=noacpi Thomas Renninger
2006-03-09  1:09 ` Shaohua Li [this message]

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=440F8061.7030502@intel.com \
    --to=shaohua.li@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=trenn@suse.de \
    /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