[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <574D3EAA.3060102@gmail.com>
Date: Tue, 31 May 2016 13:05:06 +0530
From: Sudip Mukherjee <sudipm.mukherjee@...il.com>
To: Kalle Valo <kvalo@...eaurora.org>
CC: Stephen Rothwell <sfr@...b.auug.org.au>,
QCA ath9k Development <ath9k-devel@....qualcomm.com>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org, ath9k-devel@...ts.ath9k.org,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Miaoqing Pan <miaoqing@...eaurora.org>
Subject: Re: ath9k gpio request
On Tuesday 31 May 2016 01:01 PM, Kalle Valo wrote:
> (Changing subject to a more descriptive one, was "Re: linux-next: Tree
> for May 30")
>
> Sudip Mukherjee <sudipm.mukherjee@...il.com> writes:
>
>> 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.
>>
<snip>
> The traces look incomplete to me, is there anything more before the
> "Call Trace:" line? Full unedited logs are usually the best.
sure, its attached. those two warnings are recursively going on and
there is nothing else left in dmesg to see what started it.
Regards
Sudip
View attachment "dmesg.txt" of type "text/plain" (220458 bytes)
Powered by blists - more mailing lists