From: Roman Mamedov <rm@romanrm.net>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Gabriel C <nix.or.die@googlemail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
stable <stable@vger.kernel.org>,
lwn@lwn.net, angrypenguinpoland@gmail.com,
Qiujun Huang <hqjagain@gmail.com>,
ath9k-devel@qca.qualcomm.com,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k broken [was: Linux 5.7.3]
Date: Sat, 27 Jun 2020 15:13:28 +0500 [thread overview]
Message-ID: <20200627151328.1611acbc@natsu> (raw)
In-Reply-To: <b7993e83-1df7-0c93-f6dd-dba9dc10e27a@kernel.org>
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
prev parent reply other threads:[~2020-06-27 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 16:12 Linux 5.7.3 Greg Kroah-Hartman
2020-06-17 16:12 ` Greg Kroah-Hartman
2020-06-24 22:05 ` Gabriel C
2020-06-25 4:57 ` ath9k broken [was: Linux 5.7.3] Jiri Slaby
2020-06-25 10:48 ` Gabriel C
2020-06-25 10:52 ` Gabriel C
2020-06-26 11:48 ` Gabriel C
2020-06-26 13:39 ` Greg Kroah-Hartman
2020-06-26 13:51 ` Gabriel C
2020-06-26 14:40 ` Gabriel C
2020-07-07 14:11 ` Greg Kroah-Hartman
2020-07-07 20:20 ` Viktor Jägersküpper
2020-07-15 15:13 ` Kalle Valo
2020-07-16 8:15 ` Viktor Jägersküpper
2020-07-16 9:02 ` Kalle Valo
2020-06-27 10:13 ` Roman Mamedov [this message]
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=20200627151328.1611acbc@natsu \
--to=rm@romanrm.net \
--cc=akpm@linux-foundation.org \
--cc=angrypenguinpoland@gmail.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hqjagain@gmail.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=nix.or.die@googlemail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.