Description of problem: Hi After a stop a resume, the wifi network which was previously working stopped and impossible to make it work again. After a suspend, I've got a kernel error : Kernel failure message 1: BUG: sleeping function called from invalid context at include/linux/pagemap.h:294 in_atomic():0, irqs_disabled():1 Pid: 5521, comm: hwclock Not tainted 2.6.27.3-27.rc1.fc10.i686 #1 [<c0425e3b>] __might_sleep+0xc6/0xcb [<c046d949>] lock_page+0x15/0x2f [<c046db81>] find_lock_page+0x1e/0x3a [<c046e055>] filemap_fault+0x96/0x32b [<c04799bf>] __do_fault+0x3b/0x2c7 [<c04def65>] ? journal_dirty_metadata+0x32/0xd6 [<c047b254>] handle_mm_fault+0x2e0/0x6d1 [<c0440ef2>] ? sched_clock_cpu+0x12c/0x13b [<c051f6f6>] ? rb_insert_color+0x56/0xc0 [<c043f158>] ? enqueue_hrtimer+0xc1/0xcc [<c06c7b4e>] do_page_fault+0x2e0/0x68e [<c0420a09>] ? hrtick_start_fair+0x11c/0x153 [<c040271a>] ? __switch_to+0x114/0x139 [<c0428f4d>] ? finish_task_switch+0x2f/0xb0 [<c06c48ef>] ? schedule+0x6ee/0x70d [<c0405f33>] ? do_softirq+0xbe/0xdb [<c05200d8>] ? strspn+0x24/0x2e [<c0496a13>] ? path_put+0x15/0x18 [<c045f9c4>] ? audit_syscall_exit+0xb2/0xc7 [<c06c786e>] ? do_page_fault+0x0/0x68e [<c06c6142>] error_code+0x72/0x78 I tried stopping network daemon and network manager, removing the module and reloading it, then restating the daemons, it didn't work. Version-Release number of selected component (if applicable): kernel : Linux Laia 2.6.27.3-27.rc1.fc10.i686 #1 SMP Sat Oct 18 20:35:56 EDT 2008 i686 i686 i386 GNU/Linux NetworkManager : 0.7.0 0.11.svn4175.fc10 Build Date: dim. 12 oct. 2008 17:25:13 CEST with the corresponding applet: Applet NetworkManager 0.7.0 02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01) KDE 4.1.2 environnement (I didn't test yet with knetworkmanager). How reproducible: Always Steps to Reproduce: 1. Resume to RAM 2. Restart the system 3. Trying to connect to a networtk Actual results: I can't connect to a network Expected results: Be able to connect a network Additional info: I already did a bugreport here but I wasn't sure it was on the proper location: https://bugzilla.redhat.com/show_bug.cgi?id=453124
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.