[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110310000502.GA13763@hash.localnet>
Date: Wed, 9 Mar 2011 19:05:02 -0500
From: Bob Copeland <me@...copeland.com>
To: Christoph Lameter <cl@...ux.com>
Cc: "Justin P. Mattock" <justinmattock@...il.com>,
David Rientjes <rientjes@...gle.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Nick Piggin <npiggin@...nel.dk>,
Dave Chinner <dchinner@...hat.com>,
linux-kernel@...r.kernel.org,
Pekka Enberg <penberg@...helsinki.fi>,
Jiri Slaby <jirislaby@...il.com>,
Nick Kossifidis <mickflemm@...il.com>,
"Luis R. Rodriguez" <lrodriguez@...eros.com>,
linux-wireless@...r.kernel.org
Subject: Re: <IRQ> [<ffffffff810c9204>] ? __alloc_pages_nodemask+0x622/0x696
On Wed, Mar 09, 2011 at 03:54:24PM -0600, Christoph Lameter wrote:
> [ 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
> Could the ath driver corrupt memory if the TX DMA cannot be stopped?
Looks like ath_draintxq() can do something bad (e.g. DMA engine uses
an old address from ath_tx_return_buffer()) if DMA is still active
in ath_drain_all_txq().
But this is ath9k which I'm not so familiar with, maybe Luis can say.
--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists