libreport version: 2.0.7
cmdline: BOOT_IMAGE=/vmlinuz-3.1.4-1.fc16.x86_64 root=UUID=24c17115-49bc-41ad-9e75-46e5b2dd8d08 ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
reason: WARNING: at drivers/net/wireless/iwlwifi/iwl-agn-lib.c:1766 iwlagn_set_rxon_chain+0x113/0x233 [iwlagn]()
time: Sat 10 Dec 2011 01:06:10 AM EET
backtrace: Text file, 2579 bytes
smolt_data: Text file, 2572 bytes
Created attachment 544782 [details]
Created attachment 544783 [details]
This is fixed in upstream 3.3-rc1 by:
Author: Wey-Yi Guy <email@example.com>
Date: Thu Nov 10 06:55:04 2011 -0800
iwlagn: check for SMPS mode
This commit is not CCed to stable, not sure if it worth to post it there, or maybe just apply it to fedora.
(In reply to comment #3)
> This is fixed in upstream 3.3-rc1 by:
> commit b2ccccdca46273c7b321ecf5041c362cd950da20
> Author: Wey-Yi Guy <firstname.lastname@example.org>
> Date: Thu Nov 10 06:55:04 2011 -0800
> iwlagn: check for SMPS mode
> This commit is not CCed to stable, not sure if it worth to post it there, or
> maybe just apply it to fedora.
I would suggest having Wey-Yi send it to stable if possible. I'll backport it to F16 today, but having it in the upstream tree would benefit more than just Fedora.
Patch applied in Fedora git. Should be in the next update submitted.
Just posted to -stable as well:
kernel-3.2.1-3.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.2.1-3.fc16'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
*** Bug 771954 has been marked as a duplicate of this bug. ***
kernel-3.2.1-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 785406 has been marked as a duplicate of this bug. ***
*** Bug 773073 has been marked as a duplicate of this bug. ***