Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:59431 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751275Ab2AGWBA (ORCPT ); Sat, 7 Jan 2012 17:01:00 -0500 Date: Sat, 7 Jan 2012 16:47:25 -0500 From: "John W. Linville" To: Emmanuel Grumbach Cc: Toralf =?iso-8859-1?Q?F=F6rster?= , linux-wireless@vger.kernel.org Subject: Re: suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug Message-ID: <20120107214724.GA7746@tuxdriver.com> (sfid-20120107_230128_399044_551F8011) References: <201201071127.06717.toralf.foerster@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sat, Jan 07, 2012 at 10:55:30PM +0200, Emmanuel Grumbach wrote: > > If I choosed 0x43ff my syslog message files exploded - and I'd like to trouble > > shoot a problem with my wlan at a ThinkPad T400 (iwlwifi, 5100 AGN controler). > > The symptoms are that 1-2 times in a hour the network stops working without > > any message in /var/log/messages (kernel 3.0.x, 3.1.x, 3.2.0 tested). > > > > Thanks for any advice > > -- > > For this kind of issues I added the TX_QUEUES debug flags, but I just > checked and it is not in 3.2. It is in John's wireless tree though. It > is bit 31: debug=0x80000000 > > BTW - John, I have tried many times to understand all this, but stupid > me, couldn't ever make it. How come a patch is in wireless which in my > understanding (probably wrong) is supposed to feed the current rc > cycle (meaning the 3.2-rcX which just ended) and not be in 3.2 stable > release ? Sorry for the ignorance... We are betwen the release and the next -rc1. Right now everything in wireless is the stuff that was in wireless-next last week. Hth! John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.