Description of problem: My connection stalls. NetworkManager will still show I'm connected, but won't reconnect, failing at getting an IP. The only way I know how to fix it when this happens is to reboot, but it then hangs on iptables: Unloading module. It will hang there indefinitely and I have to power off at this point. When this issue is not happening, I can reboot with no errors. Version-Release number of selected component (if applicable): iptables-1.4.1.1-1.fc9.i386 kernel: 2.6.25.11-97.fc9.i686 How reproducible: Happens 1-2 times daily. Steps to Reproduce: 1. Connect to wireless using Cisco Aironet with NetworkManager. 2. Use connection for several hours. 3. Observe sudden drop in connectivity and issue described above. Actual results: Network connectivity is unstable and reboot hangs. Expected results: Stable network connectivity and successful reboots. Additional info: Using an IBM ThinkPad T30 with Cisco Aironet card.
What exactly is hanging? The unload of a kernel module?
That is what was hanging on shutdown. I set unload to "No" in the conf and I can shut it down with no errors, now hen I lose connection. The connection loss still occasionally happens, and when it does I must reboot to reconnect. it will actually still say I'm connected to a network, but I won't have any internet access, and won't be able to reconnect to the network with NetworkManager. It seems to happen when the card is under a load for a time, such as when seeding torrents.
Sorry to be more specific, it is the iptables unloading the is hanging. It happens for both IPv6 and IPv4 (If I disable IPv6 it hangs at IP instead).
Is there a hanging modprobe command?
How would I check for this? The only thing in my modprobe.conf is aliases related to my sound card.
Have a look at the output of "ps aux". Is there is a "modprobe -r" command hanging around?
This bug entry was in needinfo for some time. Closing due to user inactivity as "NOT A BUG".