linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Ivo van Doorn <IvDoorn@gmail.com>,
	linux-wireless@vger.kernel.org,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: REGRESSION for RT2561/RT61 in 2.6.32
Date: Wed, 09 Dec 2009 22:57:59 +0100	[thread overview]
Message-ID: <4B201D67.8000607@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0912090940030.4120-100000@iolanthe.rowland.org>

On 12/09/09 15:41, Alan Stern wrote:
> On Tue, 8 Dec 2009, Gertjan van Wingerde wrote:
> 
>> Hmm, the stack overrun seems to be generated as part of the
>> Alt-SysRq-* handling, not of any rt61pci handling.
>>
>> I noticed in the Alt-SysRq-T output that powersaving is enabled. We've
>> seen some strange behaviour on this, so could you disable that with:
>>
>> iwconfig wlan0 power off
>>
>> or run a kernel in which CONFIG_CFG80211_DEFAULT_PS is disabled.
>>
>> Maybe that will fix the problem we are seeing?
> 
> It did indeed!  Thank you very much.  If you need a testbed to figure 
> out what's wrong with the power-saving code, just ask.
> 

Great!

Thanks for testing and confirming.

I'll disable powersaving for rt2x00 for now.

And then to find the bugs in there before enabling it again :-(

---
Gertjan.

  reply	other threads:[~2009-12-09 21:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 22:12 REGRESSION for RT2561/RT61 in 2.6.32 Alan Stern
2009-12-06 22:22 ` Otavio Salvador
2009-12-07  2:11   ` Alan Stern
2009-12-07 22:03 ` Gertjan van Wingerde
2009-12-08 14:27   ` Alan Stern
2009-12-08 14:48     ` Gertjan van Wingerde
2009-12-09 14:41       ` Alan Stern
2009-12-09 21:57         ` Gertjan van Wingerde [this message]
2009-12-09 22:33           ` Otavio Salvador
2010-01-11 14:54           ` REGRESSION for RT2561/RT61 in 2.6.33 Alan Stern
2010-01-11 15:11             ` Johannes Berg
2010-01-11 15:46               ` Alan Stern

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=4B201D67.8000607@gmail.com \
    --to=gwingerde@gmail.com \
    --cc=IvDoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 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).