linux 2.6 pcmcia power issues

Madhav Diwan mvdiwan at hotmail.com
Fri Feb 25 14:27:30 EST 2005 

Hi,

 I have a problem with kernel 2.6 and pcmcia cardbus. i am using an averatec
64 bit laptop running fedora core 3 - 64bit install.

I noticed at http://pcmcia.arm.linux.org.uk/ that this is a known issue so
taking some suggestions from the page and the following info :

00:0a.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller 
(rev 01)
    Subsystem: Micro-Star International Co., Ltd.: Unknown device 0111
    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 255
    Region 0: Memory at 1e000000 (32-bit, non-prefetchable) [size=4K]
    Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
    I/O window 0: 00000000-00000003
    I/O window 1: 00000000-00000003
    BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt- PostWrite-
    16-bit legacy interface ports at 0001



Bootdata ok (command line is ro root=LABEL=/1 rhgb )
Linux version 2.6.11-rc2-bk9 (root at laptop3) (gcc version 3.4.2 20041017 
(Red Hat 3.4.2-6.fc3)) #2 Mon Jan 31 15:56:27 EST 2005
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001dfd0000 (usable)
 BIOS-e820: 000000001dfd0000 - 000000001dfdf000 (ACPI data)
 BIOS-e820: 000000001dfdf000 - 000000001e000000 (ACPI NVS)
 BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
ACPI: RSDP (v000 MSI                                   ) @ 
0x00000000000f7250
ACPI: RSDT (v001 MSI    1011     0x10112004 MSFT 0x00000097) @ 
0x000000001dfd0000
ACPI: FADT (v002 MSI    1011     0x10112004 MSFT 0x00000097) @ 
0x000000001dfd0200
ACPI: MADT (v001 MSI    OEMAPIC  0x10112004 MSFT 0x00000097) @ 
0x000000001dfd0390
ACPI: OEMB (v001 MSI    AMI_OEM  0x10112004 MSFT 0x00000097) @ 
0x000000001dfdf040
ACPI: DSDT (v001    MSI     1011 0x10112004 INTL 0x02002026) @ 
0x0000000000000000
On node 0 totalpages: 122832
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 118736 pages, LIFO batch:16
  HighMem zone: 0 pages, LIFO batch:1
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:12 APIC version 16
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 2, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Checking aperture...
CPU 0: aperture @ e0000000 size 64 MB



 I Added the following grub entry due to the above memory " overlap"


    root (hd0,1)
    kernel /vmlinuz-2.6.11-rc2-bk9 ro reserve=0x1e000000,0x5000
root=LABEL=/1 rhgb
    initrd /initrd-2.6.11-rc2-bk9.img




AFTER adding PCMCIA kernel modules and setting reserve memory ..I noted that
the ACPI system was sitting on the beginnig of the memory address for the
cardbus controller

after adding the memory reservation  the system looks like this:

cat /proc/iomem

00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000cbfff : Video ROM
000f0000-000fffff : System ROM
00100000-1dfcffff : System RAM
  00100000-003e06c2 : Kernel code
  003e06c3-0056edc7 : Kernel data
1dfd0000-1dfdefff : ACPI Tables
1dfdf000-1dffffff : ACPI Non-volatile Storage
1e000000-1e004fff : reserved
1e005000-1e005fff : 0000:00:0a.0
  1e005000-1e005fff : yenta_socket
1e400000-1e7fffff : PCI CardBus #02
1e800000-1ebfffff : PCI CardBus #02
cfd00000-dfcfffff : PCI Bus #01
  d0000000-d7ffffff : 0000:01:00.0
    d0000000-d1ffffff : sisfb FB
dfe00000-dfefffff : PCI Bus #01
  dfee0000-dfefffff : 0000:01:00.0
    dfee0000-dfefffff : sisfb MMIO
 

evrything seemed ok except after reserving memory ..though the cards  i had
did not work due to my drivers not being ready at least the error when 
the pcmcia modules were installed  did not seem to occur, until the acpi 
rip event occured......


Linux Tulip driver version 1.1.13 (May 11, 2002)
warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip acpi_ec_read+0x1cf/0x211
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unable to apply power.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unsupported voltage key.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unable to apply power.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unable to apply power.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unsupported voltage key.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unable to apply power.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unable to apply power.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unable to apply power.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
cs: pcmcia_socket0: unsupported voltage key.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
Warning: CPU frequency out of sync: cpufreq and timing core thinks of 
800000,
is 1600000 kHz.
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xfffff
cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff
cs: unable to map card memory!
cs: unable to map card memory!
2.6. kernels use pcmciamtd instead of memory_cs.c and do not require special
MTD handling any more.
PCMCIA: socket ffff810017744080: *** DANGER *** unable to remove socket 
power
[madhav at laptop3 ~]$


  has any one investigated a link between the cardbus power control 
issues and
acpi memory addressing? Or am i totally of the mark?

Thanks for any help in solving these  "unable to apply power" "unable to
remove socket power" issues


madhav

More information about the linux-pcmcia mailing list