* "PCI: Cannot allocate resource region" messages at boot
@ 2002-07-12 15:38 D. Sen
2002-07-15 11:04 ` Peter Osterlund
0 siblings, 1 reply; 3+ messages in thread
From: D. Sen @ 2002-07-12 15:38 UTC (permalink / raw)
To: linux-kernel
I am getting these messages during bootup time on an IBM Thinkpad T30:
Jul 11 17:17:24 calliope kernel: PCI: Cannot allocate resource region 0
of device 02:00.0
Jul 11 17:17:24 calliope kernel: PCI: Cannot allocate resource region 0
of device 02:00.1
lspci -vv identifies these devices as:
02:00.0 CardBus bridge: Texas Instruments: Unknown device ac55 (rev 01)
Subsystem: IBM: Unknown device 0512
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 20
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d0201000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=02, secondary=03, subordinate=05, sec-latency=176
Memory window 0: f0000000-f03ff000 (prefetchable)
Memory window 1: d0400000-d07ff000
I/O window 0: 00004000-000040ff
I/O window 1: 00004400-000044ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
16-bit legacy interface ports at 0001
02:00.1 CardBus bridge: Texas Instruments: Unknown device ac55 (rev 01)
Subsystem: IBM: Unknown device 0512
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 20
Interrupt: pin B routed to IRQ 11
Region 0: Memory at d0202000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=02, secondary=06, subordinate=08, sec-latency=176
Memory window 0: f0400000-f07ff000 (prefetchable)
Memory window 1: d0800000-d0bff000
I/O window 0: 00004800-000048ff
I/O window 1: 00004c00-00004cff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
16-bit legacy interface ports at 0001
We are also seeing weird PCMCIA behaviour whereby cardmgr does not
detect the insertion and removal of PCMCIA devices. Using the Yenta
socket in the 2.4.18 kernel. Perhaps the boot messages and this
behaviour is related?
DS
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: "PCI: Cannot allocate resource region" messages at boot
2002-07-12 15:38 "PCI: Cannot allocate resource region" messages at boot D. Sen
@ 2002-07-15 11:04 ` Peter Osterlund
2002-07-15 15:27 ` D. Sen
0 siblings, 1 reply; 3+ messages in thread
From: Peter Osterlund @ 2002-07-15 11:04 UTC (permalink / raw)
To: D. Sen; +Cc: linux-kernel, Andreas Bombe
"D. Sen" <dsen@homemail.com> writes:
> I am getting these messages during bootup time on an IBM Thinkpad T30:
>
> Jul 11 17:17:24 calliope kernel: PCI: Cannot allocate resource region
> 0 of device 02:00.0
> Jul 11 17:17:24 calliope kernel: PCI: Cannot allocate resource region
> 0 of device 02:00.1
I had a similar problem on my notebook, but this patch seems to fix
it:
--- linux/drivers/pcmcia/yenta.c.orig Mon Jul 15 12:40:54 2002
+++ linux/drivers/pcmcia/yenta.c Mon Jul 15 12:40:39 2002
@@ -736,7 +736,7 @@
return;
}
- align = size = 4*1024*1024;
+ align = size = 128*1024;
min = PCIBIOS_MIN_MEM; max = ~0U;
if (type & IORESOURCE_IO) {
align = 1024;
I have no idea if this is the right thing to do. I found the
suggestion in an earlier message from Andreas Bombe.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: "PCI: Cannot allocate resource region" messages at boot
2002-07-15 11:04 ` Peter Osterlund
@ 2002-07-15 15:27 ` D. Sen
0 siblings, 0 replies; 3+ messages in thread
From: D. Sen @ 2002-07-15 15:27 UTC (permalink / raw)
To: Peter Osterlund; +Cc: linux-kernel, Andreas Bombe
I tried it out but the patch doesnt seem to make any difference.
I see those messages before any attempt to load the yenta/pcmcia socket
models. It has to be something else, I would think. Following is the
sequence of messages at boot time (the messages appear whether or not I
load pcmcia modules):
Jul 15 11:16:29 calliope syslogd 1.4.1: restart.
Jul 15 11:16:29 calliope kernel: klogd 1.4.1, log source = /proc/kmsg
started.
Jul 15 11:16:29 calliope kernel: Inspecting /boot/System.map
Jul 15 11:16:29 calliope rpc.statd[769]: Version 0.3.3 Starting
Jul 15 11:16:29 calliope nfslock: rpc.statd startup succeeded
Jul 15 11:16:29 calliope kernel: Loaded 16257 symbols from /boot/System.map.
Jul 15 11:16:29 calliope kernel: Symbols match kernel version 2.4.18.
Jul 15 11:16:29 calliope kernel: Loaded 143 symbols from 8 modules.
Jul 15 11:16:29 calliope kernel: Linux version 2.4.18-lkpc-5beta7
(root@calliope.research.dstech.org) (gcc version 3.0.4 (Mandrake Linux
8.2 3.0.4-2mdk)) #5 Mon Jul 15 09:54:34 EDT 2002
Jul 15 11:16:29 calliope kernel: BIOS-provided physical RAM map:
Jul 15 11:16:29 calliope kernel: BIOS-e820: 0000000000000000 -
000000000009f000 (usable)
Jul 15 11:16:29 calliope kernel: BIOS-e820: 000000000009f000 -
00000000000a0000 (reserved)
Jul 15 11:16:29 calliope kernel: BIOS-e820: 00000000000d2000 -
00000000000d4000 (reserved)
Jul 15 11:16:29 calliope kernel: BIOS-e820: 00000000000dc000 -
0000000000100000 (reserved)
Jul 15 11:16:29 calliope kernel: BIOS-e820: 0000000000100000 -
000000003ff60000 (usable)
Jul 15 11:16:29 calliope kernel: BIOS-e820: 000000003ff60000 -
000000003ff7a000 (ACPI data)
Jul 15 11:16:29 calliope kernel: BIOS-e820: 000000003ff7a000 -
000000003ff7c000 (ACPI NVS)
Jul 15 11:16:29 calliope kernel: BIOS-e820: 000000003ff7c000 -
0000000040000000 (reserved)
Jul 15 11:16:29 calliope kernel: BIOS-e820: 00000000ff800000 -
0000000100000000 (reserved)
Jul 15 11:16:29 calliope kernel: 127MB HIGHMEM available.
Jul 15 11:16:29 calliope kernel: On node 0 totalpages: 261984
Jul 15 11:16:29 calliope kernel: zone(0): 4096 pages.
Jul 15 11:16:29 calliope kernel: zone(1): 225280 pages.
Jul 15 11:16:29 calliope kernel: zone(2): 32608 pages.
Jul 15 11:16:29 calliope kernel: No local APIC present or hardware disabled
Jul 15 11:16:29 calliope kernel: Kernel command line: root=/dev/hda3
devfs=mount hdc=ide-scsi vga=794 ide0=autotune ide1=autotune
video=vesa:mtrr,ywrap
Jul 15 11:16:29 calliope kernel: ide_setup: hdc=ide-scsi
Jul 15 11:16:29 calliope kernel: ide_setup: ide0=autotune
Jul 15 11:16:29 calliope kernel: ide_setup: ide1=autotune
Jul 15 11:16:29 calliope kernel: Initializing CPU#0
Jul 15 11:16:29 calliope kernel: Detected 1794.219 MHz processor.
Jul 15 11:16:29 calliope kernel: Console: colour dummy device 80x25
Jul 15 11:16:29 calliope kernel: Calibrating delay loop... 3578.26 BogoMIPS
Jul 15 11:16:29 calliope kernel: Memory: 1029248k/1047936k available
(1273k kernel code, 18300k reserved, 304k data, 252k init, 130432k highmem)
Jul 15 11:16:29 calliope kernel: Dentry-cache hash table entries: 131072
(order: 8, 1048576 bytes)
Jul 15 11:16:29 calliope kernel: Inode-cache hash table entries: 65536
(order: 7, 524288 bytes)
Jul 15 11:16:29 calliope kernel: Mount-cache hash table entries: 16384
(order: 5, 131072 bytes)
Jul 15 11:16:29 calliope kernel: Buffer-cache hash table entries: 65536
(order: 6, 262144 bytes)
Jul 15 11:16:29 calliope kernel: Page-cache hash table entries: 262144
(order: 8, 1048576 bytes)
Jul 15 11:16:29 calliope kernel: CPU: L1 I cache: 12K, L1 D cache: 8K
Jul 15 11:16:29 calliope kernel: CPU: L2 cache: 512K
Jul 15 11:16:29 calliope kernel: Intel machine check architecture supported.
Jul 15 11:16:29 calliope kernel: Intel machine check reporting enabled
on CPU#0.
Jul 15 11:16:29 calliope kernel: CPU: Intel(R) Pentium(R) 4 Mobile CPU
1.80GHz stepping 04
Jul 15 11:16:29 calliope kernel: Enabling fast FPU save and restore... done.
Jul 15 11:16:29 calliope kernel: Enabling unmasked SIMD FPU exception
support... done.
Jul 15 11:16:29 calliope kernel: Checking 'hlt' instruction... OK.
Jul 15 11:16:29 calliope kernel: POSIX conformance testing by UNIFIX
Jul 15 11:16:29 calliope kernel: mtrr: v1.40 (20010327) Richard Gooch
(rgooch@atnf.csiro.au)
Jul 15 11:16:29 calliope kernel: mtrr: detected mtrr type: Intel
Jul 15 11:16:29 calliope kernel: PCI: PCI BIOS revision 2.10 entry at
0xfd8fe, last bus=8
Jul 15 11:16:29 calliope kernel: PCI: Using configuration type 1
Jul 15 11:16:29 calliope kernel: PCI: Probing PCI hardware
Jul 15 11:16:29 calliope kernel: PCI: Discovered primary peer bus 09 [IRQ]
Jul 15 11:16:29 calliope kernel: PCI: Using IRQ router PIIX [8086/248c]
at 00:1f.0
Jul 15 11:16:29 calliope kernel: PCI: Found IRQ 11 for device 00:1f.1
Jul 15 11:16:29 calliope kernel: PCI: Sharing IRQ 11 with 00:1d.2
Jul 15 11:16:29 calliope kernel: PCI: Sharing IRQ 11 with 02:02.0
Jul 15 11:16:29 calliope kernel: PCI: Cannot allocate resource region 0
of device 02:00.0
Jul 15 11:16:29 calliope kernel: PCI: Cannot allocate resource region 0
of device 02:00.1
Thanks for the suggestion though.
DS
Peter Osterlund wrote:
> "D. Sen" <dsen@homemail.com> writes:
>
>
>>I am getting these messages during bootup time on an IBM Thinkpad T30:
>>
>>Jul 11 17:17:24 calliope kernel: PCI: Cannot allocate resource region
>>0 of device 02:00.0
>>Jul 11 17:17:24 calliope kernel: PCI: Cannot allocate resource region
>>0 of device 02:00.1
>
>
> I had a similar problem on my notebook, but this patch seems to fix
> it:
>
> --- linux/drivers/pcmcia/yenta.c.orig Mon Jul 15 12:40:54 2002
> +++ linux/drivers/pcmcia/yenta.c Mon Jul 15 12:40:39 2002
> @@ -736,7 +736,7 @@
> return;
> }
>
> - align = size = 4*1024*1024;
> + align = size = 128*1024;
> min = PCIBIOS_MIN_MEM; max = ~0U;
> if (type & IORESOURCE_IO) {
> align = 1024;
>
> I have no idea if this is the right thing to do. I found the
> suggestion in an earlier message from Andreas Bombe.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-07-15 15:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-12 15:38 "PCI: Cannot allocate resource region" messages at boot D. Sen
2002-07-15 11:04 ` Peter Osterlund
2002-07-15 15:27 ` D. Sen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox