Messages in this thread | | | Date | Sat, 27 Jun 2020 15:13:28 +0500 | From | Roman Mamedov <> | Subject | Re: ath9k broken [was: Linux 5.7.3] |
| |
On Thu, 25 Jun 2020 06:57:13 +0200 Jiri Slaby <jirislaby@kernel.org> 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
| |