I purchased a PCMCIA USB 2.0 adapted for my Fujitsu Lifebook and it seemed to work fine until I tried to use cardctl eject. Ejecting the card caused the system to lock up completely, and the only thing I could do was to turn off power and restart the machine. Later I noticed that ejecting works ok as long as there are no xterms open... strange...? Ejecting the cards also doesn't crash the system everytime, the crashes seem irregular. I believe this could be fixed with tampering hotplug's IRQ or memory address configuration, but how is that done then? Anyone with similar problems?

--Edit--


This is what I see in syslog when the card is inserted:
Jul 25 00:18:08 localhost kernel: cs: cb_alloc(bus 2): vendor 0x1033, device 0x0035
Jul 25 00:18:08 localhost kernel: PCI: Enabling device 02:00.0 (0000 -> 0002)
Jul 25 00:18:08 localhost kernel: PCI: Enabling device 02:00.1 (0000 -> 0002)
Jul 25 00:18:08 localhost kernel: PCI: Enabling device 02:00.2 (0000 -> 0002)
Jul 25 00:18:08 localhost cardmgr[75]: socket 0: CardBus hotplug device
Jul 25 00:18:09 localhost kernel: ehci_hcd 02:00.2: PCI device 1033:00e0
Jul 25 00:18:09 localhost kernel: ehci_hcd 02:00.2: irq 11, pci mem cc8b2000
Jul 25 00:18:09 localhost kernel: usb.c: new USB bus registered, assigned bus number 2
Jul 25 00:18:09 localhost kernel: ehci_hcd 02:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
Jul 25 00:18:09 localhost kernel: hub.c: USB hub found
Jul 25 00:18:09 localhost kernel: hub.c: 5 ports detected
Jul 25 00:18:09 localhost kernel: PCI: Setting latency timer of device 02:00.0 to 64
Jul 25 00:18:09 localhost kernel: usb-ohci.c: USB OHCI at membase 0xcc8c8000, IRQ 11
Jul 25 00:18:09 localhost kernel: usb-ohci.c: usb-02:00.0, PCI device 1033:0035
Jul 25 00:18:09 localhost kernel: usb.c: new USB bus registered, assigned bus number 3
Jul 25 00:18:09 localhost kernel: hub.c: USB hub found
Jul 25 00:18:09 localhost kernel: hub.c: 3 ports detected
Jul 25 00:18:09 localhost kernel: PCI: Setting latency timer of device 02:00.1 to 64
Jul 25 00:18:09 localhost kernel: usb-ohci.c: USB OHCI at membase 0xcc8ca000, IRQ 11
Jul 25 00:18:09 localhost kernel: usb-ohci.c: usb-02:00.1, PCI device 1033:0035
Jul 25 00:18:09 localhost kernel: usb.c: new USB bus registered, assigned bus number 4
Jul 25 00:18:09 localhost kernel: hub.c: USB hub found
Jul 25 00:18:09 localhost kernel: hub.c: 2 ports detected
Jul 25 00:18:10 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 25 00:18:10 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 00:18:10 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 25 00:18:10 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 00:18:10 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 00:18:10 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jul 25 00:18:10 localhost insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed