From: Nick Morrow <morrownr@gmail.com>
To: nbd@nbd.name, Lorenzo Bianconi <lorenzo@kernel.org>,
ryder.lee@mediatek.com, shayne.chen@mediatek.com,
Sean Wang <sean.wang@mediatek.com>,
deren.wu@mediatek.com
Cc: linux-wireless@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: [bug report} wifi: mt76: mt7612u/mt7610u - 6.1.x hard locking systems
Date: Fri, 23 Dec 2022 15:36:24 -0600 [thread overview]
Message-ID: <CAFktD2fRnSbNgWRRoGbQzG5_Mw7=zFJKTVBHS_3D+mNUYcv9hQ@mail.gmail.com> (raw)
Starting with kernel 6.1 rc1, mt7612u and mt7610u are hard locking
systems when connection is established. From a report this morning:
"So I'm using a MT7610U based adapter and updated to 6.1.1 in Arch
Linux and it's a complete lockup a few seconds after connecting as
other people have said, I'll use the LTS kernel (5.15) in the
meanwhile but this is probably going to get a lot of people that use
distros with newer kernels."
Background: Problem first discovered with kernel 6.1 rc1. Bug report
was seen on linux-wireless around the rc5 timeframe. This is an
additional bug report.
I don't think additional info is needed as I have tested on several
distros with various RC's of 6.1 and the problem is 100% reproducible
and unavoidable. This is a show stopper bug and will result in
widespread reports as distros upgrade to kernel 6.1.
Regards,
Nick
https://github.com/morrownr/USB-WiFi
next reply other threads:[~2022-12-23 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 21:36 Nick Morrow [this message]
2022-12-23 23:20 ` [bug report} wifi: mt76: mt7612u/mt7610u - 6.1.x hard locking systems Lorenzo Bianconi
2022-12-26 23:26 ` Nick Morrow
2022-12-27 12:05 ` Lorenzo Bianconi
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='CAFktD2fRnSbNgWRRoGbQzG5_Mw7=zFJKTVBHS_3D+mNUYcv9hQ@mail.gmail.com' \
--to=morrownr@gmail.com \
--cc=deren.wu@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).