Return-path: Received: from mail-wg0-f49.google.com ([74.125.82.49]:49262 "EHLO mail-wg0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753878AbaJXLin convert rfc822-to-8bit (ORCPT ); Fri, 24 Oct 2014 07:38:43 -0400 Received: by mail-wg0-f49.google.com with SMTP id x12so875802wgg.8 for ; Fri, 24 Oct 2014 04:38:42 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 24 Oct 2014 13:38:42 +0200 Message-ID: (sfid-20141024_133847_729364_7DDB4BEB) Subject: Re: Change channel bandwidth without iw command From: Michal Kazior To: Okhwan Lee Cc: linux-wireless , "ath10k@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 24 October 2014 13:30, Okhwan Lee wrote: > Hi, > > This linked images are the printed error messages when the kernel is in panic. > http://www.mwnl.snu.ac.kr/~ohlee/1.jpg > http://www.mwnl.snu.ac.kr/~ohlee/2.jpg Thanks. Panic doesn't seem to include anything directly related to ath10k which suggests this may be some nasty memory corruption issue. You might want to enable memory debugging when building kernel (Kernel Hacking) - hopefully it'll get some extra info before the panic. How did you come to a conclusion that ath10k's monitor vdev stopping and wait_for_completion_timeout() are involved? Michał