From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: Michael Thonke <iogl64nx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Li,
Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Nguyen,
Tom L" <tom.l.nguyen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI List
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Fw: Re: 2.6.12-rc2-mm2
Date: Tue, 12 Apr 2005 10:17:13 -0600 [thread overview]
Message-ID: <1113322633.17684.23.camel@eeyore> (raw)
In-Reply-To: <425AA4C1.6050609-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Mon, 2005-04-11 at 18:24 +0200, Michael Thonke wrote:
> It first consider that no bus supports ACPI, but than it say ACPI supported.
> Maybe I interpret it in the wrong way. I hope you will/can fnd what is
> wrong.
> ...
> This message 1st spotted over the screen:
> ACPI: No ACPI bus support for 00:00
> ACPI: No ACPI bus support for 00:01
> ACPI: No ACPI bus support for 00:02
> ACPI: No ACPI bus support for 00:03
> ACPI: No ACPI bus support for 00:04
> ACPI: No ACPI bus support for 00:05
> ACPI: No ACPI bus support for 00:06
> ACPI: No ACPI bus support for 00:07
> ACPI: No ACPI bus support for 00:08
> ACPI: No ACPI bus support for 00:09
> ACPI: No ACPI bus support for 00:0a
> ACPI: No ACPI bus support for 00:0b
>
> And then for each pcie port:
> ACPI: No ACPI bus support for pcie00-03
The messages above are harmless, so you can ignore them.
ACPI is in fact supported and working in spite of these
messages.
> After that this appears:
> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 201
> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 201
> ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 217
These messages are perfectly normal.
Apart from the messages, what is actually broken? Is there a device
that is not functional? Which one?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-04-12 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 3:04 Fw: Re: 2.6.12-rc2-mm2 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD30575019C29C7-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-04-11 16:24 ` Michael Thonke
[not found] ` <425AA4C1.6050609-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2005-04-12 16:17 ` Bjorn Helgaas [this message]
2005-04-12 20:43 ` Michael Thonke
[not found] ` <425C330B.9000806-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2005-04-12 21:12 ` Bjorn Helgaas
2005-04-18 15:41 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2005-04-11 17:53 Nguyen, Tom L
2005-04-08 23:45 Andrew Morton
2005-04-08 16:29 Andrew Morton
[not found] ` <20050408092947.41175d63.akpm-3NddpPZAyC0@public.gmane.org>
2005-04-08 21:16 ` Bjorn Helgaas
2005-04-08 22:37 ` Michael Thonke
[not found] ` <425707A2.2050208-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2005-04-09 3:20 ` Len Brown
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=1113322633.17684.23.camel@eeyore \
--to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=iogl64nx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=tom.l.nguyen-ral2JQCrhuEAvxtiuMwx3w@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