public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: trooper ryan <trooper_ryan-QPf0Bz723pkjHdulDSg1yw@public.gmane.org>
Cc: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: PCI: Cannot allocate resource region 0 of device 0000:00:0d.0
Date: Sat, 24 Apr 2004 16:05:33 +0100	[thread overview]
Message-ID: <20040424150533.GL22558@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <408AF79C.1050804-QPf0Bz723pkjHdulDSg1yw@public.gmane.org>

On Sat, Apr 24, 2004 at 11:26:20PM +0000, trooper ryan wrote:
> Anyhow, the info you requested:
> # setpci -s 00:0d.0 BASE_ADDRESS_0=ffffffff
> setpci -s 00:0d.0 BASE_ADDRESS_0 returns 00d7f008 sometimes and ffffffff 
> others.

This is quite suspicious.  ffffffff would indicate this device is not
connected to the bus [1] .  The other value returned indicates it's a
32-bit BAR (entirely plausible) which is prefetchable (seems kosher for
a video capture card).  The base address would then be 0x00d7f000 which
is slightly under the 16MB boundary.  Very curious as this is normally
assigned to system RAM.

All in all, this looks like a pretty broken piece of hardware to me.
Possibly something else is going on to cause this, like the system being
over its power-budget.  I advide you to treat this as a hardware problem
and try doing some things to narrow it down, like taking all other cards
out of the machine and seeing if the problem persists; try the card in
a different slot; check the card connectors for damage, etc.

It'd also be worth trying a different OS with it, just to be sure it's
a hardware problem ;-)

[1] Due to how PCI BARs work, there must be at least one bit clear.
If it's a memory BAR, bit 0 must be clear, and if it's a port BAR, bit 1
must be 0.  If there's no reponse from a device, the PCI bus floats high,
so you get back 0xffffffff.  When you write 0xffffffff to a BAR, the device
ignores the bits that are less than the size of the aperture so when you
read it back, you should get only the implemented bits set.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297

  parent reply	other threads:[~2004-04-24 15:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-24 15:21 PCI: Cannot allocate resource region 0 of device 0000:00:0d.0 trooper ryan
     [not found] ` <408A85DE.8090700-QPf0Bz723pkjHdulDSg1yw@public.gmane.org>
2004-04-24 12:57   ` Matthew Wilcox
     [not found]     ` <20040424125753.GJ22558-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-04-24 23:26       ` trooper ryan
     [not found]         ` <408AF79C.1050804-QPf0Bz723pkjHdulDSg1yw@public.gmane.org>
2004-04-24 15:05           ` Matthew Wilcox [this message]
     [not found]             ` <20040424150533.GL22558-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-04-25 16:20               ` trooper ryan
     [not found]                 ` <408BE531.8080503-QPf0Bz723pkjHdulDSg1yw@public.gmane.org>
2004-04-25 19:13                   ` trooper ryan

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=20040424150533.GL22558@parcelfarce.linux.theplanet.co.uk \
    --to=willy-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=trooper_ryan-QPf0Bz723pkjHdulDSg1yw@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