From: Parag Warudkar <kernel-stuff@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc6-git5 : PCI mem resource alloc failure == PCMCIA Busted
Date: Sat, 13 Aug 2005 22:50:40 -0400 [thread overview]
Message-ID: <1123987840.2712.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1123982870.2779.7.camel@localhost.localdomain>
On Sat, 2005-08-13 at 21:27 -0400, Parag Warudkar wrote:
> With 2.6.13-rc6-git5 I started getting the below errors. Despite of the
> errors everything works fine. (only problem is that I have to
> disconnect /reconnect the usb mouse for it to get detected..)
Another problem is that PCMCIA is busted - I get the below errors and my
wireless pcmcia card no longer works with -rc6-git5.
Starting PCMCIA services: cardmgr[2929]: watching 2 sockets
cardmgr[2929]: could not adjust resource: IO ports 0x3d3-0x3d3:
Input/output error
dmesg | grep -i pcmcia
[ 249.156295] pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff
[ 249.156304] pcmcia: parent PCI bridge Memory window: 0xe0100000 -
0xe17fffff
[ 249.156311] pcmcia: parent PCI bridge Memory window: 0x60000000 -
0x63ffffff
[ 249.736632] pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff
[ 249.736639] pcmcia: parent PCI bridge Memory window: 0xe0100000 -
0xe17fffff
[ 249.736646] pcmcia: parent PCI bridge Memory window: 0x60000000 -
0x63ffffff
lspci -vv | grep CardBus
02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
Subsystem: Hewlett-Packard Company: Unknown device 006d
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 177
Region 0: Memory at e0106000 (32-bit, non-prefetchable)
[size=4K]
Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
Memory window 0: 60000000-61fff000 (prefetchable)
Memory window 1: e0400000-e07ff000
I/O window 0: 00003000-00003fff
I/O window 1: 00004000-00004fff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
16-bit legacy interface ports at 0001
02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
Subsystem: Hewlett-Packard Company: Unknown device 006d
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 B routed to IRQ 185
Region 0: Memory at e0107000 (32-bit, non-prefetchable)
[size=4K]
Bus: primary=02, secondary=07, subordinate=0a, sec-latency=176
Memory window 0: 62000000-63fff000 (prefetchable)
Memory window 1: e0c00000-e0fff000
I/O window 0: 00005000-00005fff
I/O window 1: 00006000-00006fff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
16-bit legacy interface ports at 0001
next prev parent reply other threads:[~2005-08-14 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 1:27 2.6.13-rc6-git5 : PCI mem resource alloc failure Parag Warudkar
2005-08-14 2:50 ` Parag Warudkar [this message]
2005-08-16 10:01 ` Jan Engelhardt
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=1123987840.2712.4.camel@localhost.localdomain \
--to=kernel-stuff@comcast.net \
--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
Powered by JetHome