Each bit enables a specific driver area/topic/type of debug messages ... bits are defined by IWL_DL_ #defines in iwl-3945-debug.h ... 0x43fff gives a nice cross section of debug messages without being *overly* verbose. -- Ben -- > -----Original Message----- > From: ipw3945-devel-bounces@xxxxxxxxxxxxxxxxxxxxx > [mailto:ipw3945-devel-bounces@xxxxxxxxxxxxxxxxxxxxx] On > Behalf Of Stefanik Gábor > Sent: Monday, July 14, 2008 2:11 PM > To: Cahill, Ben M > Cc: linux-wireless; ipw3945-devel > Subject: Re: [ipw3945-devel] iwl3945 random firmware crashes > > On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M > <ben.m.cahill@xxxxxxxxx> wrote: > > Try loading driver using module param: > > > > debug=0x43fff > > > > This will provide more information in the log, including an > event log > > (where you see "Microcode SW Error detected" in your log, you would > > have captured Event Log if you had the debug=0x43fff setting). > > > > -- Ben -- > > Just a question: Why are we using cryptic hex IDs for the > debug setting? Is there a specific reason for this, or just > noone has yet included proper modparams for the various > debugging settings? > > -- > Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) > > -------------------------------------------------------------- > ----------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source > project, along with a healthy diet, reduces your potential > for chronic lameness and boredom. Vote Now at > http://www.sourceforge.net/community/cca08 > _______________________________________________ > 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
