2.6.32.10-83.fc12.x86_64 broke, 2.6.32.9 was working. F13 kernels are also broken, potentially in a different way.
<cebbert> this got added in .10: http://git.kernel.org/?p= linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=5e2f75b8993a0d83d46 9388b50716dd5551f2eb4 Mar 18 20:07:19 <Oxf13> yeah, I think .9 worked, and .10 broke
I think I'm probably seeing the same thing: kernel-2.6.32.10-90.fc12.i686 broke, going back to 2.6.32.9-70.fc12.i686 was OK. Network works for something like 2-3 minutes, after which ARP requests for default gw no longer get response. I see some inbound packets. After reassociating (clicking 'eduroam' SSID again in NM) it works again for a couple of minutes. FWIW, I get the $SUBJECT dmesg message in both kernels, but 2.6.32.9 works fine regardless of that. The driver: 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) Subsystem: Intel Corporation Lenovo ThinkPad T61 Physical Slot: 3 Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f7f00000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-21-5c-ff-ff-62-a7-75 Kernel driver in use: iwlagn Kernel modules: iwlagn HTH.
This bug is a duplicate, problems should be solved in -94 kernel: http://koji.fedoraproject.org/koji/buildinfo?buildID=164636 (In reply to comment #0) > F13 kernels are also broken, potentially in a different way. Please open new F13 bugzilla and assign it to me. Thanks. (In reply to comment #2) > I think I'm probably seeing the same thing: kernel-2.6.32.10-90.fc12.i686 > broke, going back to 2.6.32.9-70.fc12.i686 was OK. Network works for something > like 2-3 minutes, after which ARP requests for default gw no longer get > response. I see some inbound packets. After reassociating (clicking 'eduroam' > SSID again in NM) it works again for a couple of minutes. Please open new bug (+ assign to me) if this still happens on uptodate kernels. Thanks. *** This bug has been marked as a duplicate of bug 578663 ***
I can confirm that testing -94 appears to have fixed my problem.