Comment 59 for bug 263059

Sebastian: No problem. I have also originally reported my problem in this thread. I decided to fill in a new bug because my system have never finished boot process if the driver wasn't blacklisted. However there are many similarities to the situation reported in this thread.

I think it can be useful if one of the reporters could boot with the driver blacklisted and than try to load it using modprobe and post dmesg output. One more observation is that command "modprobe iwl3945" does not hang itself but when I subsequently run a program that tries to access the driver like iwconfig than it hangs permanently.

I can also confirm that issue persist in the kernel 2.6.27-7-generic