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: Tue, 8 Dec 2009 15:48:13 +0100 [thread overview]
Message-ID: <14add3d10912080648w5610d533h2cf08a9d79fa48c1@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0912080922160.3046-200000@iolanthe.rowland.org>
On Tue, Dec 8, 2009 at 3:27 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Mon, 7 Dec 2009, Gertjan van Wingerde wrote:
>
>> > While the system is hung, Alt-SysRq-keys still work but nothing else
>> > shows up when I type (using a VT console, not X). However I don't know
>> > what debugging to do or what to look for.
>> >
>> > Under 2.6.31 everything works okay.
>> >
>>
>> Hmmm, that's odd. I haven't seen any other reports on this (on full system hangs that is).
>>
>> It would be very hard to figure out what is going wrong without any form of logging of
>> an oops or something. Is there any way you can find out if any oops information is present?
>
> There is no oops. The system just stops responding to keystrokes other
> than Alt-SysRq-*.
>
>> What does Alt-SysRq-l tell us, what are the CPU's doing when the system is hung?
>
> Unfortunately Alt-SysRq-l wasn't very helpful. The output is below
> (captured using a serial console), starting from when I configured the
> wireless interface. For thoroughness I have also attached the output
> of Alt-SysRq-T in single-user mode, but it doesn't seem to contain
> anything striking.
>
> Could the problem be connected with CONFIG_4KSTACKS (which was enabled
> in this kernel)?
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?
Other than that I have no ideas on what is happening here.
---
Gertjan.
next prev parent reply other threads:[~2009-12-08 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 22:12 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 [this message]
2009-12-09 14:41 ` Alan Stern
2009-12-09 21:57 ` Gertjan van Wingerde
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=14add3d10912080648w5610d533h2cf08a9d79fa48c1@mail.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
all inboxes | Powered by JetHome®