Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1269768ybt; Sat, 27 Jun 2020 03:20:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzCzyKoitjjK+CpPqF3U7ox2GRsilxJJuLMbUrtcxardCNNWG4lxC5Wfpr8Jshh3HuuSubB X-Received: by 2002:a17:906:5799:: with SMTP id k25mr6406506ejq.540.1593253243007; Sat, 27 Jun 2020 03:20:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593253243; cv=none; d=google.com; s=arc-20160816; b=Kju6FHOTBuZfqpoA1oCoROst12bpk6O4fUmCJ63lK59ywrAAiVH7vkurUl9J0EIoA5 kiH7E/zFb8/FwROewflHWwnqViHxQrIXVslTBnkHWNBRCgubyAI1xXil8HIwFGJ8b9IX 1jE53bPQoTaSdKn62gTQpjkJIKgH2+Mf4D6pPNUYKM9t0m6bIoSdgkeJ21ZcsecBqfdp VDzSAzGeTzs5rn/fnguXYfnMxuL4vZUpLrPYpFk0wDw6oPI4cGlOttrg82JqxZoaY4XP /MTPGdYxm3ry82HgUb7AZLG0tGHQ+Je32311fHgMqqbLhG4ngB01kxogEg3KeHvRSmj3 BZXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=BjTZJMq5AhJgB6BbqJEMNJst3DFub8xsWhmGprJXqQM=; b=X7ja3pkjNCYoVairNcI/5+lB0oyyn5fFPf+yweHUz1A08JedqNk8/MNRb0w0u0GOOX Hmok4Ac38tVY0PPVMaDEbx49rmKdNeWMfzyijE9D8+uXJB98x6AdS+e2PCAfJkbh8814 qZEDYpTy/R0PxHTdzcbOCeK8NOtu3brOc4ShVVCXykXqkLm/g5oudPnHdk6MgZNw7bpw z94F5XNFeyxMzfYCdmb4bJGCE+2UO77Bh3j1Il75HwMhe4WHxxoOMy3cuzMR0/gu0+i2 Mn2a+qrocpEjeCi1kYHGw+r5zHG8c61xE5FytuP1VEaK20NEnXEEyTD19vVixDzfiPNn 3OTA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l23si4013301ejb.322.2020.06.27.03.20.19; Sat, 27 Jun 2020 03:20:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726444AbgF0KUI (ORCPT + 99 others); Sat, 27 Jun 2020 06:20:08 -0400 Received: from rin.romanrm.net ([51.158.148.128]:54094 "EHLO rin.romanrm.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726175AbgF0KUG (ORCPT ); Sat, 27 Jun 2020 06:20:06 -0400 X-Greylist: delayed 392 seconds by postgrey-1.27 at vger.kernel.org; Sat, 27 Jun 2020 06:20:03 EDT Received: from natsu (unknown [IPv6:fd39::e99e:8f1b:cfc9:ccb8]) by rin.romanrm.net (Postfix) with SMTP id 91C8E42D; Sat, 27 Jun 2020 10:13:28 +0000 (UTC) Date: Sat, 27 Jun 2020 15:13:28 +0500 From: Roman Mamedov To: Jiri Slaby Cc: Gabriel C , Greg Kroah-Hartman , LKML , Andrew Morton , Linus Torvalds , stable , lwn@lwn.net, angrypenguinpoland@gmail.com, Qiujun Huang , ath9k-devel@qca.qualcomm.com, "linux-wireless@vger.kernel.org" Subject: Re: ath9k broken [was: Linux 5.7.3] Message-ID: <20200627151328.1611acbc@natsu> In-Reply-To: References: <1592410366125160@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 25 Jun 2020 06:57:13 +0200 Jiri Slaby wrote: > I fail to see how the commit could cause an issue like this. Is this > really reproducibly broken with the commit and irreproducible without > it? As it looks like a USB/wiring problem: > usb 1-2: USB disconnect, device number 2 > ath: phy0: Reading Magic # failed > ath: phy0: Unable to initialize hardware; initialization status: -5 > ... > usb 1-2: device descriptor read/64, error -110 > usb 1-2: device descriptor read/64, error -71 > > Ccing ath9k maintainers too. Note that this has been previously reported in: https://bugzilla.kernel.org/show_bug.cgi?id=208251 and confirmed by several people on various stable series and the mainline that the referenced commit is indeed causing the problem. I don't get the "device descriptor read" errors though, my dmesg is posted on the bug report, it just says "ath9k_htc: Failed to initialize the device". > > I don't have so much info about the HW, besides a dmesg showing the > > phy breaking. > > I also added the reporter to CC too. > > > > https://gist.github.com/AngryPenguinPL/1e545f0da3c2339e443b9e5044fcccea > > > > If you need more info, please let me know and I'll try my best to get > > it as fast as possible for you. -- With respect, Roman