From: "D. Sen" <dsen@homemail.com>
To: linux-kernel@vger.kernel.org
Subject: "PCI: Cannot allocate resource region" messages at boot
Date: Fri, 12 Jul 2002 11:38:26 -0400 [thread overview]
Message-ID: <3D2EF7F2.1070107@homemail.com> (raw)
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
next reply other threads:[~2002-07-12 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 15:38 D. Sen [this message]
2002-07-15 11:04 ` "PCI: Cannot allocate resource region" messages at boot Peter Osterlund
2002-07-15 15:27 ` D. Sen
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=3D2EF7F2.1070107@homemail.com \
--to=dsen@homemail.com \
--cc=linux-kernel@vger.kernel.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