Bug 6539

Summary: PCI: cannot allocate resource region - Acer TravelMate 4101 WLMI, 1654 WLMi
Product: ACPI Reporter: Alexandru Minoiu (aminoiu)
Component: Config-OtherAssignee: ykzhao (yakui.zhao)
Status: REJECTED WILL_NOT_FIX    
Severity: normal CC: acpi-bugzilla, bughunter2, nanericwang
Priority: P2    
Hardware: i386   
OS: Linux   
Kernel Version: 2.6.16.15 Subsystem:
Regression: --- Bisected commit-id:
Attachments: dmidecode output
dmesg output when booted with acpi on
lspci -vvv output with acpi on
dmesg output with acpi off
lspci -vvv output with acpi=off
The DSDT file.
debug patch
dmesg,lspci and acpidump output
dmesg with zcpi off and nommconf
Dmesg output with pci=noacpi on patched kernel
Content of /proc/interrupts
dmesg and /proc/interrupts with noapic and acpi_irq_nobalance

Description Alexandru Minoiu 2006-05-12 13:37:06 UTC 
Most recent kernel where this bug did not occur:
Distribution:
Fedora Core 5
Hardware Environment:
Acer TravelMate 4101 WLMI

I have attached the output of dmidecode.

Software Environment:

Kernel is vanilla 2.6.16.15 
The .config file is attached.

Problem Description:

When the kernel boots with acpi enabled (no kernel  options),
the following messages are displayed:

..............................

PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.2
PCI: Bridge: 0000:00:01.0
  IO window: 3000-3fff
  MEM window: c8100000-c81fffff
  PREFETCH window: d0000000-d7ffffff
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.2
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bus 7, cardbus bridge: 0000:06:01.0
  IO window: 00004000-000040ff
  IO window: 00004400-000044ff
  PREFETCH window: 30000000-31ffffff
  MEM window: 32000000-33ffffff
PCI: Bridge: 0000:00:1e.0
  IO window: 4000-4fff
  MEM window: c8200000-c82fffff
  PREFETCH window: 30000000-31ffffff

.......................

So there seems to be a prblem with the PCI confiurstion, but related to
ACPI too.

With the option acpi=off the following messages are displayed:

.......................
PCI: Transparent bridge - 0000:00:1e.0
PCI: Bus #07 (-#08) may be hidden behind transparent bridge #06 (-#07) (try
'pci=assign-busses')
PCI: Bridge: 0000:00:01.0
  IO window: 3000-3fff
  MEM window: c8100000-c81fffff
  PREFETCH window: d0000000-d7ffffff
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.2
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bus 7, cardbus bridge: 0000:06:01.0
  IO window: 00004000-000040ff
  IO window: 00004400-000044ff
  PREFETCH window: 30000000-31ffffff
  MEM window: 32000000-33ffffff
PCI: Bridge: 0000:00:1e.0
  IO window: 4000-4fff
  MEM window: c8200000-c82fffff
  PREFETCH window: 30000000-31ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Setting latency timer of device 0000:00:1c.0 to 64
PCI: Setting latency timer of device 0000:00:1c.1 to 64
PCI: Setting latency timer of device 0000:00:1c.2 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
...............................

The messages with "cannnot allocate resource region" related to the
0000:00:1c bridge do not show up. Still the following messages remain
unchanged:

PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.2
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.

