From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] linux-next: Tree for May 30
Date: Mon, 30 May 2016 18:47:51 -0000 [thread overview]
Message-ID: <574C4851.9090201@gmail.com> (raw)
In-Reply-To: <20160530132225.4d297678@canb.auug.org.au>
On Monday 30 May 2016 08:52 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160527:
Hi All,
I have just built and booted with next-20160530 and my dmesg is full of
warnings from ath9k. Last kernel tested was v4.6 and there was no
problem with that.
The traces are like:
Call Trace:
[<ffffffff813b8ddc>] dump_stack+0x63/0x87
[<ffffffff8107a331>] __warn+0xd1/0xf0
[<ffffffff8107a41d>] warn_slowpath_null+0x1d/0x20
[<ffffffffc095801f>] ath9k_hw_gpio_request+0x6f/0x320 [ath9k_hw]
[<ffffffffc095ac24>] ath9k_hw_reset+0xfe4/0x12e0 [ath9k_hw]
[<ffffffffc03d45d4>] ath_reset_internal+0x104/0x1f0 [ath9k]
[<ffffffffc03d46fd>] ath_reset+0x3d/0x60 [ath9k]
[<ffffffffc03dd1c6>] ath_chanctx_set_channel+0x1b6/0x300 [ath9k]
[<ffffffffc03d36b6>] ath9k_config+0xc6/0x1f0 [ath9k]
[<ffffffff817d6e92>] ? mutex_lock+0x12/0x2f
[<ffffffffc05a7923>] ieee80211_hw_config+0x63/0x350 [mac80211]
[<ffffffffc05b3041>] ieee80211_scan_work+0x161/0x480 [mac80211]
[<ffffffff81093183>] process_one_work+0x153/0x3f0
[<ffffffff8109393b>] worker_thread+0x12b/0x4b0
[<ffffffff81093810>] ? rescuer_thread+0x340/0x340
[<ffffffff81099129>] kthread+0xc9/0xe0
[<ffffffff817d8f1f>] ret_from_fork+0x1f/0x40
[<ffffffff81099060>] ? kthread_park+0x60/0x60
---[ end trace 27eb5094a52869ea ]---
Call Trace:
[<ffffffff813b8ddc>] dump_stack+0x63/0x87
[<ffffffff8107a331>] __warn+0xd1/0xf0
[<ffffffff8107a41d>] warn_slowpath_null+0x1d/0x20
[<ffffffffc0956b19>] ath9k_hw_gpio_get+0x1a9/0x1b0 [ath9k_hw]
[<ffffffffc03d03e4>] ath9k_rfkill_poll_state+0x34/0x60 [ath9k]
[<ffffffffc05c4b53>] ieee80211_rfkill_poll+0x33/0x40 [mac80211]
[<ffffffffc049d65a>] cfg80211_rfkill_poll+0x2a/0xc0 [cfg80211]
[<ffffffff817c5514>] rfkill_poll+0x24/0x50
[<ffffffff81093183>] process_one_work+0x153/0x3f0
[<ffffffff8109393b>] worker_thread+0x12b/0x4b0
[<ffffffff81093810>] ? rescuer_thread+0x340/0x340
[<ffffffff81099129>] kthread+0xc9/0xe0
[<ffffffff817d8f1f>] ret_from_fork+0x1f/0x40
[<ffffffff81099060>] ? kthread_park+0x60/0x60
---[ end trace 27eb5094a5286a3d ]---
If it is a known problem then great.. else i can debug and see what the
problem is. There are only few patches added for GPIO, so should not be
a problem to find out what is causing the error.
Regards
Sudip
WARNING: multiple messages have this Message-ID (diff)
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Kalle Valo <kvalo@codeaurora.org>,
QCA ath9k Development <ath9k-devel@qca.qualcomm.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for May 30
Date: Mon, 30 May 2016 19:34:01 +0530 [thread overview]
Message-ID: <574C4851.9090201@gmail.com> (raw)
In-Reply-To: <20160530132225.4d297678@canb.auug.org.au>
On Monday 30 May 2016 08:52 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160527:
Hi All,
I have just built and booted with next-20160530 and my dmesg is full of
warnings from ath9k. Last kernel tested was v4.6 and there was no
problem with that.
The traces are like:
Call Trace:
[<ffffffff813b8ddc>] dump_stack+0x63/0x87
[<ffffffff8107a331>] __warn+0xd1/0xf0
[<ffffffff8107a41d>] warn_slowpath_null+0x1d/0x20
[<ffffffffc095801f>] ath9k_hw_gpio_request+0x6f/0x320 [ath9k_hw]
[<ffffffffc095ac24>] ath9k_hw_reset+0xfe4/0x12e0 [ath9k_hw]
[<ffffffffc03d45d4>] ath_reset_internal+0x104/0x1f0 [ath9k]
[<ffffffffc03d46fd>] ath_reset+0x3d/0x60 [ath9k]
[<ffffffffc03dd1c6>] ath_chanctx_set_channel+0x1b6/0x300 [ath9k]
[<ffffffffc03d36b6>] ath9k_config+0xc6/0x1f0 [ath9k]
[<ffffffff817d6e92>] ? mutex_lock+0x12/0x2f
[<ffffffffc05a7923>] ieee80211_hw_config+0x63/0x350 [mac80211]
[<ffffffffc05b3041>] ieee80211_scan_work+0x161/0x480 [mac80211]
[<ffffffff81093183>] process_one_work+0x153/0x3f0
[<ffffffff8109393b>] worker_thread+0x12b/0x4b0
[<ffffffff81093810>] ? rescuer_thread+0x340/0x340
[<ffffffff81099129>] kthread+0xc9/0xe0
[<ffffffff817d8f1f>] ret_from_fork+0x1f/0x40
[<ffffffff81099060>] ? kthread_park+0x60/0x60
---[ end trace 27eb5094a52869ea ]---
Call Trace:
[<ffffffff813b8ddc>] dump_stack+0x63/0x87
[<ffffffff8107a331>] __warn+0xd1/0xf0
[<ffffffff8107a41d>] warn_slowpath_null+0x1d/0x20
[<ffffffffc0956b19>] ath9k_hw_gpio_get+0x1a9/0x1b0 [ath9k_hw]
[<ffffffffc03d03e4>] ath9k_rfkill_poll_state+0x34/0x60 [ath9k]
[<ffffffffc05c4b53>] ieee80211_rfkill_poll+0x33/0x40 [mac80211]
[<ffffffffc049d65a>] cfg80211_rfkill_poll+0x2a/0xc0 [cfg80211]
[<ffffffff817c5514>] rfkill_poll+0x24/0x50
[<ffffffff81093183>] process_one_work+0x153/0x3f0
[<ffffffff8109393b>] worker_thread+0x12b/0x4b0
[<ffffffff81093810>] ? rescuer_thread+0x340/0x340
[<ffffffff81099129>] kthread+0xc9/0xe0
[<ffffffff817d8f1f>] ret_from_fork+0x1f/0x40
[<ffffffff81099060>] ? kthread_park+0x60/0x60
---[ end trace 27eb5094a5286a3d ]---
If it is a known problem then great.. else i can debug and see what the
problem is. There are only few patches added for GPIO, so should not be
a problem to find out what is causing the error.
Regards
Sudip
WARNING: multiple messages have this Message-ID (diff)
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Kalle Valo <kvalo@codeaurora.org>,
QCA ath9k Development <ath9k-devel@qca.qualcomm.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for May 30
Date: Mon, 30 May 2016 19:34:01 +0530 [thread overview]
Message-ID: <574C4851.9090201@gmail.com> (raw)
In-Reply-To: <20160530132225.4d297678@canb.auug.org.au>
On Monday 30 May 2016 08:52 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160527:
Hi All,
I have just built and booted with next-20160530 and my dmesg is full of
warnings from ath9k. Last kernel tested was v4.6 and there was no
problem with that.
The traces are like:
Call Trace:
[<ffffffff813b8ddc>] dump_stack+0x63/0x87
[<ffffffff8107a331>] __warn+0xd1/0xf0
[<ffffffff8107a41d>] warn_slowpath_null+0x1d/0x20
[<ffffffffc095801f>] ath9k_hw_gpio_request+0x6f/0x320 [ath9k_hw]
[<ffffffffc095ac24>] ath9k_hw_reset+0xfe4/0x12e0 [ath9k_hw]
[<ffffffffc03d45d4>] ath_reset_internal+0x104/0x1f0 [ath9k]
[<ffffffffc03d46fd>] ath_reset+0x3d/0x60 [ath9k]
[<ffffffffc03dd1c6>] ath_chanctx_set_channel+0x1b6/0x300 [ath9k]
[<ffffffffc03d36b6>] ath9k_config+0xc6/0x1f0 [ath9k]
[<ffffffff817d6e92>] ? mutex_lock+0x12/0x2f
[<ffffffffc05a7923>] ieee80211_hw_config+0x63/0x350 [mac80211]
[<ffffffffc05b3041>] ieee80211_scan_work+0x161/0x480 [mac80211]
[<ffffffff81093183>] process_one_work+0x153/0x3f0
[<ffffffff8109393b>] worker_thread+0x12b/0x4b0
[<ffffffff81093810>] ? rescuer_thread+0x340/0x340
[<ffffffff81099129>] kthread+0xc9/0xe0
[<ffffffff817d8f1f>] ret_from_fork+0x1f/0x40
[<ffffffff81099060>] ? kthread_park+0x60/0x60
---[ end trace 27eb5094a52869ea ]---
Call Trace:
[<ffffffff813b8ddc>] dump_stack+0x63/0x87
[<ffffffff8107a331>] __warn+0xd1/0xf0
[<ffffffff8107a41d>] warn_slowpath_null+0x1d/0x20
[<ffffffffc0956b19>] ath9k_hw_gpio_get+0x1a9/0x1b0 [ath9k_hw]
[<ffffffffc03d03e4>] ath9k_rfkill_poll_state+0x34/0x60 [ath9k]
[<ffffffffc05c4b53>] ieee80211_rfkill_poll+0x33/0x40 [mac80211]
[<ffffffffc049d65a>] cfg80211_rfkill_poll+0x2a/0xc0 [cfg80211]
[<ffffffff817c5514>] rfkill_poll+0x24/0x50
[<ffffffff81093183>] process_one_work+0x153/0x3f0
[<ffffffff8109393b>] worker_thread+0x12b/0x4b0
[<ffffffff81093810>] ? rescuer_thread+0x340/0x340
[<ffffffff81099129>] kthread+0xc9/0xe0
[<ffffffff817d8f1f>] ret_from_fork+0x1f/0x40
[<ffffffff81099060>] ? kthread_park+0x60/0x60
---[ end trace 27eb5094a5286a3d ]---
If it is a known problem then great.. else i can debug and see what the
problem is. There are only few patches added for GPIO, so should not be
a problem to find out what is causing the error.
Regards
Sudip
next prev parent reply other threads:[~2016-05-30 18:47 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 3:22 linux-next: Tree for May 30 Stephen Rothwell
2016-05-30 14:04 ` Sudip Mukherjee [this message]
2016-05-30 18:47 ` [ath9k-devel] " Sudip Mukherjee
2016-05-30 14:04 ` Sudip Mukherjee
2016-05-31 7:31 ` [ath9k-devel] ath9k gpio request Kalle Valo
2016-05-31 7:31 ` Kalle Valo
2016-05-31 7:31 ` Kalle Valo
2016-05-31 7:31 ` Kalle Valo
2016-05-31 7:35 ` Sudip Mukherjee
2016-05-31 12:22 ` [ath9k-devel] " Sudip Mukherjee
2016-05-31 7:35 ` Sudip Mukherjee
2016-06-01 6:54 ` Pan, Miaoqing
2016-06-01 7:01 ` [ath9k-devel] " Pan, Miaoqing
2016-06-01 6:54 ` Pan, Miaoqing
2016-06-01 11:12 ` Sudip Mukherjee
2016-06-01 15:43 ` [ath9k-devel] " Sudip Mukherjee
2016-06-01 11:12 ` Sudip Mukherjee
2016-06-01 12:18 ` Sudip Mukherjee
2016-06-01 16:49 ` [ath9k-devel] " Sudip Mukherjee
2016-06-01 12:18 ` Sudip Mukherjee
[not found] ` <574ED297.4080004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-02 8:02 ` Pan, Miaoqing
2016-06-02 8:03 ` [ath9k-devel] " Pan, Miaoqing
2016-06-02 8:02 ` Pan, Miaoqing
2016-06-02 8:02 ` Pan, Miaoqing
2016-06-02 9:01 ` [ath9k-devel] " Janusz Dziedzic
2016-06-02 9:01 ` Janusz Dziedzic
2016-06-02 9:01 ` Janusz Dziedzic
2016-06-02 11:39 ` Sudip Mukherjee
2016-06-02 16:09 ` [ath9k-devel] " Sudip Mukherjee
2016-06-02 11:39 ` Sudip Mukherjee
2016-06-03 5:33 ` [ath9k-devel] " Kalle Valo
2016-06-03 5:33 ` Kalle Valo
2016-06-03 5:33 ` Kalle Valo
2016-06-03 5:33 ` Kalle Valo
2016-06-03 5:49 ` Pan, Miaoqing
2016-06-03 5:49 ` [ath9k-devel] " Pan, Miaoqing
2016-06-03 5:49 ` Pan, Miaoqing
2016-06-04 14:37 ` [ath9k-devel] " Kalle Valo
2016-06-04 14:37 ` Kalle Valo
2016-06-04 14:37 ` Kalle Valo
2016-06-04 14:37 ` Kalle Valo
2016-06-04 14:37 ` Kalle Valo
2016-06-05 17:40 ` Sudip Mukherjee
2016-06-05 17:52 ` [ath9k-devel] " Sudip Mukherjee
2016-06-05 17:40 ` Sudip Mukherjee
2016-06-07 11:43 ` [ath9k-devel] " Kalle Valo
2016-06-07 11:43 ` Kalle Valo
2016-06-07 11:43 ` Kalle Valo
2016-06-07 11:43 ` Kalle Valo
2016-06-07 11:43 ` Kalle Valo
2016-06-06 1:51 ` Pan, Miaoqing
2016-06-06 1:51 ` [ath9k-devel] " Pan, Miaoqing
2016-06-06 1:51 ` Pan, Miaoqing
2016-06-06 1:51 ` Pan, Miaoqing
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=574C4851.9090201@gmail.com \
--to=sudipm.mukherjee@gmail.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.