From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28955 invoked from network); 1 Aug 2023 00:05:00 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 1 Aug 2023 00:05:00 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 9front; Mon Jul 31 20:03:26 -0400 2023 Message-ID: Date: Tue, 01 Aug 2023 01:43:36 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: <9963074F9746325AED1D776B228FAF11@gaff.inri.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: immutable social persistence-scale event configuration-aware database layer Subject: Re: [9front] mnt reform trackball stops responding Reply-To: 9front@9front.org Precedence: bulk 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