how to debug a "get dev info on socket 0 failed" error?

What does "bind" mean, what binds to what or for what reason?  And why doesn't 
it work?


Environment: am embedded system with an Intel PXA250 processor (that's some 
ARM like processor)
Linux 2.4.19-rmk4-pxa2
pcmcia-cs 3.2.3

I'm using the kernel-modules, in /etc/modules.conf there is a line "alias 
alias ide_cs ide-cs pc_debug=9".

Question: is this correct?   Why aren't those drivers named equally?  It's a 
pain-in-the-ass to have an ide-cs.o and ide_cs.o :-(


Anyway, when I boot without any card and call dmesg, then I see:

ds.c 1.112 2001/10/13 00:08:28 (David Hinds)
cs: bind_device(): client 0xc0376a60, sock 0, dev Driver Services
cs: register_client(): client 0xc0376a60, sock 0, dev Driver Services
cs: bind_device(): client 0xc0376b60, sock 1, dev Driver Services
cs: register_client(): client 0xc0376b60, sock 1, dev Driver Services
Looking up port of RPC 100003/2 on 192.168.233.1
Looking up port of RPC 100005/1 on 192.168.233.1
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing init memory: 80K
ds_open(socket 0)
ds_open(socket 1)
ds_open(socket 2)
ds_open(socket 2)
ds_poll(socket 0)
ds_poll(socket 1)
ds_poll(socket 0)
ds_poll(socket 1)

Now I insert the card and I see on the console:

# my_pcmcia_configure_socket: sock 0 vcc 33 vpp 33
my_pcmcia_configure_socket: sock 0 vcc 33 vpp 33
my_pcmcia_configure_socket: sock 0 vcc 33 vpp 33
cardmgr[248]: initializing socket 0
cardmgr[248]: socket 0: ATA/IDE Fixed Disk
cardmgr[248]:   product info: "KINGSTON TECHNOLOGY ATA CARD", "V1.00"
cardmgr[248]:   manfid: 0x0007, 0x0000  function: 4 (fixed disk)
cardmgr[248]: executing: 'modprobe ide_cs'
cardmgr[248]: get dev info on socket 0 failed: Resource temporarily 
unavailable

when I look at dmesg, I see

cs: setup_socket(c0384800): applying power
my_pcmcia_configure_socket: sock 0 vcc 33 vpp 33
cs: resetting socket c0384800
my_pcmcia_configure_socket: sock 0 vcc 33 vpp 33
my_pcmcia_configure_socket: sock 0 vcc 33 vpp 33
cs: reset done on socket c0384800
cs: send_event(sock 0, event 4, pri 0)
ds: ds_event(0x000004, 0, 0xc0376a60)
cs: send_event(sock 0, event 16, pri 0)
cs: send_event(sock 0, event 32, pri 0)
ds_poll(socket 0)
ds_poll(socket 1)
ds_read(socket 0)
ds_ioctl(socket 0, 0x8004640b, 0xbffff93c)
ds_ioctl(socket 0, 0xc0206404, 0xbffff93c)
ds_ioctl(socket 0, 0xc2946406, 0xbffff93c)
ds_ioctl(socket 0, 0xc2946407, 0xbffff93c)
ds_ioctl(socket 0, 0xc0206404, 0xbffff93c)
ds_ioctl(socket 0, 0xc2946406, 0xbffff93c)
ds_ioctl(socket 0, 0xc2946407, 0xbffff93c)
ds_ioctl(socket 0, 0xc0206404, 0xbffff93c)
ds_ioctl(socket 0, 0xc2946406, 0xbffff93c)
ds_ioctl(socket 0, 0xc2946407, 0xbffff93c)
ds_ioctl(socket 0, 0xc0206404, 0xbffff93c)
ds_ioctl: ret = 31
ds_ioctl(socket 0, 0xc0206404, 0xbffff93c)
ds_ioctl: ret = 31
ds_ioctl(socket 0, 0xc00c6409, 0xbffff930)
ide_cs.c 1.26 1999/11/16 02:10:49 (David Hinds)
cs: CardServices(GetCardServicesInfo, 0xc7c9bee8, 0x00000001)
ds: register_pccard_driver('ide-cs')
ds_ioctl(socket 0, 0xc050643c, 0x367f8)
bind_request(0, 'ide_cs')
cs: bind_device(): client 0xc7f66080, sock 0, dev ide_cs
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0xc050643d, 0x367f8)
ds_ioctl(socket 0, 0x4050643f, 0x367f8)
unbind_request(0, 'ide_cs')
ds_poll(socket 0)
ds_poll(socket 1)

# lsmod
Module                  Size  Used by
ide-cs                  4016   0  (unused)
# cat /proc/devices
Character devices:
  1 mem
...
254 pcmcia

Block devices:
 31 mtdblock

So, ide-cs is there, but there is no block device ide0 or something.


# cat /proc/bus/pccard/drivers
ide-cs                   0 0
# cat /proc/bus/pccard/00/clients
fn 0: 'ide_cs' [attr 0x0000] [state 0x0008]
fn ff: 'Driver Services' [attr 0x0001] [state 0x0000]
# cat /proc/bus/pccard/00/status
k_flags  : detect ready vs_3v
status   : SS_DETECT SS_READY SS_POWERON SS_BATDEAD SS_BATWARN SS_3VCARD
mask     : SS_DETECT
cs_flags : SS_OUTPUT_ENA
Vcc      : 33
Vpp      : 33
irq      : 0
I/O      : 165 (180)
attribute: 300 (301)
common   : 250 (271)



How could I pursue this bug and fix it?   I might add that even my hardware 
might be buggy, it's freshly soldered :-)



-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp