Since there seems to be some doubt in the kernel team about whether this bug still exists, I confirm that it's consistently reproducible with 2.6.28-11.38 and iwl3945.
Since there seems to be some doubt in the kernel team about whether this bug still exists, I confirm that it's consistently reproducible with 2.6.28-11.38 and iwl3945.