There are some errors with the DSDT compilation but the batterry status 
and cpufreq related drivers work (it's a "smart" battery).

I have attached the DSDT, and the output of dmesg and lspci -vvv
in both situations : with acpi on, and with acpi=off.

I hope this helps, and if there is more information needed please
say so.

Steps to reproduce:
always
Comment 1 Alexandru Minoiu 2006-05-12 13:41:38 UTC 
Created attachment 8100 [details]
dmidecode output
Comment 2 Alexandru Minoiu 2006-05-12 13:44:35 UTC 
Created attachment 8101 [details]
dmesg output when booted with acpi on
Comment 3 Alexandru Minoiu 2006-05-12 13:46:06 UTC 
Created attachment 8103 [details]
lspci -vvv output with acpi on
Comment 4 Alexandru Minoiu 2006-05-12 13:47:15 UTC 
Created attachment 8104 [details]
dmesg output with acpi off
Comment 5 Alexandru Minoiu 2006-05-12 13:55:13 UTC 
Created attachment 8106 [details]
lspci -vvv output with acpi=off

The output of lspci -vvv  with acpi=off is different from the
output of the same command when acpi is on at boot time:

--- lspci.txt	2006-05-12 01:35:46.000000000 +0300
+++ ../withoutacpi/lspci.txt	2006-05-12 01:53:30.000000000 +0300
@@ -36,11 +36,9 @@
		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Off, PwrInd On, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
-	Capabilities: [100] Virtual Channel
-	Capabilities: [140] Unknown (5)
 
 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI
Express Port 1 (rev 04) (prog-if 00 [Normal decode])
-	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
+	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
@@ -61,7 +59,7 @@
		Link: Speed 2.5Gb/s, Width x1
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+
		Slot: Number 2, PowerLimit 6.500000
-		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq-
+		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Unknown, PwrInd Unknown, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0
Enable-
@@ -70,11 +68,9 @@
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
-	Capabilities: [100] Virtual Channel
-	Capabilities: [180] Unknown (5)
 
 00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI
Express Port 2 (rev 04) (prog-if 00 [Normal decode])
-	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
+	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
@@ -95,7 +91,7 @@
		Link: Speed 2.5Gb/s, Width x1
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+
		Slot: Number 3, PowerLimit 6.500000
-		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq-
+		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Unknown, PwrInd Unknown, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0
Enable-
@@ -104,11 +100,9 @@
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
-	Capabilities: [100] Virtual Channel
-	Capabilities: [180] Unknown (5)
 
 00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI
Express Port 3 (rev 04) (prog-if 00 [Normal decode])
-	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
+	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=02, subordinate=04, sec-latency=0
@@ -125,11 +119,11 @@
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 3
		Link: Latency L0s <1us, L1 <4us
-		Link: ASPM Disabled RCB 64 bytes Disabled CommClk- ExtSynch-
+		Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x1
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+
		Slot: Number 4, PowerLimit 6.500000
-		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq-
+		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Unknown, PwrInd Unknown, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0
Enable-
@@ -138,8 +132,6 @@
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
-	Capabilities: [100] Virtual Channel
-	Capabilities: [180] Unknown (5)
 
 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
USB UHCI #1 (rev 04) (prog-if 00 [UHCI])
	Subsystem: Acer Incorporated [ALI] Unknown device 0066
@@ -162,7 +154,7 @@
	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: 0
-	Interrupt: pin C routed to IRQ 10
+	Interrupt: pin C routed to IRQ 11
	Region 4: I/O ports at 1840 [size=32]
 
 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
USB UHCI #4 (rev 04) (prog-if 00 [UHCI])
@@ -202,7 +194,7 @@
	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: 0
-	Interrupt: pin A routed to IRQ 11
+	Interrupt: pin A routed to IRQ 10
	Region 0: I/O ports at 1c00 [size=256]
	Region 1: I/O ports at 1880 [size=64]
	Region 2: Memory at c8000800 (32-bit, non-prefetchable) [size=512]
@@ -215,7 +207,7 @@
	Subsystem: Acer Incorporated [ALI] Unknown device 0066
	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 B routed to IRQ 10
+	Interrupt: pin B routed to IRQ 11
	Region 0: I/O ports at 2400 [size=256]
	Region 1: I/O ports at 2000 [size=128]
	Capabilities: [50] Power Management version 2
@@ -233,7 +225,7 @@
	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: 0
-	Interrupt: pin A routed to IRQ 10
+	Interrupt: pin A routed to IRQ 0
	Region 0: I/O ports at <unassigned>
	Region 1: I/O ports at <unassigned>
	Region 2: I/O ports at <unassigned>
@@ -273,14 +265,13 @@
		Link: Speed 2.5Gb/s, Width x16
	Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
		Address: 0000000000000000  Data: 0000
-	Capabilities: [100] Advanced Error Reporting
 
 06:01.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
	Subsystem: Acer Incorporated [ALI] Unknown device 0066
	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: 168, Cache Line Size 10
-	Interrupt: pin A routed to IRQ 10
+	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at c8208000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=06, secondary=07, subordinate=08, sec-latency=176
	Memory window 0: 30000000-31fff000 (prefetchable)
@@ -295,7 +286,7 @@
	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 (750ns min, 1000ns max), Cache Line Size 08
-	Interrupt: pin A routed to IRQ 10
+	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at c8209000 (32-bit, non-prefetchable) [size=2K]
	Region 1: Memory at c8200000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [44] Power Management version 2
Comment 6 Alexandru Minoiu 2006-05-12 14:06:53 UTC 
Created attachment 8107 [details]
The DSDT file.

This is a copy of /proc/acpi/dsdt.
After the DSDT is disassembled and then I try to
generate the AML file with iasl -tc , the output is:

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20060421 [May  9 2006]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a

curdsdt.dsl   462:		       Store (\PPMF, CFGD)
Error	 4062 - 		  Object does not exist ^  (CFGD)

curdsdt.dsl   481:		       And (CFGD, 0xFFFFFF3F, CFGD)
Error	 4062 - 	 Object does not exist ^  (CFGD)

curdsdt.dsl   481:		       And (CFGD, 0xFFFFFF3F, CFGD)
Error	 4062 - 			   Object does not exist ^  (CFGD)

curdsdt.dsl   594:	       If (LEqual (And (PDC0, 0x0A), 0x0A))
Error	 4062 - 	     Object does not exist ^  (PDC0)

curdsdt.dsl   599:	       If (LEqual (And (PDC1, 0x0A), 0x0A))
Error	 4066 - 				   ^ Object is not accessible
from this scope (PDC1)

curdsdt.dsl  1952:		       Method (DRUL, 1, NotSerialized)
Warning  1086 - 				  ^ Not all control paths
return a value (DRUL)

curdsdt.dsl  2599:			   Method (_DCK, 1, NotSerialized)
Warning  1086 -  Not all control paths return a value ^  (_DCK)

curdsdt.dsl  2599:			   Method (_DCK, 1, NotSerialized)
Warning  1079 -   Reserved method must return a value ^  (_DCK)

curdsdt.dsl  2651:			   Store (CFGD, \PPMF)
Error	 4062 - 	       Object does not exist ^	(CFGD)

curdsdt.dsl  2655:			       And (CFGD, 0xFFFFFF3F, CFGD)
Error	 4062 - 		 Object does not exist ^  (CFGD)

curdsdt.dsl  2655:			       And (CFGD, 0xFFFFFF3F, CFGD)
Error	 4062 - 				   Object does not exist ^ 
(CFGD)

curdsdt.dsl  2664:			       Store (\PPMF, CFGD)
Error	 4062 - 			  Object does not exist ^  (CFGD)

curdsdt.dsl  7128:		   Z00C,
Error	 4062 - Object does not exist ^  (Z00C)

curdsdt.dsl  7129:		   Z00C,
Error	 4062 - Object does not exist ^  (Z00C)

curdsdt.dsl  7420:		   Z00C,
Error	 4062 - Object does not exist ^  (Z00C)

curdsdt.dsl  7421:		   Z00C,
Error	 4062 - Object does not exist ^  (Z00C)

curdsdt.dsl  7593:			       And (0xFE, Local7)
Warning  1104 - 				       ^ Result is not used,
operator has no effect

ASL Input:  curdsdt.dsl - 7740 lines, 291249 bytes, 3225 keywords
Compilation complete. 13 Errors, 4 Warnings, 0 Remarks, 1160 Optimizations
Comment 7 Len Brown 2006-05-18 01:06:51 UTC 
does anything actually fail to work on this machine,
or it this bug about the following lines dmesg:

PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.0
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.2
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.2
Comment 8 Alexandru Minoiu 2006-05-18 17:13:25 UTC 
Hi,
I haven't found any failure so far, just those messages worried me.
So I guess everything is OK with that ?
Sorry if this is just another false positive :).
Comment 9 Luc Mo Costabella 2006-07-09 04:52:14 UTC 
Hi,

