From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] mnt reform trackball stops responding
Date: Tue, 01 Aug 2023 01:43:36 +0200 [thread overview]
Message-ID: <B33234730F14035C0FF030F67F04824A@felloff.net> (raw)
In-Reply-To: <9963074F9746325AED1D776B228FAF11@gaff.inri.net>
i pushed a commit this weekend...
i could reproduce the trackball and the keyboard stop working
when i plug a external mouse in the middle usb port.
basically the keyboard and trackball just get a single
transaction error from where they never recover.
it seems to be a quirk of the internal usb hub or electrical
issue for me. it never happens with the port to the front,
which is on the same hub (shared with keyboard and trackball)...
there should be zero difference...
also works fine if i use a powered hub.
in any case, i found a issue in the way nusb/kb tries to
handle these kind of errors that would not work with xhci.
basically, we now immediately issue a port reset when
we encounter a error reading the interrupt endpoints,
which makes usbd detach the device and then attempt
a new attach.
i cannot avoid this glitch, but at least it recovers quickly.
--
cinap
next prev parent reply other threads:[~2023-08-01 0:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 3:19 sl
2023-07-19 3:32 ` sl
2023-07-20 16:36 ` Philip Silva
2023-07-20 18:59 ` Stanley Lieber
2023-07-21 2:46 ` sl
2023-07-22 16:31 ` Philip Silva
2023-07-22 17:24 ` Stanley Lieber
2023-07-26 19:51 ` Sigrid Solveig Haflínudóttir
2023-07-26 23:39 ` cinap_lenrek
2023-07-27 15:10 ` sl
2023-07-27 16:32 ` Sigrid Solveig Haflínudóttir
2023-07-26 23:48 ` [9front] 9front Boots Into "No Config" -- The Most Bizarre Error Of Them All Jay F. Shachter
2023-07-27 0:55 ` Jacob Moody
2023-07-27 0:25 ` [9front] mnt reform trackball stops responding sl
2023-07-31 23:43 ` cinap_lenrek [this message]
2023-08-02 1:17 ` sl
2023-08-02 3:03 ` ieliedonge
2023-08-02 3:36 ` sl
2023-08-02 20:52 ` cinap_lenrek
2023-07-31 23:48 ` cinap_lenrek
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=B33234730F14035C0FF030F67F04824A@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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).