From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Luis Rodriguez <Luis.Rodriguez@atheros.com>,
Bruno Randolf <br1@einfach.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ath9k: BUG kmalloc-8192: Poison overwritten
Date: Fri, 14 May 2010 13:52:53 -0700 [thread overview]
Message-ID: <20100514205253.GC28198@tux> (raw)
In-Reply-To: <4638F7CF-1E00-411F-A086-BA30809E00BD@gmail.com>
On Fri, May 14, 2010 at 01:21:34PM -0700, Justin P. Mattock wrote:
> Eveything is on except ath5k
> For debugging.
Bleh, try this.
diff --git a/drivers/net/wireless/ath/ath9k/recv.c b/drivers/net/wireless/ath/ath9k/recv.c
index 1ca42e5..3404198 100644
--- a/drivers/net/wireless/ath/ath9k/recv.c
+++ b/drivers/net/wireless/ath/ath9k/recv.c
@@ -129,7 +129,7 @@ int ath_rx_init(struct ath_softc *sc, int nbufs)
common->rx_bufsize = roundup(IEEE80211_MAX_MPDU_LEN,
min(common->cachelsz, (u16)64));
- ath_print(common, ATH_DBG_CONFIG, "cachelsz %u rxbufsize %u\n",
+ printk("ATH9K: cachelsz %u rxbufsize %u\n",
common->cachelsz, common->rx_bufsize);
/* Initialize rx descriptors */
Not sure why this is not printing, the common debug_mask should
already be set here prior to this. Anyway this would force the
print I want.
Luis
next prev parent reply other threads:[~2010-05-14 20:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 22:17 ath9k: BUG kmalloc-8192: Poison overwritten Justin P. Mattock
2010-05-13 23:01 ` Luis R. Rodriguez
2010-05-14 0:21 ` Justin P. Mattock
2010-05-14 0:28 ` Luis R. Rodriguez
2010-05-14 0:50 ` Justin P. Mattock
2010-05-14 1:08 ` Bruno Randolf
2010-05-14 1:13 ` Justin P. Mattock
2010-05-14 1:23 ` Luis R. Rodriguez
2010-05-14 1:26 ` Justin P. Mattock
2010-05-14 1:43 ` Luis R. Rodriguez
2010-05-14 1:45 ` Luis R. Rodriguez
2010-05-14 2:14 ` Justin P. Mattock
2010-05-14 4:01 ` Luis R. Rodriguez
2010-05-14 4:44 ` Justin P. Mattock
2010-05-14 6:16 ` Luis R. Rodriguez
2010-05-14 6:20 ` Bruno Randolf
2010-05-14 6:31 ` Justin P. Mattock
2010-05-14 6:36 ` Luis R. Rodriguez
2010-05-14 6:42 ` Justin P. Mattock
2010-05-14 6:38 ` Bruno Randolf
2010-05-14 15:41 ` Justin P. Mattock
2010-05-14 16:53 ` Luis R. Rodriguez
2010-05-14 17:24 ` Justin P. Mattock
2010-05-14 17:29 ` Luis R. Rodriguez
2010-05-14 19:04 ` Justin P. Mattock
2010-05-14 20:13 ` Luis R. Rodriguez
2010-05-14 20:21 ` Justin P. Mattock
2010-05-14 20:52 ` Luis R. Rodriguez [this message]
2010-05-14 20:58 ` Justin P. Mattock
2010-05-14 22:32 ` Justin P. Mattock
2010-05-15 0:52 ` Luis R. Rodriguez
2010-05-15 1:26 ` Justin P. Mattock
2010-05-14 6:20 ` Justin P. Mattock
2010-05-14 4:55 ` Pekka Enberg
2010-05-14 5:07 ` Luis R. Rodriguez
2010-05-14 5:19 ` Justin P. Mattock
2010-05-14 16:12 ` Christoph Lameter
2010-05-14 16:54 ` Justin P. Mattock
2010-05-14 14:26 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100514205253.GC28198@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=br1@einfach.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox