From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mga09.intel.com ([134.134.136.24]:61054 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752463Ab1GYVDa (ORCPT ); Mon, 25 Jul 2011 17:03:30 -0400 Subject: Re: [PATCH] iwlagn: check for !priv->txq in iwlagn_wait_tx_queue_empty From: wwguy To: Keith Packard Cc: Intel Linux Wireless , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" In-Reply-To: References: <1311622702-4807-1-git-send-email-keithp@keithp.com> <1311621715.5579.138.camel@wwguy-huron> Content-Type: text/plain; charset="UTF-8" Date: Mon, 25 Jul 2011 13:59:07 -0700 Message-ID: <1311627547.13973.2.camel@wwguy-ubuntu> (sfid-20110725_230346_421069_293687E3) Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, 2011-07-25 at 13:03 -0700, Keith Packard wrote: > On Mon, 25 Jul 2011 12:21:55 -0700, "Guy, Wey-Yi" wrote: > > > but why you need it?, "start device" call will fail if can not allocate > > priv->txq > > The device is down, so start_device was never called. At least, that's > my assumption -- I've got the wireless device 'disabled' in > NetworkManager. > the iwlagn_wait_tx_queue_empty() function only can be call from either "flush" operation or from debugfs. I agree it is a problem if call from debugfs. did you actually see the problem when it is not from debugfs(). there is a recent patch in mac80211 to make sure do not call "flush" is not needed. Thanks Wey