On Thu, Mar 3, 2011 at 8:01 PM, Tony Houghton <h@xxxxxxxxxxx> wrote: > On Thu, 3 Mar 2011 10:51:15 +0530 > Mohammed Shafi <shafi.wireless@xxxxxxxxx> wrote: > >> On Wed, Mar 2, 2011 at 10:00 PM, Tony Houghton <h@xxxxxxxxxxx> wrote: >> > >> > Is this still not reproducible? I'd like to do more to help trace >> > the problem but I'm a bit stuck. Is there something I can do to >> > make sure all the debug/log messages from ath9k appear on the >> > console? >> >> sudo dmesg -n 8? > > AFAICT that will just make sure the debug messages get logged, but not > make them appear anywhere the other messages aren't appearing eg on a > console or net console. I could try tail -f /dev/xconsole. > > The ath9k module has a "debug" parameter. It just says it's a mask and I > don't know how to use it. Do I set bits to enable or disable levels? > What value to log "everything"? > Please make sure of the following things CONFIG_ATH_COMMON=m CONFIG_ATH_DEBUG=y CONFIG_ATH9K_HW=m CONFIG_ATH9K_COMMON=m CONFIG_ATH9K=m CONFIG_ATH9K_DEBUGFS=y CONFIG_ATH9K_RATE_CONTROL=y CONFIG_ATH9K_HTC=m CONFIG_ATH9K_HTC_DEBUGFS=y sudo modprobe ath9k debug=0xffffffff you will get lot of messages from the debug log. -- 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
