Comment 38 for bug 345710

I've also tested it (the v3) and no problem when loading and unloading the
module.

2009/7/2 Stefan Bader <email address hidden>

> ** Description changed:
>
> + SRU Justification:
> +
> + Impact: Removing the iwl3945 module can cause a hard lockup of the
> + system as there is a race condition which might get the rfkill_poll
> + workqueue restarted/running after the module code has been unloaded.
> +
> + Fix: Two patches from upstream, the first moving the call that restarts
> + the workqueue on the way down to be executed before stopping the
> + workqueue. The second patch makes the call stopping the workqueue wait
> + for any running worker.
> +
> + Testcase: Removing and loading the module in a loop (has been verified
> + to be working after the patches being applied).
> +
> + ---
> +
> I can reliably reproduce a total system lock-up (no response to SysReq
> keys) when-ever the module is removed. It occurs about 3 seconds after
> the removal has completed whilst the notification of removal is still
> on-screen.
>
> sudo modprobe -r iwl3945
>
> sudo modprobe iwl3945
>
> uname -a
> Linux hephaestion 2.6.28-11-generic #35-Ubuntu SMP Wed Mar 18 21:55:34 UTC
> 2009 x86_64 GNU/Linux
> lspci -nn | grep -i Wireless
> 06:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG
> [Golan] Network Connection [8086:4222] (rev 02)
>
> Because the lock-up is total the log files aren't synced and therefore
> the last 5 seconds or so of messages are not in the logs to help
> diagnose it. Tomorrow I shall use a netconsole connection to try to get
> more information.
>
> ** Tags removed: upstream-pending
>
> --
> modprobe -r iwl3945 causes total system freeze
> https://bugs.launchpad.net/bugs/345710
> You received this bug notification because you are a direct subscriber
> of the bug.
>