From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: Simon Derr <Simon.Derr-6ktuUTfB/bM@public.gmane.org>
Cc: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] fix(Fix _STA checking in acpi_bus_add)
Date: Wed, 28 Apr 2004 09:34:26 -0600 [thread overview]
Message-ID: <200404280934.26381.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <Pine.A41.4.53.0404281637220.37100-uSTK/MBzOD2tas8oWxsmKKkcovwApn/9@public.gmane.org>
On Wednesday 28 April 2004 8:53 am, Simon Derr wrote:
> On Wed, 28 Apr 2004, Matthew Wilcox wrote:
>
> > Sounds like you have a bug. Why does your firmware not report that the
> > device is present?
> >
> Yes there is very probably some firmware bug involved, and as a matter of
> fact we happen to have a 16-way system where the 0xff bus is visible even
> with recent kernels.
Is your box based on Intel chipsets and/or firmware? You might be
suffering from the problem I described here:
https://sourceforge.net/mailarchive/message.php?msg_id=6923358
Intel firmware seems to describe the PCI root bridge where chipset
configuration space lives with _STA==0x8. The spec says this means
"functional, but not present". The current Linux code ignores things
that are "not present".
Nobody cared enough to do anything about this issue at the time, so
it is still broken. I did raise the issue with our ACPI representative,
but I don't know what happened. I'd like to see some clarification in
the spec.
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next prev parent reply other threads:[~2004-04-28 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 14:18 [PATCH] fix(Fix _STA checking in acpi_bus_add) Simon Derr
[not found] ` <Pine.LNX.4.58.0404281525160.30907-64bZMsc4qGVEtYaxpPmRp1aPQRlvutdw@public.gmane.org>
2004-04-28 14:25 ` Matthew Wilcox
[not found] ` <20040428142557.GB22558-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-04-28 14:53 ` Simon Derr
[not found] ` <Pine.A41.4.53.0404281637220.37100-uSTK/MBzOD2tas8oWxsmKKkcovwApn/9@public.gmane.org>
2004-04-28 15:34 ` Bjorn Helgaas [this message]
[not found] ` <200404280934.26381.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-04-29 8:18 ` Simon Derr
[not found] ` <Pine.A41.4.53.0404291005470.37100-uSTK/MBzOD2tas8oWxsmKKkcovwApn/9@public.gmane.org>
2004-04-29 14:46 ` Bjorn Helgaas
[not found] ` <200404290846.41647.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-04-29 18:49 ` Bruno Ducrot
2004-05-12 4:40 ` Len Brown
[not found] ` <1084336805.12353.143.camel-D2Zvc0uNKG8@public.gmane.org>
2004-05-12 21:49 ` Len Brown
[not found] ` <1084398577.12352.186.camel-D2Zvc0uNKG8@public.gmane.org>
2004-05-12 21:54 ` Bjorn Helgaas
2004-04-29 8:44 ` Bruno Ducrot
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 15:10 Yu, Luming
2004-05-12 22:07 Moore, Robert
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=200404280934.26381.bjorn.helgaas@hp.com \
--to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
--cc=Simon.Derr-6ktuUTfB/bM@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=willy-8fiUuRrzOP0dnm+yROfE0A@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