-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for the quick followup, Andreas--

At 2006-12-13 22:10, [EMAIL PROTECTED] said:

> If you have both /dev/bus/usb and /proc/bus/usb that is a bug in
> your system config and can trigger this. 

hrm.  /dev/bus/usb appears to be created/managed by udev entirely, but
/proc/bus/usb is exported (as an empty directory) by the kernel, and
then usbfs is mounted on top of that.

I can unmount /proc/bus/usb, but i get an error trying to remove the
directory:

[0 [EMAIL PROTECTED] ~]# rmdir /proc/bus/usb
rmdir: /proc/bus/usb: Operation not permitted
[1 [EMAIL PROTECTED] ~]# 

fwiw, /proc/bus/usb gets mounted in /etc/init.d/mountkernfs.sh, which
appears to be part of the initscripts package under etch.

> udev will start two processes, one tries the /dev/bus/usb device,
> one tries the /proc/bus/usb device, and the one who can claim the
> interface wins.

i can see why that would be a problem.  i'm just not sure what to do
about it.  Maybe this bug should be reassigned to udev or initscripts?

> remove either /dev/bus/usb or /proc/bus/usb or edit the openct udev
> script in /lib/udev to ignore requests for one of those two.

with /proc/bus/usb unmounted, i'm still getting two ifdhandlers, but
with slightly different messages than before:

Dec 13 16:37:56 squeak ifdhandler[14728]: Unable to open USB device 
/dev/usbdev2.32_ep00: No such device or address
Dec 13 16:37:56 squeak ifdhandler[14728]: usb:/dev/usbdev2.32_ep00: 
initialization failed (driver egate)
Dec 13 16:37:56 squeak ifdhandler[14728]: unable to open reader egate usb 
/dev/usbdev2.32_ep00
Dec 13 16:37:56 squeak ifdhandler[14736]: Unable to open USB device 
/proc/bus/usb/002/032: No such file or directory
Dec 13 16:37:56 squeak ifdhandler[14736]: usb:/proc/bus/usb/002/032: 
initialization failed (driver egate)
Dec 13 16:37:56 squeak ifdhandler[14736]: unable to open reader egate usb 
/proc/bus/usb/002/032

I haven't fiddled with /lib/udev/openct_usb yet.

However, despite the two ifdhandlers, while /proc/bus/usb is
unmounted, the reader seems to be persistently labeled reader 0.

> > If i can help in debugging this at all, please let me know.
> 
> true. for some reason this never happends on my machines. maybe
> ubuntu does something different? if you only have /dev/bus or
> /proc/bus but not both, and the problem still happends, then there
> is a big problem and we need to debug it. but for the time being I
> guess it is the dual /dev/bus and /proc/bus that is causing the
> problems.

hrm.  i still don't know why udev should be spawning two ifdhandler
processes if /proc/bus/usb is unmounted.  If that's not OK, maybe this
should be reassigned to udev.  But if that is deemed acceptable, maybe
the bug should be with the initscripts package, for including an
/etc/init.d/mountkernfs.sh which mounts /proc/bus/usb even on systems
which have /dev/bus/usb already?

        --dkg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFFgHTZiXTlFKVLY2URAp7fAKCuVmagspWYurUUSX875/L/0SNz9gCglN9A
nAuG3G3eAtbcmu9FBEifHy0=
=mnzz
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to