Your message dated Sun, 24 Jun 2012 03:22:11 +0100
with message-id <[email protected]>
and subject line Re: usbip: attachall command is not working
has caused the Debian Bug report #597161,
regarding usbip: attachall command is not working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
597161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597161
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: usbip
Version: 0.1.7-3
Severity: normal


A set of USB devices is exported via a usbip server. The usbip client can list 
the exported devices from the remote server successfully:

unki@srv:~$ sudo usbip -l usbipâ‚‹server 2>&1 | grep Dallas
   5-7.1: Dallas Semiconductor : DS1490F 2-in-1 Fob, 1-Wire adapter (04fa:2490)
 5-7.2.1: Dallas Semiconductor : DS1490F 2-in-1 Fob, 1-Wire adapter (04fa:2490)
5-7.2.2.1: Dallas Semiconductor : DS1490F 2-in-1 Fob, 1-Wire adapter (04fa:2490)
5-7.2.2.2: Dallas Semiconductor : DS1490F 2-in-1 Fob, 1-Wire adapter (04fa:2490)
5-7.2.2.4: Dallas Semiconductor : DS1490F 2-in-1 Fob, 1-Wire adapter (04fa:2490)
 5-7.2.3: Dallas Semiconductor : DS1490F 2-in-1 Fob, 1-Wire adapter (04fa:2490)
 5-7.2.4: Dallas Semiconductor : DS1490F 2-in-1 Fob, 1-Wire adapter (04fa:2490)
   5-7.3: Dallas Semiconductor : DS1490F 2-in-1 Fob, 1-Wire adapter (04fa:2490)

Trying to use the --attachall parameters fails with the following message on 
the client:

unki@srv:~$ sudo usbip -x usbip-server
- usbip-server
request failed at peer, 1
usbip err: vhci_attach.c: 324 (query_import_device) recv op_common
usbip err: vhci_attach.c: 362 (attach_device) query
request failed at peer, 1
usbip err: vhci_attach.c: 324 (query_import_device) recv op_common
usbip err: vhci_attach.c: 362 (attach_device) query
request failed at peer, 1
usbip err: vhci_attach.c: 324 (query_import_device) recv op_common
usbip err: vhci_attach.c: 362 (attach_device) query
request failed at peer, 1
usbip err: vhci_attach.c: 324 (query_import_device) recv op_common
usbip err: vhci_attach.c: 362 (attach_device) query
request failed at peer, 1
usbip err: vhci_attach.c: 324 (query_import_device) recv op_common
usbip err: vhci_attach.c: 362 (attach_device) query
request failed at peer, 1
usbip err: vhci_attach.c: 324 (query_import_device) recv op_common
usbip err: vhci_attach.c: 362 (attach_device) query
request failed at peer, 1
usbip err: vhci_attach.c: 324 (query_import_device) recv op_common
usbip err: vhci_attach.c: 362 (attach_device) query
request failed at peer, 1
usbip err: vhci_attach.c: 324 (query_import_device) recv op_common
usbip err: vhci_attach.c: 362 (attach_device) query


The usbip server logs to /var/log/user.log the following during this attempt:


Sep 17 09:07:26 srv usbipd: device not available, 5-7.1
Sep 17 09:07:26 srv usbipd:      status SDEV_ST_USED
Sep 17 09:07:26 srv usbipd: connected from ::ffff:10.1.128.150:57500
Sep 17 09:07:27 srv usbipd: not found requested device 
Sep 17 09:07:27 srv usbipd: connected from ::ffff:10.1.128.150:57502
Sep 17 09:07:27 srv usbipd: not found requested device 
Sep 17 09:07:27 srv usbipd: connected from ::ffff:10.1.128.150:57504
Sep 17 09:07:27 srv usbipd: not found requested device 
Sep 17 09:07:27 srv usbipd: connected from ::ffff:10.1.128.150:57505
Sep 17 09:07:27 srv usbipd: not found requested device 
Sep 17 09:07:27 srv usbipd: connected from ::ffff:10.1.128.150:57506
Sep 17 09:07:27 srv usbipd: not found requested device 
Sep 17 09:07:27 srv usbipd: connected from ::ffff:10.1.128.150:57507
Sep 17 09:07:27 srv usbipd: not found requested device 
Sep 17 09:07:27 srv usbipd: connected from ::ffff:10.1.128.150:57509
Sep 17 09:07:27 srv usbipd: not found requested device 

But it works now to attach the USB devices one by one with the --attach 
parameter:

unki@srv:~$ sudo usbip --attach usbip-server 5-7.1
16 ports available

port 0 attached
unki@srv:~$ sudo usbip --attach usbip-server 5-7.2.1
16 ports available

port 1 attached
unki@srv:~$ sudo usbip --attach usbip-server 5-7.2.2.1
16 ports available

port 2 attached
unki@srv:~$ sudo usbip --attach usbip-server 5-7.2.2.2
16 ports available

port 3 attached
unki@srv:~$ sudo usbip --attach usbip-server 5-7.2.2.4
16 ports available

port 4 attached
unki@srv:~$ sudo usbip --attach usbip-server 5-7.2.3
16 ports available

port 5 attached
unki@srv:~$ sudo usbip --attach usbip-server 5-7.2.4
16 ports available

port 6 attached
unki@srv:~$ sudo usbip --attach usbip-server 5-7.3
16 ports available

port 7 attached

And now accessing the virtual USB ports works without any problems.
Just the --attachall call fails.

Regards,
Andreas

-- System Information:
Debian Release: squeeze/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages usbip depends on:
ii  libc6                         2.11.2-5   Embedded GNU C Library: Shared lib
ii  libglib2.0-0                  2.24.1-1   The GLib library of C routines
ii  libsysfs2                     2.1.0-6    interface library to sysfs
ii  libusbip0                     0.1.7-3    USB device sharing system over IP 
ii  usbutils                      0.87-5     Linux USB utilities

usbip recommends no packages.

usbip suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1.1.1+3.2.17-1

The attachall option/command has been removed in later versions.
Obviously this doesn't help you much, but at least there is no longer
the suggestion that you might be able to do this.

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.  It's the only way to be sure.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to