Some more things from the syslog that may be of relevance. System went through multiple suspend and resume cycles. Before the failure we have a wlan authentication and the ATH driver throws a fit. [ 7339.673270] ll header: ff:ff:ff:ff:ff:ff:00:90:fb:1c:4f:5c:08:00 [ 7340.076865] FIREWALL:INPUT IN=wlan0 OUT= MAC=00:19:e3:06:2c:16:00:90:fb:1c:4f:5c:08:00 SRC=192.168.5.1 DST=192.168.5.11 LEN=48 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=251 SEQ=0 [ 7416.743752] cfg80211: Calling CRDA to update world regulatory domain [ 7419.292521] wlan0: authenticate with 00:21:55:b4:20:20 (try 1) [ 7419.312690] wlan0: authenticated [ 7419.318325] wlan0: associate with 00:21:55:b4:20:20 (try 1) [ 7419.322764] wlan0: RX AssocResp from 00:21:55:b4:20:20 (capab=0x401 status=0 aid=218) [ 7419.322770] wlan0: associated [ 7427.161366] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 7427.161432] ath: Failed to stop TX DMA! [ 7434.492398] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 7434.492462] ath: Failed to stop TX DMA! [ 7603.339047] ============================================================================= [ 7603.339053] BUG radix_tree_node: Padding overwritten. 0xffff88000008fe00-0xffff88000008fe32 [ 7603.339055] ----------------------------------------------------------------------------- [ 7603.339056] Could the ath driver corrupt memory if the TX DMA cannot be stopped? Maybe fix the driver first? -- 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
