PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

[trooper ryan]

Hi,

I'm really struggling to get a Brooktree video-capture card functional 
under 2.6.5.  I think i've isolated the problem as dmesg reports:
PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

That device corresponds to the card as shown by lspci -vvv (see below).

I tried passing the option pci=noacpi at boot, but still had problems.

I'd really appreciate any suggestions as i've been trying to get this 
card functional for about two weeks.  Im so frustrated Im almost 
considering putting it in an XP box!

Thanks,
Trooper


0000:00:0d.0 Multimedia video controller: Brooktree Corporation: Unknown 
device 034e (rev 11)
         Subsystem: LeadTek Research Inc.: Unknown device 6606
         Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR+
         Latency: 32 (4000ns min, 10000ns max)
         Interrupt: pin A routed to IRQ 11
         Region 0: Memory at <ignored> (32-bit, prefetchable) [disabled]
         Capabilities: [44] <chain broken>

0000:00:0d.1 Multimedia controller: Brooktree Corporation: Unknown 
device 0858 (rev 11)
         Subsystem: LeadTek Research Inc.: Unknown device 6606
         Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR+
         Latency: 32 (1000ns min, 63750ns max)
         Interrupt: pin A routed to IRQ 11
         Region 0: Memory at <ignored> (32-bit, prefetchable) [disabled]
         Capabilities: [44] <chain broken>

0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 
630/730 PCI/AGP VGA Display Adapter (rev 21) (prog-if 00 [VGA])
         Subsystem: Asustek Computer, Inc.: Unknown device 80e1
         Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Interrupt: pin A routed to IRQ 11
         BIST result: 00
         Region 0: Memory at f0000000 (32-bit, prefetchable)
         Region 1: Memory at e9800000 (32-bit, non-prefetchable) [size=128K]
         Region 2: I/O ports at a800 [size=128]
         Capabilities: [40] Power Management version 1
                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
         Capabilities: [50] AGP version 2.0
                 Status: RQ=16 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- 
HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
                 Command: RQ=16 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- 
FW- Rate=x4


-------------------------------------------------------
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

Re: PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

[Matthew Wilcox]

On Sat, Apr 24, 2004 at 03:21:02PM +0000, trooper ryan wrote:
> I'm really struggling to get a Brooktree video-capture card functional 
> under 2.6.5.  I think i've isolated the problem as dmesg reports:
> PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

Yeah, it looks like device 0000:00:0d.0 is completely messed up.

> That device corresponds to the card as shown by lspci -vvv (see below).

Can you send lspci -s 00:0d.0 -vvvxx too?

> I'd really appreciate any suggestions as i've been trying to get this 
> card functional for about two weeks.  Im so frustrated Im almost 
> considering putting it in an XP box!

Don't be stupid.  People think that threats like these make people take
them more seriously.  It actually has the opposite effect.

> 0000:00:0d.0 Multimedia video controller: Brooktree Corporation: Unknown 
> device 034e (rev 11)
>         Subsystem: LeadTek Research Inc.: Unknown device 6606
>         Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
> >TAbort- <TAbort- <MAbort- >SERR- <PERR+
>         Latency: 32 (4000ns min, 10000ns max)
>         Interrupt: pin A routed to IRQ 11
>         Region 0: Memory at <ignored> (32-bit, prefetchable) [disabled]
>         Capabilities: [44] <chain broken>

This "chain broken" concerns me a little.  If they aren't even able to
get something as simple as PCI capabilities right, what else may they have broken?

You can use setpci to figure out how much space this device is requesting.

setpci -s 00:0d.0 BASE_ADDRESS_0=ffffffff
setpci -s 00:0d.0 BASE_ADDRESS_0

will give you back something like ffff0004 (which would correspond to
a 64k region).  Let us know what that returns.

> 0000:00:0d.1 Multimedia controller: Brooktree Corporation: Unknown 
> device 0858 (rev 11)
>         Subsystem: LeadTek Research Inc.: Unknown device 6606
>         Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
> >TAbort- <TAbort- <MAbort- >SERR- <PERR+
>         Latency: 32 (1000ns min, 63750ns max)
>         Interrupt: pin A routed to IRQ 11
>         Region 0: Memory at <ignored> (32-bit, prefetchable) [disabled]
>         Capabilities: [44] <chain broken>
> 
> 0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 
> 630/730 PCI/AGP VGA Display Adapter (rev 21) (prog-if 00 [VGA])
>         Subsystem: Asustek Computer, Inc.: Unknown device 80e1
>         Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium 
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>         Interrupt: pin A routed to IRQ 11
>         BIST result: 00
>         Region 0: Memory at f0000000 (32-bit, prefetchable)
>         Region 1: Memory at e9800000 (32-bit, non-prefetchable) [size=128K]
>         Region 2: I/O ports at a800 [size=128]
>         Capabilities: [40] Power Management version 1
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Capabilities: [50] AGP version 2.0
>                 Status: RQ=16 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- 
> HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
>                 Command: RQ=16 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- 
> FW- Rate=x4
> 
> 
> -------------------------------------------------------
> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel

-- 
"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

Re: PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

[trooper ryan]

Matthew,

Thanks for taking the time to look at the problem.  I wasn't trying to 
be threatening, just conveying my level of frustration :)

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.

# lspci -s 00:0d.0 -vvvxx
0000:00:0d.0 Multimedia video controller: Brooktree Corporation: Unknown 
device 

0346 (rev 11)
         Subsystem: LeadTek Research Inc.: Unknown device 6606
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Step 

