* suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug @ 2012-01-07 10:27 Toralf Förster 2012-01-07 20:55 ` Emmanuel Grumbach 0 siblings, 1 reply; 6+ messages in thread From: Toralf Förster @ 2012-01-07 10:27 UTC (permalink / raw) To: linux-wireless 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 -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug 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 0 siblings, 2 replies; 6+ messages in thread From: Emmanuel Grumbach @ 2012-01-07 20:55 UTC (permalink / raw) To: Toralf Förster; +Cc: linux-wireless > 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... thanks ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug 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 1 sibling, 1 reply; 6+ messages in thread From: Emmanuel Grumbach @ 2012-01-07 21:04 UTC (permalink / raw) To: Toralf Förster; +Cc: linux-wireless On Sat, Jan 7, 2012 at 22:55, Emmanuel Grumbach <egrumbach@gmail.com> 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... > Or maybe the wireless tree has already be recreated on top of Linus's tree (through Dave's tree) after he merged everything ? ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug 2012-01-07 21:04 ` Emmanuel Grumbach @ 2012-01-07 21:47 ` John W. Linville 0 siblings, 0 replies; 6+ messages in thread From: John W. Linville @ 2012-01-07 21:47 UTC (permalink / raw) To: Emmanuel Grumbach; +Cc: Toralf Förster, linux-wireless On Sat, Jan 07, 2012 at 11:04:11PM +0200, Emmanuel Grumbach wrote: > On Sat, Jan 7, 2012 at 22:55, Emmanuel Grumbach <egrumbach@gmail.com> 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... > > > Or maybe the wireless tree has already be recreated on top of Linus's > tree (through Dave's tree) after he merged everything ? Right, that. :-) -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug 2012-01-07 20:55 ` Emmanuel Grumbach 2012-01-07 21:04 ` Emmanuel Grumbach @ 2012-01-07 21:47 ` John W. Linville 2012-01-08 6:01 ` Emmanuel Grumbach 1 sibling, 1 reply; 6+ messages in thread From: John W. Linville @ 2012-01-07 21:47 UTC (permalink / raw) To: Emmanuel Grumbach; +Cc: Toralf Förster, linux-wireless 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: suggestion for a reasonable value for /sys/module/iwlwifi/parameters/debug 2012-01-07 21:47 ` John W. Linville @ 2012-01-08 6:01 ` Emmanuel Grumbach 0 siblings, 0 replies; 6+ messages in thread From: Emmanuel Grumbach @ 2012-01-08 6:01 UTC (permalink / raw) To: John W. Linville; +Cc: Toralf Förster, linux-wireless On Sat, Jan 7, 2012 at 23:47, John W. Linville <linville@tuxdriver.com> wrote: > 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! > yup, it does. Thanks Toralf, back to you. There are quite a few fixes that will be included in the next stable release (3.3) in about 3 months. I really believe these fixes can help you. You can also try to disable 11n to see if it helps. To do so, add 11n_disable as a module parameter. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-01-08 6:01 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2012-01-08 6:01 ` Emmanuel Grumbach
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).