On Mon, 2009-11-02 at 18:07 -0800, Cahill, Ben M wrote: > Thanks for the report; disappointing news. Oops. I reported a bug I introduced.... http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2113 I take a look at the issue. Sorry. Best regards, Maxim Levitsky > > Don't forget to load driver with debug=0x43fff, to get Error and Event logs. > > -- Ben -- > > >-----Original Message----- > >From: Maxim Levitsky [mailto:maximlevitsky@xxxxxxxxx] > >Sent: Monday, November 02, 2009 7:40 PM > >To: iwlwifi maling list; linux-wireless > >Subject: [ipw3945-devel] iwl3945 microcode errors > > > >I see that iwl3945 began to show some microcode errors like that: > > > >[ 18.259947] iwl3945 0000:06:00.0: firmware: requesting > >iwlwifi-3945-2.ucode > >[ 18.766225] iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9 > >[ 18.817952] iwl3945 0000:06:00.0: Microcode SW error > >detected. Restarting 0x82000008. > >[ 18.817971] iwl3945 0000:06:00.0: Error Reply type > >0x00000000 cmd UNKNOWN (0x88) seq 0xDB3B ser 0x00880000 > >[ 18.822468] iwl3945 0000:06:00.0: Can't stop Rx DMA. > >[ 20.790058] iwl3945 0000:06:00.0: Wait for START_ALIVE > >timeout after 2000ms. > > > >Now it still works, but there were cases it didn't. > > > >I post more detailed info soon. > > > >Best regards, > > Maxim Levitsky > > > > > >--------------------------------------------------------------- > >--------------- > >Come build with us! The BlackBerry(R) Developer Conference in SF, CA > >is the only developer event you need to attend this year. > >Jumpstart your > >developing skills, take BlackBerry mobile applications to > >market and stay > >ahead of the curve. Join us from November 9 - 12, 2009. Register now! > >http://p.sf.net/sfu/devconference > >_______________________________________________ > >Ipw3945-devel mailing list > >Ipw3945-devel@xxxxxxxxxxxxxxxxxxxxx > >https://lists.sourceforge.net/lists/listinfo/ipw3945-devel > > -- 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