I have the same problem (documented in bug 6305
which I think is a duplicate of this one, and
was never attended), but the computer crashes
during setup. My config :
Acer aspire 1654WLMi notebook
Fedora Core 5
kernel : 2.6.16-1.2080_FC5

The system crashes during udev
initialization. With kernel 2.6.16, the
system loads if I use option acpi=off, but
with several functions not available (for
example the battery level).

With kernel 2.6.17, I have the same crash
during udev initialisation. If I use option
acpi=off, the system loads further, but
crashes before the login with a black screen.

If you need dmesg, lspci or other output,
please let me know by email. Help, I had to
use Windoze since I bought the computer in
Feb. 2006 !
Comment 10 ykzhao 2007-10-21 19:26:45 UTC 
Hi, Alexandru
Will you please upload the full dmesg(acpi is on) and acpidump info?  
Thanks.
Comment 11 ykzhao 2007-11-26 21:21:46 UTC 

*** This bug has been marked as a duplicate of bug 7218 ***
Comment 12 Fu Michael 2007-12-03 01:10:17 UTC 
*** Bug 7218 has been marked as a duplicate of this bug. ***
Comment 13 Fu Michael 2007-12-03 01:11:08 UTC 
track this bug instead of 7218, as there are more info here...
Comment 14 ykzhao 2007-12-25 18:44:34 UTC 
Created attachment 14186 [details]
debug patch

