From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from alexa-out.qualcomm.com ([129.46.98.28]) by bombadil.infradead.org with esmtps (Exim 4.87 #1 (Red Hat Linux)) id 1eJCo3-0004kR-9w for ath10k@lists.infradead.org; Mon, 27 Nov 2017 06:22:51 +0000 From: Kalle Valo Subject: Re: Kernel panic hosting 5Ghz AP Date: Mon, 27 Nov 2017 06:21:47 +0000 Message-ID: <87h8tg6y2t.fsf@kamboji.qca.qualcomm.com> References: <87zi7da458.fsf@kamboji.qca.qualcomm.com> In-Reply-To: (Konstantin Bogomolov's message of "Thu, 23 Nov 2017 11:41:54 -0500") Content-Language: en-US MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Konstantin Bogomolov Cc: "ath10k@lists.infradead.org" Konstantin Bogomolov writes: > Hello Kalle, > > The panic happens after hostapd outputs "ACS-STARTED". Usually, the > first attempt for me to start hostapd fails to create the AP (I think > this is a separate issue with the 5Ghz AP), but the second attempt > always initiates a panic on Debian 4.9 drivers. > > I don't think this is a regression, because I saw the same behaviour > on a custom 4.1 kernel. I have also tried using backported drivers > from 4.12.0 to both 4.1 and 4.9, where the panic was also reproducible > on the second hostapd attempt, but didn't happen every time as it does > on Debian 4.9. So the AP did work on some occasions using the > backports, but the panic still happened very frequently. Sadly I don't > have logs at this time using those backports. > > I'll try and reproduce this using a recent kernel and let you know the results. Also try without ACS (meaning specify a channel mannually hostapd config file) just to see if the crash is ACS related. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k