linux-kernel - Re: [Bug #13943] WARNING: at net/mac80211/mlme.c:2292 with ath5k

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]

Message-ID: <b637ec0b0910030636h66d13f21m31f1a894505b2067@mail.gmail.com>
Date:	Sat, 3 Oct 2009 15:36:01 +0200
From:	Fabio Comolli <fabio.comolli@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	"Luis R. Rodriguez" <mcgrof@...il.com>
Subject: Re: [Bug #13943] WARNING: at net/mac80211/mlme.c:2292 with ath5k

Hi Rafael.

On Fri, Oct 2, 2009 at 11:42 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Friday 02 October 2009, Fabio Comolli wrote:
>> Hi.
>>
>> On Fri, Oct 2, 2009 at 7:17 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
>> > On Friday 02 October 2009, Fabio Comolli wrote:
>> >> Hi.
>> >> I suppose this is still valid. I had to work around it by rfkill-ing
>> >> the device during the suspend process and reenabling at resume time.
>> >
>> > Thanks for the update.
>> >
>> >> I can try to reproduce it with 2.6.31.1 if you want it.
>> >
>> > In fact I'm more interested in whether or not it's still present in the Linus'
>> > tree.
>> >
>>
>> Well, I just tried 2.6.32-rc1-git3 and I have to say that it's mostly
>> useless with my eeepc. The warning didn't show up after resume but it
>> was impossible to reassociate with my AP and after some tentative the
>> screen went blank.
>>
>> I was able to poweroff the netbook using the power button but I'm a
>> little scared to try again.
>
> It shouldn't kill the system cold dead, so as long as you have your data
> backed up, you can do some debugging IMHO.
>
>> Maybe I'll try with -rc3 or something.
>
> I guess you should report the issues you have at the moment.  Then, it's
> actually more likely that someone will take care of fixing them.
>

OK. This is what I've been able to come up with so far:

* with 2.6.31.x the warning shows up more or less every suspend-to-ram cycle;
* with 2.6.32-rc the warning never shows up;
* with 2.6.31.x when the warning shows up wifi is unusable until rfkill cycle;
* whith 2.6.32-rc after suspend-to-ram cycle wifi is unusable and
rfkill does not cure it unless I rfkill it off - suspend-to-ram -
resume - rfkill it on. This seems to work.

When wifi does not work in 2.6.32-rc the messages show:

---------------------------------------------
[   49.647233] wlan0: direct probe to AP xx:xx:xx:xx:xx:xx (try 1)
[   49.649234] wlan0: direct probe responded
[   49.649244] wlan0: authenticate with AP xx:xx:xx:xx:xx:xx (try 1)
[   49.650546] wlan0: authenticated
[   49.650581] wlan0: associate with AP xx:xx:xx:xx:xx:xx (try 1)
[   49.652183] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x451
status=12 aid=1)
[   49.652190] wlan0: AP denied association (code=12)
---------------------------------------------

The script I feed to pm-utils to have wifi work across the
suspend-to-ram cycle is just:

---------------------------------------------
#!/bin/sh
RFKILL=`basename /sys/devices/platform/eeepc/rfkill/*`

case "$1" in
	hibernate|suspend)
		cat /sys/devices/platform/eeepc/rfkill/$RFKILL/state > /tmp/suspend
		echo 0 > /sys/devices/platform/eeepc/rfkill/$RFKILL/state
		;;
	thaw|resume)
		cat /tmp/suspend > /sys/devices/platform/eeepc/rfkill/$RFKILL/state
		;;
	*) exit $NA
		;;
esac
---------------------------------------------

I can confirm that with 32-rc sometimes the screen flickers badly
after resume, for example running a simple dmesg command. However,
nothing is written in the logs, neither messages nor Xorg.0.log.
Chipset is i915.

Hope this helps. Please note that git is not an option for me on this machine.

> Thanks,
> Rafael

Regards,
Fabio


> --
> 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/
>
--
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/