linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Nick Morrow <morrownr@gmail.com>
Cc: nbd@nbd.name, ryder.lee@mediatek.com, shayne.chen@mediatek.com,
	Sean Wang <sean.wang@mediatek.com>,
	deren.wu@mediatek.com, linux-wireless@vger.kernel.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [bug report} wifi: mt76: mt7612u/mt7610u - 6.1.x hard locking systems
Date: Tue, 27 Dec 2022 13:05:19 +0100	[thread overview]
Message-ID: <Y6rffzYy5hgIQKSE@localhost.localdomain> (raw)
In-Reply-To: <CAFktD2fbpUv9X5MY1jozyXoxvNXW=4OfaJ3B1KcZtdrBfiG4NA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]

> > > 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,
> >
> > Hi Nick,
> >
> > Can you please try the patch below?
> > https://patchwork.kernel.org/project/linux-wireless/patch/20221217085624.52077-1-nbd@nbd.name/
> >
> > Regards,
> > Lorenzo
> 
> Lorenzo,
> 
> Today, I downloaded kernel 6.1.1, applied the above patch and
> compiled. Once installed, I tested with an Alfa ACM mt7612u based
> adapter. I no longer see the problem. No system lockups at all. iperf3
> is showing a consistent performance of around 387 Mb/s. dmesg is
> clean. The patch appears to have fixed the issue. I can also test with
> a mt7610u based adapter if you think it is necessary but since that
> patch was not to mt76, I decided testing only with the mt7612u adapter
> was probably good enough. Let me know if there is anything else I can
> do.

no, it is not necessary to test with mt7610u as well. Thanks for testing.

Regards,
Lorenzo

> 
> Nick
> https://github.com/morrownr/USB-WiFi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2022-12-27 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23 21:36 [bug report} wifi: mt76: mt7612u/mt7610u - 6.1.x hard locking systems Nick Morrow
2022-12-23 23:20 ` Lorenzo Bianconi
2022-12-26 23:26   ` Nick Morrow
2022-12-27 12:05     ` Lorenzo Bianconi [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=Y6rffzYy5hgIQKSE@localhost.localdomain \
    --to=lorenzo@kernel.org \
    --cc=deren.wu@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=morrownr@gmail.com \
    --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).