I have the same bug here (and didn't test any new drive) but I would like to share a WORKAROUND, while the bug isn't fixed.
If you load the iwlagn with the option 11n_disable, you disable the N standard, and avoid the kernel panic.
I've add 'options iwlagn 11n_disable=1' to my /etc/modprobe.d/options. So far, so good.
I want this fixed for the Intrepid release, but if it's not possible, I would consider add this workaround enable by default.
I have the same bug here (and didn't test any new drive) but I would like to share a WORKAROUND, while the bug isn't fixed.
If you load the iwlagn with the option 11n_disable, you disable the N standard, and avoid the kernel panic.
I've add 'options iwlagn 11n_disable=1' to my /etc/modprobe. d/options. So far, so good.
I want this fixed for the Intrepid release, but if it's not possible, I would consider add this workaround enable by default.