Hi Jason, On Mon, 2009-03-09 at 18:40 -0700, Jason Andryuk wrote: > I thought I had made a big breakthrough when I found the solution to > getting > "iwlwifi: use iwl_cmd instead of iwl3945_cmd" > bb64785ad94d575fe4f5f9e69f4f6c0b24e9905d to work. Then I discovered > that casting to iwl3945_tx_cmd was fixed later by "iwl3945: use > iwl3945_tx_cmd instead of iwl_tx_cmd" fadd267e... Does this mean if you apply commit fadd267e on top of bb64785ad94d575fe4f5f9e69f4f6c0b24e9905d then things work? > > However, with this new knowledge, I was able to get farther. > > Using my iwl3945_tx_cmd conversion patch, Is this the last patch you emailed? I don't think so as it (your last patch) replaced iwl3945_cmd_meta and iwl3945_host_cmd. > a patch for allocating rb_stts could you please post this patch > and a patch for the BUG_ON -> WARN_ON, ... and this one > I was able to narrow down commit > "iwl3945: sync tx queue data structure with iwlagn" > ff5010c3e12f1d0da27a5f871c2e3d5333dfbe2f as the one that starts > introducing Microcode SW errors. > I am not sure how your repository looks at this stage. What is your latest wireless-testing commit and what patches do you have on top of it? > I tried adding in Reinette's iwl3945_hw_txq_free_tfd pci_unmap_single > patch from earlier, but it did not fix the problem. > > Would TX debugging output be more helpful? 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. You can also put a dump_stack() in iwl3945_connection_init_rx_config to see where the call comes from and then trace the value of mode to see where it is set to 515 ... it is supposed to be 2 (NL80211_IFTYPE_STATION). > > Any thoughts on what could be going wrong? I am finding it hard to keep track of things as what works and what does not work appears to shift. I did install a 64bit system in the hopes of reproducing your issue but could not with a basic open connect. How do you connect to the AP? Please provide details that you think will enable me to reproduce. Thanks Reinette -- 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
