linux-kernel - Re: REGRESSION for RT2561/RT61 in 2.6.32

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 8 Dec 2009 15:48:13 +0100
From:	Gertjan van Wingerde <gwingerde@...il.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Ivo van Doorn <IvDoorn@...il.com>, linux-wireless@...r.kernel.org,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: REGRESSION for RT2561/RT61 in 2.6.32

On Tue, Dec 8, 2009 at 3:27 PM, Alan Stern <stern@...land.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/