ping- SERR- FastB2B-
         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort- <TAbort 

- <MAbort- >SERR- <PERR+
         Latency: 32 (4000ns min, 10000ns max)
         Interrupt: pin A routed to IRQ 11
         Region 0: Memory at <ignored> (32-bit, prefetchable)
         Capabilities: [44] <chain broken>
00: 9e 10 46 03 06 00 90 82 11 00 00 04 00 20 80 00
10: 08 f0 d7 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 7d 10 06 66
30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 01 10 28

-Trooper

Matthew Wilcox wrote:
> On Sat, Apr 24, 2004 at 03:21:02PM +0000, trooper ryan wrote:
> 
>>I'm really struggling to get a Brooktree video-capture card functional 
>>under 2.6.5.  I think i've isolated the problem as dmesg reports:
>>PCI: Cannot allocate resource region 0 of device 0000:00:0d.0
> 
> 
> Yeah, it looks like device 0000:00:0d.0 is completely messed up.
> 
> 
>>That device corresponds to the card as shown by lspci -vvv (see below).
> 
> 
> Can you send lspci -s 00:0d.0 -vvvxx too?
> 
> 
>>I'd really appreciate any suggestions as i've been trying to get this 
>>card functional for about two weeks.  Im so frustrated Im almost 
>>considering putting it in an XP box!
> 
> 
> Don't be stupid.  People think that threats like these make people take
> them more seriously.  It actually has the opposite effect.
> 
> 
>>0000:00:0d.0 Multimedia video controller: Brooktree Corporation: Unknown 
>>device 034e (rev 11)
>>        Subsystem: LeadTek Research Inc.: Unknown device 6606
>>        Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
>>ParErr- Stepping- SERR- FastB2B-
>>        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
>>
>>>TAbort- <TAbort- <MAbort- >SERR- <PERR+
>>
>>        Latency: 32 (4000ns min, 10000ns max)
>>        Interrupt: pin A routed to IRQ 11
>>        Region 0: Memory at <ignored> (32-bit, prefetchable) [disabled]
>>        Capabilities: [44] <chain broken>
> 
> 
> This "chain broken" concerns me a little.  If they aren't even able to
> get something as simple as PCI capabilities right, what else may they have broken?
> 
> You can use setpci to figure out how much space this device is requesting.
> 
> setpci -s 00:0d.0 BASE_ADDRESS_0=ffffffff
> setpci -s 00:0d.0 BASE_ADDRESS_0
> 
> will give you back something like ffff0004 (which would correspond to
> a 64k region).  Let us know what that returns.
> 
> 
>>0000:00:0d.1 Multimedia controller: Brooktree Corporation: Unknown 
>>device 0858 (rev 11)
>>        Subsystem: LeadTek Research Inc.: Unknown device 6606
>>        Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
>>ParErr- Stepping- SERR- FastB2B-
>>        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
>>
>>>TAbort- <TAbort- <MAbort- >SERR- <PERR+
>>
>>        Latency: 32 (1000ns min, 63750ns max)
>>        Interrupt: pin A routed to IRQ 11
>>        Region 0: Memory at <ignored> (32-bit, prefetchable) [disabled]
>>        Capabilities: [44] <chain broken>
>>
>>0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 
>>630/730 PCI/AGP VGA Display Adapter (rev 21) (prog-if 00 [VGA])
>>        Subsystem: Asustek Computer, Inc.: Unknown device 80e1
>>        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
>>ParErr- Stepping- SERR- FastB2B-
>>        Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium 
>>
>>>TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>
>>        Interrupt: pin A routed to IRQ 11
>>        BIST result: 00
>>        Region 0: Memory at f0000000 (32-bit, prefetchable)
>>        Region 1: Memory at e9800000 (32-bit, non-prefetchable) [size=128K]
>>        Region 2: I/O ports at a800 [size=128]
>>        Capabilities: [40] Power Management version 1
>>                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
>>PME(D0-,D1-,D2-,D3hot-,D3cold-)
>>                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>        Capabilities: [50] AGP version 2.0
>>                Status: RQ=16 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- 
>>HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
>>                Command: RQ=16 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- 
>>FW- Rate=x4
>>
>>
>>-------------------------------------------------------
>>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
>>_______________________________________________
>>Acpi-devel mailing list
>>Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>https://lists.sourceforge.net/lists/listinfo/acpi-devel
> 
> 


-------------------------------------------------------
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

Re: PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

[Matthew Wilcox]

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

Re: PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

[trooper ryan]

The card does work on an XP box I have, so I suspect it might be the PCI 
  riser card I'm using to slot it in to a 1RU box.  I'll try and locate 
another PCI riser to use and let you know how I go.

Thanks for all your help!



Matthew Wilcox wrote:
> 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.
> 


-------------------------------------------------------
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

Re: PCI: Cannot allocate resource region 0 of device 0000:00:0d.0

[trooper ryan]

This turned out to be a hardware problem - I gave the riser contacts a 
good clean and now the device is recognised correctly.

Many thanks for your help Matthew!



trooper ryan wrote:
> The card does work on an XP box I have, so I suspect it might be the PCI 
>  riser card I'm using to slot it in to a 1RU box.  I'll try and locate 
> another PCI riser to use and let you know how I go.
> 
> Thanks for all your help!
> 
> 
> 
> Matthew Wilcox wrote:
> 
>> 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.
>>
> 
> 
> -------------------------------------------------------
> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> 
> 


-------------------------------------------------------
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