On Thu, Mar 12, 2009 at 11:31 PM, Jason Andryuk <jandryuk@xxxxxxxxx> wrote: > On Tue, Mar 10, 2009 at 11:40 PM, Jason Andryuk <jandryuk@xxxxxxxxx> wrote: >>> You log below has a new error (similar to what you note in your next >>> email). "Unsupported interface type 515". This is very strange and >>> really looks like some corruption as this value is initialized with a >>> macro during probe. Could you enable mac and info debugging also (add >>> 0x3 to your current debug flags)? This code has also changed a bit since >>> commit bb64785ad94d575fe4f5f9e69f4f6c0b24e9905d. > Looking at ff5010c3e12f1d0da27a5f871c2e3d5333dfbe2f, I found the call > to iwl_reset_qos corrupts priv->iw_mode. It is 2 before the call and > 515 after. Turns out that iwlcore.ko was stale with respect to iwl3945.ko. The older iwl_reset_qos in iwlcore.ko used an incorrect offset to access priv->qos_data. Unfortunately this did not solve the Microcode SW error, and I spent a lot of time chasing the wrong issue. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
