Return-path: Received: from mail-pd0-f171.google.com ([209.85.192.171]:50860 "EHLO mail-pd0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751071AbaJZJKp convert rfc822-to-8bit (ORCPT ); Sun, 26 Oct 2014 05:10:45 -0400 Received: by mail-pd0-f171.google.com with SMTP id r10so3859739pdi.30 for ; Sun, 26 Oct 2014 02:10:44 -0700 (PDT) Date: Sun, 26 Oct 2014 18:10:39 +0900 From: Okhwan Lee To: Michal Kazior Cc: linux-wireless , "=?utf-8?Q?ath10k=40lists.infradead.org?=" Message-ID: (sfid-20141026_101049_418186_AD6F3D9C) In-Reply-To: References: Subject: Re: Change channel bandwidth without iw command MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Sender: linux-wireless-owner@vger.kernel.org List-ID:  Hi,  Thanks for your help. We just disable some functions step by step.  Then we can conclude that wait_for_completion_timeout makes kernel panic.  We guess that monitor vdev stopping after reception of a Action frame requires more time than the case when using iw command.  Instead of wait_for_completion_timeout, we also use alternative function, wait_for_completion (uses maximum timeout value),  but the panic is still there. We don’t have the expert on kernel memory debugging from now on.  We have to study more how to handle it.  Again, thank you.   Okhwan Lee Sent with Airmail 켜짐 2014년 10월 24일 에서 오후 8:38:44, Michal Kazior (michal.kazior@tieto.com(mailto:michal.kazior@tieto.com)) 작성됨: >