linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: lolilolicon <lolilolicon@gmail.com>, ath9k-devel@qca.qualcomm.com
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
	linville@tuxdriver.com
Subject: Re: Bug: USB wifi card TL-WN722N (AR9271, ath9k_htc) fails to get DHCP lease
Date: Sat, 28 Jun 2014 19:37:12 -0500	[thread overview]
Message-ID: <53AF5FB8.3060505@lwfinger.net> (raw)
In-Reply-To: <CAMtVo_MxCfV7MWC+ksWc=PJM0KEHDUVuCMpg0NCWBW8EeLU5Jw@mail.gmail.com>

On 06/28/2014 04:17 PM, lolilolicon wrote:
> This bug was introduced in merge commit 88daf80 (if I did the bisect correctly).
>
> A workaround around the bug is to set the ath9k_htc param nohwcrypt=1.
>
> The difference in the journal/log between good and bad is that in the
> presence of the bug, dhcpcd would time out soliciting a DHCP lease.
> Some other users report that they're getting an IP, but the connection
> is very slow.
>
> Also reported elsewhere:
> https://bugs.archlinux.org/task/40905
> https://bugzilla.kernel.org/show_bug.cgi?id=78581
>
> Apologies if I messed up anything (sending to the wrong ML/people,
> inadequate info, etc.)
> If you need anything else, just ask.

Something went wrong in your bisection. Commit 88daf80 is a merge commit and is 
unlikely to be the bad one. You might try a checkout of b080e04 and try it to 
see if it is bad or good. That is the first non-merge commit before 88daf80.

Larry


  reply	other threads:[~2014-06-29  0:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28 21:17 Bug: USB wifi card TL-WN722N (AR9271, ath9k_htc) fails to get DHCP lease lolilolicon
2014-06-29  0:37 ` Larry Finger [this message]
2014-06-29  9:32   ` lolilolicon
2014-06-29 17:08     ` Larry Finger
2014-06-29 21:08       ` lolilolicon
2014-06-30 14:20         ` John W. Linville
2014-06-30 17:24           ` [ath9k-devel] " Oleksij Rempel
2014-07-01  4:41             ` Nathan Schulte

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=53AF5FB8.3060505@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lolilolicon@gmail.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).