On Mon, Oct 15, 2012 at 04:51:00PM +0200, Paul Bolle wrote: > On Fri, 2012-09-14 at 14:17 +0200, Paul Bolle wrote: > > 0) It's one year later now and this Microcode SW error again showed up > > in the logs. I recently upgraded and I haven't kept any logs, but my > > guess would be that I have run into that error once every week. (This > > laptop is now running a v3.5.3 based kernel as shipped for Fedora 17.) > > > > 1) Would you have any suggestions how to pinpoint the cause of this > > error? It is mainly annoying, and I managed to ignore it since my > > previous message, but I still would like to free the logs from the noise > > it makes. > > 0) I ported the "iwlegacy_tracing" patch from > https://bugzilla.kernel.org/show_bug.cgi?id=42766 to v3.6-rc7 and to > iwl4965. I've been running iwl4965 with tracing enabled ever since (that > is on: v3.6-rc7, v3.6, v3.6.1, and v3.6.2). Finally, after only three > weeks I hit our Microcode SW error again. > > 1) So now I've got a 600+k line (or 65 MB) trace dump. What should I do > with it? Just post me privately let say last 10MB of it... Stanislaw -- 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
