From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] 1/4 multi-ioport space support for 2.5
Date: Fri, 09 May 2003 23:31:29 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705714@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705599@msgid-missing>
Oops, some more info: I missed the following boot-time error messages:
PCI: Probing PCI hardware on bus (00:00)
alloc 0x3b0-0x3df from PCI IO for PCI Bus 00:00 failed
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Root Bridge [PCI1] (00:01)
PCI: Probing PCI hardware on bus (00:01)
alloc 0x0-0x0 from PCI IO for PCI Bus 00:01 failed
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
ACPI: PCI Root Bridge [PCI2] (00:02)
PCI: Probing PCI hardware on bus (00:02)
alloc 0x2000-0x2fff from PCI IO for PCI Bus 00:02 failed
alloc 0x0-0x0 from PCI mem for PCI Bus 00:02 failed
alloc 0x0-0x0 from PCI IO for PCI Bus 00:02 failed
ACPI: PCI Interrupt Routing Table [\_SB_.PCI2._PRT]
ACPI: PCI Root Bridge [PCI3] (00:03)
PCI: Probing PCI hardware on bus (00:03)
alloc 0xa0000-0xfffff from PCI mem for PCI Bus 00:03 failed
alloc 0x3b0-0x3df from PCI IO for PCI Bus 00:03 failed
Maybe it isn't a firmware problem, after all.
--david
next prev parent reply other threads:[~2003-05-09 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 22:25 [Linux-ia64] [PATCH] 1/4 multi-ioport space support for 2.5 Bjorn Helgaas
2003-04-24 22:37 ` Jesse Barnes
2003-04-25 0:44 ` Bjorn Helgaas
2003-04-25 1:05 ` Jesse Barnes
2003-04-25 11:36 ` Matthew Wilcox
2003-04-25 16:13 ` Bjorn Helgaas
2003-04-25 17:18 ` Jesse Barnes
2003-05-09 23:20 ` David Mosberger
2003-05-09 23:31 ` David Mosberger [this message]
2003-05-12 20:58 ` Bjorn Helgaas
2003-05-12 22:50 ` David Mosberger
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=marc-linux-ia64-105590723705714@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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 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.