linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emil Karlson <jekarl@iki.fi>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: Ap mode regression in linux-5.3-rc1 in rt2800usb
Date: Mon, 19 Aug 2019 09:06:19 +0300	[thread overview]
Message-ID: <20190819090619.54f523cb@lettuce> (raw)
In-Reply-To: <20190816093302.GA2158@redhat.com>

Hi

On Fri, 16 Aug 2019 11:33:02 +0200
Stanislaw Gruszka <sgruszka@redhat.com> wrote:

> > > > After upgrading my ap running rt2800usb to linux-5.3-rc1 I
> > > > noticed an unusual problem of not being able to connect to my
> > > > ap with my android devices (nexus7/flo and nexus5x/bullhead),
> > > > from tcpdump it seemed ap was receiving packets from the
> > > > android devices after successful association, but android
> > > > devices were not seeing the dhcp replies.
> > > > 
> > > > I reverted drivers/net/wireless/ralink to the state it is in
> > > > v5.2.8 and android clients can connect again normally. I did not
> > > > explicitly set watchdog parameter to any value.
> > 
> > > Most suspicious are 710e6cc1595e and 41a531ffa4c5 .
> > 
> > It seems to me that reverting only
> > 710e6cc1595e25378c4b9977f7a8b4ad4a72a109
> > allows all my android devices to successfully connect to the
> > internet.
> 
> Please test attached patch as proposed fix for
> 710e6cc1595e25378c4b9977f7a8b4ad4a72a109 and report back. Thanks.

After some testing it seems attached patch fixes the regression with no
observed negative side effects. Thanks.

Best Regards
-Emil

      reply	other threads:[~2019-08-19  6:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190813215000.6cc27ade@lettuce>
2019-08-14  8:50 ` Ap mode regression in linux-5.3-rc1 in rt2800usb Stanislaw Gruszka
2019-08-16  8:00   ` Emil Karlson
2019-08-16  9:33     ` Stanislaw Gruszka
2019-08-19  6:06       ` Emil Karlson [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=20190819090619.54f523cb@lettuce \
    --to=jekarl@iki.fi \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.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).