From: "John W. Linville" <linville@tuxdriver.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
linux-wireless@vger.kernel.org
Subject: Re: suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug
Date: Sat, 7 Jan 2012 16:47:25 -0500 [thread overview]
Message-ID: <20120107214724.GA7746@tuxdriver.com> (raw)
In-Reply-To: <CANUX_P22vWv+XenOLs7Smf2P7CpPCVperF5JagS2JyCCpHXKOQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2012-01-07 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 10:27 suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug Toralf Förster
2012-01-07 20:55 ` Emmanuel Grumbach
2012-01-07 21:04 ` Emmanuel Grumbach
2012-01-07 21:47 ` John W. Linville
2012-01-07 21:47 ` John W. Linville [this message]
2012-01-08 6:01 ` Emmanuel Grumbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120107214724.GA7746@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.