Will you please try the debug patch and attach the output of dmesg ?
Thanks.
Comment 15 ykzhao 2007-12-25 18:48:45 UTC 
Hi, Alexandru && Luo
Will you please try the debug patch and attach the output of dmesg ,lspci -vxxx and acpidump? 

Thanks.
Comment 16 Jelle Geerts 2007-12-26 03:26:34 UTC 
If they don't respond, I might be able to give it a try. I have my notebook back soon.
Comment 17 ykzhao 2008-01-23 00:55:22 UTC 
Since there is no response, the bug will be rejected. 
If problem still exists in the latest kernel, Please reopen the bug.
Thanks.
Comment 18 Alexandru Minoiu 2008-03-11 07:38:56 UTC 
Hi,
Sorry for the delay. I have applied the patch by ykzhao to
version 2.6.24-rc5  of the kernel. I shall attach the requested info.
Thanks.
Comment 19 Alexandru Minoiu 2008-03-11 07:47:38 UTC 
Created attachment 15214 [details]
dmesg,lspci and acpidump output

Hi,
This zip archive contains the output of the following commands,
after I have applied the debug patch to the 2.6.24-rc5 kernel:
acpidump
dmesg
lspci -vxxx

I hope this helps.
Thanks a lot!
Comment 20 ykzhao 2008-03-18 02:58:10 UTC 
Hi, Alexandru
   Thanks for the info.
   From the log in comment #19 we can know that the pci bridge(1c.0,1c.1, 1c.2) is programmed by BIOS as the following :
   I/O base and limit: 0-0xfff
   Memory base and limit: 0-0xfffff.

   Unfortunately OSPM can't allocate the I/O memory resource for the above region. So OS reports the warning message that Cannot allocate resource region 7 of bridge 0000:00:1c.0. 
   At the same time there is no PCI device behind the 1c.0/1c.1/1c.2 bridge.
   It is harmless.
Comment 21 ykzhao 2008-03-18 07:12:41 UTC 
Hi, Alexandru
   Will you please boot the system with the option of "acpi=off" and attach the output of dmesg?
   It will be great if you can boot the system with the option of "pci=nommconf" and attach the output of dmesg.
   Of course the debug patch is required.
   Thanks.
Comment 22 Alexandru Minoiu 2008-03-21 10:53:44 UTC 
Created attachment 15384 [details]
dmesg with zcpi off and nommconf

Hi Yakui Zhao,
I have done what you have asked and booted
the patched kernel with acpi=off and pci=nommconf
in three combinations:
- with acpi=off : logacpioff.txt
- with pci=nommconf : lognommconf.txt
- with acpi=off and pci=nommconf : logacpioffnommconf.txt
These three files in the acpinommconf.zip archive 
contain the output of dmesg.

