From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8A5E4C47094 for ; Mon, 7 Jun 2021 19:06:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6C03361130 for ; Mon, 7 Jun 2021 19:06:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231228AbhFGTI3 (ORCPT ); Mon, 7 Jun 2021 15:08:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:42896 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230264AbhFGTI2 (ORCPT ); Mon, 7 Jun 2021 15:08:28 -0400 Received: by mail.kernel.org (Postfix) with ESMTPS id 348E861130 for ; Mon, 7 Jun 2021 19:06:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1623092797; bh=lq+8BVFB4esSK47jgU5fdxJ9uxNuCK9sLZN0Tt01WUs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dJGtyoZx1QXMoQCfG+xqq1H8d6MzIFo5kItV8MtadpB8UNBglGzNP8cu8d8cUifUE Jl4C6ywryiokYmFqJzvPGQYdIBUVIs8caOwdqpN2uqwc90HskwVgAqeQKDwkPxf6bm YnS6S2WoO0pspE/MsA4j3GexuCi8ErgkB76GjzRhjrwa4HzBmlbaRqP9NrANJrt+ZB SmY9XWhPY7iD99+MiQ5TajZC3t/hGr/cWOXdnWTKrppwfSBL6L0hc1faWa3WF+l1/F oyBr3n78m2DVsobkwYR1NypvBanYwH7KM9jUw7p4vh9CZHfKxPlsrbITjmCbOeTRk2 Y87ySxc/SJcfQ== From: bugzilla-daemon@bugzilla.kernel.org To: linux-usb@vger.kernel.org Subject: [Bug 212955] Possible kernel regression USB2 (not USB3) port EDIROL UA-101 (in USB 1.1 mode, not USB2) error -110 Date: Mon, 07 Jun 2021 19:06:36 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo drivers_usb@kernel-bugs.kernel.org X-Bugzilla-Product: Drivers X-Bugzilla-Component: USB X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jaffa225man@gmail.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: drivers_usb@kernel-bugs.kernel.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=3D212955 --- Comment #23 from Lucas Endres (jaffa225man@gmail.com) --- (In reply to Alan Stern from comment #22) > Using two different drivers would definitely explain the different patter= ns > of communication with the device in your two usbmon traces. >=20 > But it doesn't explain why, with one of the drivers, the device seems to > stop responding when used with EHCI (and works okay with xHCI!). Maybe t= his > is caused by a bug in the device's firmware. It that's true, changing the > communication pattern might work around the problem. Sorry, but here's another pertinent factor that I should have mentioned ear= lier if I haven't: It could very well be a bug in the UA-101's firmware, since if I connect an audible input and watch it on the UA-101's builtin levels meter (with it already on), I think it does freeze. The levels remain when the input is unplugged, after plugging in USB while running a nonworking commit. Thanks for the insight! I suppose I should start comparing the code to each module, since I think that's what you're suggesting. --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=