From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] linux-4.8-rcX: ath9k traceback
Date: Fri, 02 Sep 2016 17:21:36 -0000 [thread overview]
Message-ID: <1472831794.2773.1.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <87eg5338b5.fsf@purkki.adurom.net>
On Thu, 2016-09-01 at 19:15 +0300, Kalle Valo wrote:
> Mimi Zohar <zohar@linux.vnet.ibm.com> writes:
>
> > There weren't any problems on linux-4.7 kernels. I'm getting the
> > following traceback on linux-4.8-rc1/-rc4 kernels. Let me know if you
> > need any additional information.
> >
> > [ 64.006529] WARNING: CPU: 3 PID: 94 at drivers/net/wireless/ath/ath9k/beacon.c:642 ath9k_beacon_config+0x12c/0x140 [ath9k]
>
> This should fix it:
>
> ath9k: fix client mode beacon configuration
>
> https://git.kernel.org/cgit/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=05860bed491b114a9f2d7a4f6e09fb02c0b69056
Yep, that resolved the problem. Thanks!
Mimi
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: QCA ath9k Development <ath9k-devel@qca.qualcomm.com>,
ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: linux-4.8-rcX: ath9k traceback
Date: Fri, 02 Sep 2016 11:56:34 -0400 [thread overview]
Message-ID: <1472831794.2773.1.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <87eg5338b5.fsf@purkki.adurom.net>
On Thu, 2016-09-01 at 19:15 +0300, Kalle Valo wrote:
> Mimi Zohar <zohar@linux.vnet.ibm.com> writes:
>
> > There weren't any problems on linux-4.7 kernels. I'm getting the
> > following traceback on linux-4.8-rc1/-rc4 kernels. Let me know if you
> > need any additional information.
> >
> > [ 64.006529] WARNING: CPU: 3 PID: 94 at drivers/net/wireless/ath/ath9k/beacon.c:642 ath9k_beacon_config+0x12c/0x140 [ath9k]
>
> This should fix it:
>
> ath9k: fix client mode beacon configuration
>
> https://git.kernel.org/cgit/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=05860bed491b114a9f2d7a4f6e09fb02c0b69056
Yep, that resolved the problem. Thanks!
Mimi
next prev parent reply other threads:[~2016-09-02 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 22:24 linux-4.8-rcX: ath9k traceback Mimi Zohar
2016-09-01 1:02 ` [ath9k-devel] " Mimi Zohar
2016-09-01 16:15 ` Kalle Valo
2016-09-01 16:15 ` Kalle Valo
2016-09-02 15:56 ` Mimi Zohar [this message]
2016-09-02 17:21 ` [ath9k-devel] " Mimi Zohar
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=1472831794.2773.1.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=ath9k-devel@lists.ath9k.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.