From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sudip Mukherjee Subject: Re: linux-next: Tree for May 30 Date: Mon, 30 May 2016 19:34:01 +0530 Message-ID: <574C4851.9090201@gmail.com> References: <20160530132225.4d297678@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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" To: Stephen Rothwell , Kalle Valo , QCA ath9k Development Return-path: In-Reply-To: <20160530132225.4d297678@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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: [] dump_stack+0x63/0x87 [] __warn+0xd1/0xf0 [] warn_slowpath_null+0x1d/0x20 [] ath9k_hw_gpio_request+0x6f/0x320 [ath9k_hw] [] ath9k_hw_reset+0xfe4/0x12e0 [ath9k_hw] [] ath_reset_internal+0x104/0x1f0 [ath9k] [] ath_reset+0x3d/0x60 [ath9k] [] ath_chanctx_set_channel+0x1b6/0x300 [ath9k] [] ath9k_config+0xc6/0x1f0 [ath9k] [] ? mutex_lock+0x12/0x2f [] ieee80211_hw_config+0x63/0x350 [mac80211] [] ieee80211_scan_work+0x161/0x480 [mac80211] [] process_one_work+0x153/0x3f0 [] worker_thread+0x12b/0x4b0 [] ? rescuer_thread+0x340/0x340 [] kthread+0xc9/0xe0 [] ret_from_fork+0x1f/0x40 [] ? kthread_park+0x60/0x60 ---[ end trace 27eb5094a52869ea ]--- Call Trace: [] dump_stack+0x63/0x87 [] __warn+0xd1/0xf0 [] warn_slowpath_null+0x1d/0x20 [] ath9k_hw_gpio_get+0x1a9/0x1b0 [ath9k_hw] [] ath9k_rfkill_poll_state+0x34/0x60 [ath9k] [] ieee80211_rfkill_poll+0x33/0x40 [mac80211] [] cfg80211_rfkill_poll+0x2a/0xc0 [cfg80211] [] rfkill_poll+0x24/0x50 [] process_one_work+0x153/0x3f0 [] worker_thread+0x12b/0x4b0 [] ? rescuer_thread+0x340/0x340 [] kthread+0xc9/0xe0 [] ret_from_fork+0x1f/0x40 [] ? 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