USB storage problem

Help
Michiel
2007-01-16
2013-05-30
  • Michiel

    Michiel - 2007-01-16

    Hello,

    I've installed the usbip driver on a 2.6.19.2 kernel. Both client and server. The client and server both have Ubuntu installed (Edgy Eft).

    When I attach a usb_storage (USB flash disk (2 different types tried)) device and attach it to the client, the vhci-hcd.ko gives some error. Like the following:
        usbip err: vhci_driver.c:  60 (imported_device_init) sysfs_open_device -i�^  [No such file or directory]
        usbip err: vhci_driver.c: 140 (parse_status) init new device  [No such file or directory]
        usbip err: vhci_attach.c: 443 (detach_port ) open vhci_driver  [No such file or directory]

    I don't know if SourceForge will filter the "special" characters.

    I think the special characters are meant as port name/id. Which usbip doesn't recognise.

    USB mouse does attach correctly though.

    When I attach a usbdisk at first it's connected correctly and it doesn't give any errors. At /sys/bus/platform/devices/vhci_hcd/status it gives the following message:
        prt sta spd bus dev socket   local_busid
        000 006 003 004 007 e39dd300 6-1

    But after gnome-volume-manager comes in to play (at least I think it is gnome-volume-manager which mounts the usb device to a mount location) it gives the errors above and also the rule changes in /sys/bus/platform/devices/vhci_hcd/status like the following:
        prt sta spd bus dev socket   local_busid
        000 006 003 004 007 e39dd300 8

    It changes the local_busid to something else. I don't know why it does that, but I think the vhci driver recognises the busid as the old one, so it can't find the usb device anymore. My knowledge doesn't go that far to verify that, but maybe you guys know.

     
    • hirofuchi

      hirofuchi - 2007-01-16

      Hi,

      This will be a bug of something. But, I am not sure what is wrong.

      > prt sta spd bus dev socket local_busid
      > 000 006 003 004 007 e39dd300 6-1
      ...
      > prt sta spd bus dev socket local_busid
      > 000 006 003 004 007 e39dd300 8

      I think local_busid (also found in /sys/bus/usb/devices/) does not change as long as a device is connected. If a remote device (6-1) is disconnected, the usbip drivers will cleanup resources and no entry will be listed in /sys/bus/platform/devices/vhci_hcd/status .

      Is there no kernel message at this time?

      If possible,  please look at /sys/bus/usb/devices/ directory. It has all usb devices in a system.

       
      • Michiel

        Michiel - 2007-01-16

        Here you can find the kernel log: http://beheer.eduwijs.nl/kernel-usbip.log I thought of kernel loggin though. I've also build it under debugging mode now.

        /sys/devices/platform/vhci_hcd/status shows on error (now):
        prt sta spd bus dev socket           local_busid
        000 006 003 004 007         f4f9a280 �

        Also a wierd character.

        The device is not disconnected or reconnected at the testing moment. Maybe bad communication between server and client?

        But it's still listed as "in use". Is it because it didn't cleanup resource good enough?

         
    • Michiel

      Michiel - 2007-01-17

      Also I think it's udev or it's gnome-volume-manager which is changing the busid. I don't think usbip is the one which does that.

       
    • Michiel

      Michiel - 2007-01-17

      Ok, gnome-volume-manager is the one which mounts the USB storage devices. (http://www.linuxfromscratch.org/blfs/view/svn/gnome/gnome-volume-manager.html)

      I'm going to look if i can manage to change those scripts and to look what it does with the device.

       
    • Michiel

      Michiel - 2007-01-18

      Also I've another log from syslog. Maybe this one will explain more: http://beheer.eduwijs.nl/syslog-usbip.log

       
    • Michiel

      Michiel - 2007-01-18

      OK i've looked into the syslog log and saw the following rule:
      Jan 18 15:27:49 michiel kernel: vhci_hcd vhci_hcd: Unlink after no-IRQ?  Controller is probably using the wrong IRQ.

      Could this be the error which is causing USB storage devices not to work? If that's so it needs te disconnect the device, but it gives the following message:
      Jan 18 15:27:49 michiel kernel: usbip: vhci_hcd: dequeue a urb f76269c0
      Jan 18 15:27:49 michiel kernel: usbip: vhci_hcd: device f76200f8 seems to be still connected

      and
      Jan 18 15:27:49 michiel kernel: vhci_rx   :(/root/usbip-0.1.4/drivers/2.6.19/usbip_common.c,334) usbip_dump_header: BASE: cmd 4 bus 0 dev 0 seq 15 pipe 0000
      Jan 18 15:27:49 michiel kernel: dev(0) ep(0) OUT ISO
      Jan 18 15:27:49 michiel kernel: vhci_rx   :(/root/usbip-0.1.4/drivers/2.6.19/usbip_common.c,359) usbip_dump_header: RET_UNLINK: status -104
      Jan 18 15:27:49 michiel kernel: vhci_rx   :(/root/usbip-0.1.4/drivers/2.6.19/usbip_common.c,334) usbip_dump_header: BASE: cmd 4 bus 0 dev 0 seq 15 pipe 0000
      Jan 18 15:27:49 michiel kernel: dev(0) ep(0) OUT ISO
      Jan 18 15:27:49 michiel kernel: vhci_rx   :(/root/usbip-0.1.4/drivers/2.6.19/usbip_common.c,359) usbip_dump_header: RET_UNLINK: status -104
      Jan 18 15:27:49 michiel kernel: usbip: unlink->seqnum 15
      Jan 18 15:27:49 michiel kernel: vhci_rx   :(/root/usbip-0.1.4/drivers/2.6.19/vhci_rx.c,128) dequeue_pending_unlink: found pending unlink, 15

      So it tries to unlink the devices, but it's not succesfull.

       
      • hirofuchi

        hirofuchi - 2007-01-19

        Hi,

        Thanks! Very Informative.

        > Jan 18 15:27:49 michiel kernel: vhci_hcd vhci_hcd: Unlink after no-IRQ? Controller is probably using the wrong IRQ.
        > Jan 18 15:27:49 michiel kernel: usbip: vhci_hcd: dequeue a urb f76269c0
        > Jan 18 15:27:49 michiel kernel: usbip: vhci_hcd: device f76200f8 seems to be still connected

        > Could this be the error which is causing USB storage devices not to work? If that's so it needs te disconnect the device, but it gives the following message:

        The Linux kernel in the client side tried to disconnect (reset) it.
        But, vhci_hcd driver did not reset it correctly.
        So, /sys/bus/platform/devices/vhci_hcd/status showed a wrong entry.
        I will try to fix this issue.

        However, I think the first error was caused by the server side.
        Did you find any error messages in the server side?

         
        • Michiel

          Michiel - 2007-01-19

          On the server I get the following errors: (without debugging)
          usbip: set_configuration: devnum 2 1
          usbip: unlink urb e31d1d40
          usbip: unlinked by a call of usb_unlink_urb()
          stub_rx   : ***ERROR*** (/usr/src/usbip-0.1.4/drivers/2.6.19/stub_rx.c,392) stub_rx_pdu: recv a header, 0
          usb 2-2: reset full speed USB device using uhci_hcd and address 2
          usbip: device reset

          With debug on usbipd I get the following:
          connected from ::ffff:192.168.2.27:45560
          usbip err: stub_driver.c: 110 (usbip_exported_device_new) open /sys/devices/pci0000:00/0000:00:10.4/usb5/5-4  [No such file or directory]
          usbip err: stub_driver.c: 197 (refresh_exported_devices) usbip_exported_device new  [No such file or directory]
          usbip dbg: stub_server.c: 142 (recv_request_import) found requested device 2-2
          usbip dbg: stub_driver.c: 317 (usbip_stub_export_device) write: 4

          with debug compiled usbip driver with usbipd on debug i get:
          Jan 19 11:16:07 cybercafe02 kernel: usbip: stub up
          Jan 19 11:16:08 cybercafe02 kernel: usb 5-4: reset high speed USB device using ehci_hcd and address 4
          Jan 19 11:16:08 cybercafe02 kernel: usbip: device reset
          ...
          Jan 19 11:16:30 cybercafe02 kernel: dev(4) ep(0) OUT CTL
          Jan 19 11:16:30 cybercafe02 kernel: /usr/src/usbip-0.1.4/drivers/2.6.19/stub_rx.c: set_configuration is not fully supported yet
          Jan 19 11:16:30 cybercafe02 kernel:
          Jan 19 11:16:30 cybercafe02 kernel: usbip: set_configuration: devnum 4 1
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 00 01 | 00 00 00 05 | 00 00 00 04 | 00 00 00 0c | 80 00 04 80 | 00 00 00 00 |
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 00 01 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 | a1 fe 00 00 |
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 01 00 |
          Jan 19 11:16:35 cybercafe02 kernel: usbip_xmit: received, osize 52 ret 52 size 0 total 52
          Jan 19 11:16:35 cybercafe02 kernel: dev(4) ep(0) IN CTL
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 00 01 | 00 00 00 05 | 00 00 00 04 | 00 00 00 0d | c0 00 84 00 | 00 00 00 00 |
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 00 1f | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 | a1 fe 00 00 |
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 01 00 |
          Jan 19 11:16:35 cybercafe02 kernel: usbip_xmit: received, osize 52 ret 52 size 0 total 52
          Jan 19 11:16:35 cybercafe02 kernel: dev(4) ep(1) OUT BLK
          Jan 19 11:16:35 cybercafe02 kernel:    55 53 42 43 | 01 00 00 00 | 24 00 00 00 | 80 00 06 12 | 00 00 00 24 | 00 00 00 00 |
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 00 00 | 00 00 00
          Jan 19 11:16:35 cybercafe02 kernel: usbip_xmit: received, osize 31 ret 31 size 0 total 31
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 00 01 | 00 00 00 05 | 00 00 00 04 | 00 00 00 0e | c0 00 84 80 | 00 00 00 01 |
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 00 24 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 |
          Jan 19 11:16:35 cybercafe02 kernel:    00 00 00 00 |
          Jan 19 11:16:35 cybercafe02 kernel: usbip_xmit: received, osize 52 ret 52 size 0 total 52
          Jan 19 11:16:35 cybercafe02 kernel: dev(4) ep(1) IN BLK
          Jan 19 11:16:40 cybercafe02 kernel:    00 00 00 02 | 00 00 00 05 | 00 00 00 04 | 00 00 00 0f | 00 00 00 00 | 00 00 00 0e |
          Jan 19 11:16:40 cybercafe02 kernel:    00 00 00 00 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00 |
          Jan 19 11:16:40 cybercafe02 kernel:    00 00 00 00 |
          Jan 19 11:16:40 cybercafe02 kernel: usbip_xmit: received, osize 52 ret 52 size 0 total 52
          Jan 19 11:16:40 cybercafe02 kernel: dev(0) ep(0) OUT ISO
          Jan 19 11:16:40 cybercafe02 kernel: usbip: unlink urb e31d1bc0
          Jan 19 11:16:40 cybercafe02 kernel: usbip: unlinked by a call of usb_unlink_urb()

          And the busid which is given by usbip client is just a lost pointer.

           
  • Timo Müller

    Timo Müller - 2010-01-07

    Hi
    I also have some problems using USBIP with externel storage. I'm quite new at sourceforge and don't know where else I can ask my questions I hope you can help me finding some solution and the answer where else I should ask my questions.
    But now to my problems: I run USBIP in Version 0.1.7.3 on 2 Debian Squeeze Systems with an i386 Kernel v.2.6.32. 
    USBIP works fine if I use my mouse for testing, but any time I mount an external storage with usbip on the client I get errors no minute later. Most of the time I see the MSG that the usb-cable may be bad. I tested it with three usb-sticks and one external HDD. Here are some parts of my system.log from my client.

    Jan  7 10:22:02 usbip2 kernel:   Initialized drm 1.1.0 20060810
    Jan  7 10:22:02 usbip2 kernel:  pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    Jan  7 10:22:02 usbip2 kernel:  pci 0000:00:02.0: setting latency timer to 64
    Jan  7 10:22:02 usbip2 kernel:  mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining
    Jan  7 10:22:02 usbip2 kernel:   MTRR allocation failed.  Graphics performance may suffer.
    Jan  7 10:22:02 usbip2 kernel:  pci 0000:00:02.0: irq 25 for MSI/MSI-X
    Jan  7 10:22:02 usbip2 kernel:   Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    Jan  7 10:22:02 usbip2 kernel:  eth0: no IPv6 routers present
    Jan  7 10:25:54 usbip2 anacron: Anacron 2.3 started on 2010-01-07
    Jan  7 10:25:54 usbip2 anacron: Normal exit (0 jobs run)
    Jan  7 10:25:54 usbip2 kernel:  CPU0 attaching NULL sched-domain.
    Jan  7 10:25:54 usbip2 kernel:  CPU1 attaching NULL sched-domain.
    Jan  7 10:25:54 usbip2 kernel:  CPU0 attaching sched-domain:
    Jan  7 10:25:54 usbip2 kernel:   domain 0: span 0-1 level MC
    Jan  7 10:25:54 usbip2 kernel:    groups: 0 1
    Jan  7 10:25:54 usbip2 kernel:  CPU1 attaching sched-domain:
    Jan  7 10:25:54 usbip2 kernel:   domain 0: span 0-1 level MC
    Jan  7 10:25:54 usbip2 kernel:    groups: 1 0
    Jan  7 10:29:27 usbip2 kernel:  usbip_common_mod: module is from the staging directory, the quality is unknown, you have been warned.
    Jan  7 10:29:27 usbip2 kernel:  usbip_common_mod: usbip common driver1.0
    Jan  7 10:29:27 usbip2 kernel:  vhci_hcd: module is from the staging directory, the quality is unknown, you have been warned.
    Jan  7 10:29:27 usbip2 kernel:  vhci_hcd: vhci_hcd, 1.0
    Jan  7 10:29:27 usbip2 kernel:  usbip: proving…
    Jan  7 10:29:27 usbip2 kernel:  vhci_hcd vhci_hcd: USB/IP Virtual Host Contoroller
    Jan  7 10:29:27 usbip2 kernel:  vhci_hcd vhci_hcd: new USB bus registered, assigned bus number 9
    Jan  7 10:29:27 usbip2 kernel:  usb usb9: New USB device found, idVendor=1d6b, idProduct=0002
    Jan  7 10:29:27 usbip2 kernel:  usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    Jan  7 10:29:27 usbip2 kernel:  usb usb9: Product: USB/IP Virtual Host Contoroller
    Jan  7 10:29:27 usbip2 kernel:  usb usb9: Manufacturer: Linux 2.6.32.1-1-usbip vhci_hcd
    Jan  7 10:29:27 usbip2 kernel:  usb usb9: SerialNumber: vhci_hcd
    Jan  7 10:29:27 usbip2 kernel:  usb usb9: configuration #1 chosen from 1 choice
    Jan  7 10:29:27 usbip2 kernel:  hub 9-0:1.0: USB hub found
    Jan  7 10:29:27 usbip2 kernel:  hub 9-0:1.0: 8 ports detected
    Jan  7 10:29:27 usbip2 kernel:  usbip: module is from the staging directory, the quality is unknown, you have been warned.
    Jan  7 10:29:27 usbip2 kernel:  usbcore: registered new interface driver usbip
    Jan  7 10:29:27 usbip2 kernel:  usbip:Stub Driver for USB/IP:1.0
    Jan  7 10:29:27 usbip2 usbipd: listen at :3240
    Jan  7 10:29:27 usbip2 usbipd: listen at :3240
    Jan  7 10:29:27 usbip2 usbipd: usbipd start (usbip 0.1.7 ($Id: stub_server.c 42 2007-09-07 12:07:51Z hirofuchi $))
    Jan  7 10:38:12 usbip2 kernel:  usbip: rhport(0) sockfd(3) devid(131074) speed(3)
    Jan  7 10:38:12 usbip2 kernel:  usbip: changed 1
    Jan  7 10:38:13 usbip2 kernel:  usbip: changed 0
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: new high speed USB device using vhci_hcd and address 2
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: new high speed USB device using vhci_hcd and address 3
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: new high speed USB device using vhci_hcd and address 4
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: SetAddress Request (4) to port 0
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: New USB device found, idVendor=0c0b, idProduct=b159
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: Product: DataStation maxi m.u
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: Manufacturer: Trekstor
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: SerialNumber: 0008C942
    Jan  7 10:38:13 usbip2 kernel:  usb 9-1: configuration #1 chosen from 1 choice
    Jan  7 10:38:13 usbip2 kernel:  usbip 9-1:1.0: this device 9-1 is not in match_busid table. skip!
    Jan  7 10:38:13 usbip2 kernel:  Initializing USB Mass Storage driver…
    Jan  7 10:38:13 usbip2 kernel:  scsi4 : SCSI emulation for USB Mass Storage devices
    Jan  7 10:38:13 usbip2 kernel:  usbcore: registered new interface driver usb-storage
    Jan  7 10:38:13 usbip2 kernel:  USB Mass Storage support registered.
    Jan  7 10:38:13 usbip2 kernel:  usb-storage: device found at 4
    Jan  7 10:38:13 usbip2 kernel:  usb-storage: waiting for device to settle before scanning
    Jan  7 10:38:18 usbip2 kernel:  usb-storage: device scan complete
    Jan  7 10:38:39 usbip2 kernel:  usbip: vhci_hcd: dequeue a urb f6412ac0
    Jan  7 10:38:39 usbip2 kernel:  vhci_hcd vhci_hcd: Unlink after no-IRQ?  Controller is probably using the wrong IRQ.
    Jan  7 10:38:39 usbip2 kernel:  usbip: vhci_hcd: device f66d9918 seems to be still connected
    Jan  7 10:38:39 usbip2 kernel:  usbip: unlink->seqnum 17
    Jan  7 10:38:39 usbip2 kernel:  usbip: -104
    Jan  7 10:38:42 usbip2 kernel:  hub 9-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    Jan  7 10:38:45 usbip2 kernel:  hub 9-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    Jan  7 10:38:48 usbip2 kernel:  hub 9-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    Jan  7 10:38:51 usbip2 kernel:  hub 9-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    Jan  7 10:38:51 usbip2 kernel:  usb 9-1: USB disconnect, address 4
    Jan  7 10:38:51 usbip2 kernel:  scsi 4:0:0:0: Device offlined - not ready after error recovery
    Jan  7 10:38:54 usbip2 kernel:  hub 9-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    Jan  7 10:38:57 usbip2 kernel:  hub 9-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    Jan  7 10:39:00 usbip2 kernel:  hub 9-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    Jan  7 10:39:03 usbip2 kernel:  hub 9-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    Jan  7 10:39:03 usbip2 kernel:  hub 9-0:1.0: unable to enumerate USB device on port 1
    Jan  7 11:00:33 usbip2 kernel:  BUG: unable to handle kernel paging request at 00190f5b
    Jan  7 11:00:33 usbip2 kernel:  IP:  strnlen+0x6/0x16
    Jan  7 11:00:33 usbip2 kernel:  *pde = 00000000
    Jan  7 11:00:33 usbip2 kernel:  Oops: 0000  SMP
    Jan  7 11:00:33 usbip2 kernel:  last sysfs file: /sys/devices/platform/vhci_hcd/status
    Jan  7 11:00:33 usbip2 kernel:  Modules linked in: usb_storage usbip(C) vhci_hcd(C) usbip_common_mod(C) i915 drm_kms_helper drm i2c_algo_bit video output ppdev lp sco bridge stp bnep rfcomm l2cap crc16 bluetooth rfkill acpi_cpufreq cpufreq_powersave cpufreq_conservative cpufreq_stats cpufreq_userspace binfmt_misc fuse loop firewire_sbp2 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event parport_pc snd_seq i2c_i801 snd_timer parport i2c_core asus_atk0110 psmouse snd_seq_device processor pcspkr serio_raw evdev snd soundcore snd_page_alloc ext3 jbd mbcache sg sr_mod sd_mod crc_t10dif cdrom usbhid hid ata_generic uhci_hcd ehci_hcd ata_piix libata firewire_ohci firewire_core crc_itu_t intel_agp e1000e scsi_mod ide_pci_generic button ide_core usbcore nls_base agpgart thermal fan thermal_sys
    Jan  7 11:00:33 usbip2 kernel: 
    Jan  7 11:00:33 usbip2 kernel:  Pid: 2797, comm: usbip Tainted: G         C (2.6.32.1-1-usbip #1) P5E-VM DO
    Jan  7 11:00:33 usbip2 kernel:  EIP: 0060: EFLAGS: 00010297 CPU: 1
    Jan  7 11:00:33 usbip2 kernel:  EIP is at strnlen+0x6/0x16
    Jan  7 11:00:33 usbip2 kernel:  EAX: 00190f5b EBX: ffffffff ECX: 00190f5b EDX: fffffffe
    Jan  7 11:00:33 usbip2 kernel:  ESI: f63bfeec EDI: f5164057 EBP: 00190f5b ESP: f63bfe68
    Jan  7 11:00:33 usbip2 kernel:   DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    Jan  7 11:00:33 usbip2 kernel:  Process usbip (pid: 2797, ti=f63be000 task=f50735c0 task.ti=f63be000)
    Jan  7 11:00:33 usbip2 kernel:  Stack:
    Jan  7 11:00:33 usbip2 kernel:   c022d74e ffffffff 00000000 f63bff14 f63bfeec f63bfea0 00000002 c022e230
    Jan  7 11:00:33 usbip2 kernel:  <0> 00000004 00000000 ffffffff 0000000a ffffffff ffffffff f5164057 f63bfed4
    Jan  7 11:00:33 usbip2 kernel:  <0> c022e12e f5164057 f63bfee0 c022e12e f5164046 f63bfeec f81fb071 0ae9bfa8
    Jan  7 11:00:33 usbip2 kernel:  Call Trace:
    Jan  7 11:00:33 usbip2 kernel:    ? string+0x33/0x81
    Jan  7 11:00:33 usbip2 kernel:    ? vsnprintf+0x194/0x372
    Jan  7 11:00:33 usbip2 kernel:    ? vsnprintf+0x92/0x372
    Jan  7 11:00:33 usbip2 kernel:    ? vsnprintf+0x92/0x372
    Jan  7 11:00:33 usbip2 kernel:    ? sprintf+0x17/0x19
    Jan  7 11:00:33 usbip2 kernel:    ? show_status+0xb1/0x105
    Jan  7 11:00:33 usbip2 kernel:    ? show_status+0x0/0x105
    Jan  7 11:00:33 usbip2 kernel:    ? dev_attr_show+0x16/0x32
    Jan  7 11:00:33 usbip2 kernel:    ? sysfs_read_file+0x8b/0xea
    Jan  7 11:00:33 usbip2 kernel:    ? sysfs_read_file+0x0/0xea
    Jan  7 11:00:33 usbip2 kernel:    ? vfs_read+0x7b/0xd3
    Jan  7 11:00:33 usbip2 kernel:    ? sys_read+0x3c/0x63
    Jan  7 11:00:33 usbip2 kernel:    ? sysenter_do_call+0x12/0x28
    Jan  7 11:00:33 usbip2 kernel:  Code: 0e 89 c7 89 d0 f2 ae 74 05 bf 01 00 00 00 4f 89 f8 5f c3 85 c9 57 89 c7 89 d0 74 05 f2 ae 75 01 4f 89 f8 5f c3 89 c1 89 c8 eb 06 <80> 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 c3 90 55 89 d5 57 56
    Jan  7 11:00:33 usbip2 kernel:  EIP:  strnlen+0x6/0x16 SS:ESP 0068:f63bfe68
    Jan  7 11:00:33 usbip2 kernel:  CR2: 0000000000190f5b
    Jan  7 11:00:33 usbip2 kernel:  ----
    Jan  7 11:00:48 usbip2 kerneloops: Submitted 1 kernel oopses to www.kerneloops.org
    Jan  7 11:00:48 usbip2 kerneloops: kerneloops.org: oops is posted as http://www.kerneloops.org/submitresult.php?number=1092223

    May someone help me with these errors. Did I make some mistake or is this some known bug with a workaround, …….

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks