Due to backport of patch linux-2.6-iwl3945-report-killswitch-changes-even-if-the-interface-is-down.patch we have bunch of iwl3945 bugs (race conditions) that are not reproducible on vanilla 2.6.29. These patches address them (at least some of them). [PATCH 1/3] iwl3945: release resources before shutting down (F11 backport) Resolves RHBZ 499811 (and partially 501117), backport of upstream commit, 2.6.30 has this fix. [PATCH 2/3] iwl3945: add debugging for wrong command queue (F11 backport) Partially resolves RHBZ 501117. Backport of upstream commit, 2.6.30 has this commit. Bug is still reproducible, but after patch applied system not crash. Further work needed to fully resolve the problem, but I'm not sure is easy way to fix 501117 (DMA related memory corruption) other than rebase driver to that we have in 2.6.31. [PATCH 3/3] iwl3945: fix rfkill SW and HW mishmash Resolves RHBZ 498622. The bug is fixed in mainline from 2.6.31-rc3 due to total rewrite of rfkill framework (commit: 19d337dff95cbf76edd3ad95c0cee2732c3e1ec5 "rfkill: rewrite"). However it is reproducible on 2.6.30 as well. Perhaps I should post this patch against 2.6.30, but I'm not sure is such kind of patches, which are not backports, are acceptable in stable kernel. I tested all patches on my laptop. _______________________________________________ Fedora-kernel-list mailing list Fedora-kernel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-kernel-list
