From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 210801] TopSeed Technology Corp. eHome Infrared Transceiver spams log with Error: urb status = -71
Date: Thu, 07 Jan 2021 14:02:32 +0000 [thread overview]
Message-ID: <bug-210801-208809-jFiHs4J6vZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210801-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210801
--- Comment #5 from Hans-Peter Jansen (hpj@urpla.net) ---
Okay, reverting 528222d853f92 does the trick.
My RC is working fine again for VDR, I can pull and plug the RC controller, VDR
is complaining, but after restarting VDR, all is fine again.
This is the kernel log of pulling and plugging the RC controller:
```
[ 4.903556] rc rc0: lirc_dev: driver mceusb registered at minor = 0, raw IR
receiver, raw IR transmitter
[ 5.084059] mceusb 5-10.4:1.0: long-range (0x1) receiver active
[ 5.127510] mceusb 5-10.4:1.0: Registered TopSeed Technology Corp. eHome
Infrared Transceiver with mce emulator interface version 1
[ 5.127512] mceusb 5-10.4:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x1
active)
[ 5.127530] usbcore: registered new interface driver mceusb
[ 1537.725685] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1537.733681] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1537.741680] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1537.749683] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1537.757670] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1537.765684] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1537.773662] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1537.781659] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1537.789654] mceusb 5-10.4:1.0: Error: urb status = -71
[ 1540.361827] rc rc0: lirc_dev: driver mceusb registered at minor = 0, raw IR
receiver, raw IR transmitter
[ 1540.541769] mceusb 5-10.4:1.0: long-range (0x1) receiver active
[ 1540.585785] mceusb 5-10.4:1.0: Registered TopSeed Technology Corp. eHome
Infrared Transceiver with mce emulator interface version 1
[ 1540.585787] mceusb 5-10.4:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x1
active)
```
With 528222d853f92 applied, I wasn't able to recover at all, I had to stop VDR
and pulling the RC controller in order to stop flooding the log with the urb
status = -71 errors.
Sean, do you have any idea, what could have changed with 528222d853f92
resulting in this behavior?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-01-07 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 16:19 [Bug 210801] New: TopSeed Technology Corp. eHome Infrared Transceiver spams log with Error: urb status = -71 bugzilla-daemon
2020-12-21 6:46 ` [Bug 210801] " bugzilla-daemon
2020-12-21 17:09 ` bugzilla-daemon
2021-01-06 15:34 ` bugzilla-daemon
2021-01-07 14:02 ` bugzilla-daemon [this message]
2021-01-07 16:13 ` bugzilla-daemon
2021-01-14 14:17 ` bugzilla-daemon
2021-01-14 15:41 ` bugzilla-daemon
2021-02-04 15:06 ` bugzilla-daemon
2021-02-05 18:08 ` 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-210801-208809-jFiHs4J6vZ@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).