Thanks a lot,
Alex.
Comment 23 ykzhao 2008-03-27 08:08:31 UTC 
Hi, Alexandru
    Thanks for the info.
    Will you please try the boot option of "pci=noacpi" and attach the output of dmesg?
    Thanks.
Comment 24 Alexandru Minoiu 2008-03-28 15:36:45 UTC 
Created attachment 15483 [details]
Dmesg output with pci=noacpi on patched kernel

Hi Yakui Zhao,
I have attached the output of dmesg after booting the patched kernel
with the option pci=noacpi. I hope this helps.
I noticed that in some dmesg outputs, when acpi=off or when pci=noacpi
(this attachement) , there is a stack trace after irq 10: nobody cared .
Comment 25 Alexandru Minoiu 2008-03-28 16:15:50 UTC 
Created attachment 15484 [details]
Content of /proc/interrupts

Hi Yakui,

  I have made another attachement with two files:
    - pcinoacpiirqs.txt - is cat > /proc/interrupts when pci=noacpi
    - nooptionsirqs.txt - is cat > /proc/interrupts without any boot options .
  Maybe this sheds some light on the stack trace in pcinoacpipatched.txt
  after the "irq 10: nobody cared"  line.

  Thanks!
Comment 26 ykzhao 2008-04-07 00:14:33 UTC 
Hi,Alexandru
   Sorry for the delay.
   From the logs it seems that there are two problems about your laptop.
a. there exists the following message when acpi is enabled.
   >PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.0
   >PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
   >PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.0
   >PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.1
   >PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
   >PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.1
   >PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.2
   >PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.2
   >PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.2
  The above message won't break anything and it is harmless. Maybe the above message is related with that some configure setting of some PCI devices(1c.0,1c.1,1c.2) will be changed in the course of mode transition from legacy mode to acpi mode(not sure). When the system is booted with the option of "pci=noacpi", OSPM will also use the same legacy PCI scan mechanism as the boot option of "acpi=off". The only difference is that  acpi is enabled in case of "pci=noacpi". Maybe the configure settings of some devices will be changed when the system is switched from legacy mode to ACPI mode.
   Because the above message is harmless, it is not worth spending more time on it.
b. the error message "IRQ 10 nobody cared" on 2.6.24-rc5 kernel with acpi=off or "pci=noacpi"
   It seems that this is related with PCI interrupt routing.(pci=noacpi/ acpi=off).
   Will you please try to boot the system with the option of "noapic acpi_irq_nobalance" and attach the output of dmesg, /proc/interrupts?
   Thanks.
Comment 27 Alexandru Minoiu 2008-04-10 08:58:53 UTC 
Created attachment 15719 [details]
dmesg and /proc/interrupts with noapic and acpi_irq_nobalance

Hi Yakui,
I have attached the output of dmesg and /proc/interrupts as you asked.
Since I see no visible problem regarding the "PCI cannot allocate ..." messages
except the messages themselves I think it is OK to close the bug if you wish.
The second problem does not bother me either, because I run Linux with acpi on
and the IRQ problem does not manifest itself in this case.
If you need more info please tell me.

Thank you for your time.
Comment 28 ykzhao 2008-04-10 19:59:46 UTC 
Hi, Alexandru
    Thanks for the info.
    From the log in comment #27 it seems that the system can work well when the system is booted in PIC mode with acpi enabled. And it is confirmed that the second problem is caused by the incorrect PCI interrupt routing.(pci=noacpi/acpi=off).
    In your laptop there is no MPS table /bios PRT table , which includes the info of PCI interrupt routing. When the system is booted with pci=noacpi/acpi=off , OSPM will read the irq number directly from the PCI device config space and request the interrupt handler for the device. Unfortunately the IRQ number of some PCI devices is incorrect. So OS will report the error message " IRQ 10 nobody cared".
    For example: 06.01.2 device:
    The irq number of PCI config space is 0x0b.
    The irq number in PIC mode is 0x0a.
   > ACPI: PCI Interrupt 0000:06:01.2[A] -> Link [LNKG] -> GSI 10 (level, low) -> IRQ 10

  Because the system can work well with acpi enabled, it is unnecessary to fix this problem.