Red Hat Bugzilla – Bug 169268
pcmcia generates error with kernel 2.6.13-1.1524_FC4
Last modified: 2015-01-04 17:22:11 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Description of problem:
On start up pcmcia generates an error message when using the kernel from updates-testing(2.6.13-1.1524_FC4). Booting into the older kernel sees normal startup for pcmcia.
[root@eyrie ~]# uname -r
[root@eyrie ~]# dmesg -c >> /dev/null
[root@eyrie ~]# service pcmcia restart
Shutting down PCMCIA services: done.
Starting PCMCIA services: cardmgr: watching 1 socket
cardmgr: could not adjust resource: IO ports 0x3d3-0x3d3: Input/output error
[root@eyrie ~]# dmesg
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x100-0x4ff: excluding 0x170-0x177 0x370-0x377
cs: IO port probe 0xa00-0xaff: clean.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.restart pcmcia with new kernel
2.restart pcmcia with old kernel
Actual Results: error message on starting pcmcia
Expected Results: no error message
fixed for me with 2.6.13-1.1526_FC4
Robert? Does it work now?
Same problem with 2.6.13-1.1524_FC4 also fixed for me in 2.6.13-1.1526_FC4
Sorry, had some family problems and forgot about this.
Looks good to me as well.
I still see something similar in 2.6.13-1.1526_FC4. At boot, when the cardmgr
service starts, it prints a message to the effect of "could not reserve
resources 0xa0000000 - 0xa0ffffff: input/output error" (apologies for not having
the exact text). It doesn't show up if I subsequently restart the pcmcia
service. I don't know if this affects anything since I have no PCMCIA devices
with which to test.
Created attachment 119502 [details]
2.6.13-1.1526_FC4 startup messages w/ I/O error on cardmgr start
Created attachment 119503 [details]
lspci for machine w/ cardmgr error on 2.6.13-1.1526_FC4
I too see problems 2.6.13-1.1526_FC4 that were not in 2.6.12:
I see no log errors, but my pcmcia wireless card is only recognised on every
second insertion. First, third, fifth etc insertions do not start up the card
and generate nothing in the logs (this did not happen with older kernels). Card
starts OK if present on boot, but then fails to start if removed and
reinserted, and then on every second try after that.