linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208267] New: usbip broken with latest kernels?
Date: Sun, 21 Jun 2020 13:57:09 +0000	[thread overview]
Message-ID: <bug-208267-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=208267

            Bug ID: 208267
           Summary: usbip broken with latest kernels?
           Product: Drivers
           Version: 2.5
    Kernel Version: Linux t420 5.7.4-arch1-1 #1 SMP PREEMPT Thu, 18 Jun
                    2020 16:01:07 +0000 x86_64 GNU/Linux
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: forum@docmax.my.to
        Regression: No

[root@t420]: /home/docmax># usbip list -l
 - busid 1-1.1 (0572:6831)
   Conexant Systems (Rockwell), Inc. : DVBSky S960 DVB-S2 tuner (0572:6831)

 - busid 1-1.2.3 (057e:0306)
   Nintendo Co., Ltd : Wii Remote Controller RVL-003 (057e:0306)

 - busid 1-1.2.4 (045e:0719)
   Microsoft Corp. : Xbox 360 Wireless Adapter (045e:0719)

 - busid 1-1.3 (147e:2016)
   Upek : Biometric Touchchip/Touchstrip Fingerprint Sensor (147e:2016)

 - busid 1-1.4 (0a5c:217f)
   Broadcom Corp. : BCM2045B (BDC-2.1) (0a5c:217f)

 - busid 1-1.6 (04f2:b221)
   Chicony Electronics Co., Ltd : integrated camera (04f2:b221)

 - busid 4-1 (152d:0567)
   JMicron Technology Corp. / JMicron USA Technology Corp. : JMS567 SATA 6Gb/s
bridge (152d:0567)

 - busid 4-2 (152d:0567)
   JMicron Technology Corp. / JMicron USA Technology Corp. : JMS567 SATA 6Gb/s
bridge (152d:0567)

 - busid 3-1.2 (174c:5136)
   ASMedia Technology Inc. : ASM1053 SATA 3Gb/s bridge (174c:5136)

[root@t420]: /home/docmax># usbip -d bind -b 1-1.2.4
usbip: debug: usbip.c:129:[run_command] running command: `bind'
usbip: debug: sysfs_utils.c:24:[write_sysfs_attribute] error writing to
attribute /sys/bus/usb/drivers/usbip-host/bind
usbip: error: error binding device 1-1.2.4 to driver: No such device
usbip: error: could not bind device to usbip-host

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2020-06-21 13:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 13:57 bugzilla-daemon [this message]
2020-06-21 14:52 ` [Bug 208267] usbip broken with latest kernels? bugzilla-daemon
2020-06-21 15:20   ` Greg KH
2020-06-21 15:20 ` bugzilla-daemon
2020-06-21 17:03 ` bugzilla-daemon
2020-06-22  8:04   ` Greg KH
2020-06-22  8:04 ` bugzilla-daemon
2020-06-28 22:48 ` bugzilla-daemon
2020-07-19 21:29 ` bugzilla-daemon
2020-07-20  6:57   ` Greg KH
2020-07-20  6:57 ` bugzilla-daemon
2020-07-20  7:15 ` bugzilla-daemon
2020-07-21 11:38 ` bugzilla-daemon
2020-08-27 20:37 ` bugzilla-daemon
2020-08-28 20:46 ` bugzilla-daemon
2020-09-01 10:41 ` bugzilla-daemon
2020-09-01 14:06   ` Greg KH
2020-09-01 14:06 ` bugzilla-daemon
2020-09-01 14:18 ` bugzilla-daemon
2020-09-01 14:52   ` Greg KH
2020-09-01 14:52 ` bugzilla-daemon
2020-09-05 12:56 ` bugzilla-daemon
2020-09-06 10:07 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-208267-208809@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).