From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.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>,
Miles Lane <miles.lane@gmail.com>
Subject: Re: ath9k: BUG kmalloc-8192: Poison overwritten
Date: Fri, 14 May 2010 18:26:33 -0700 [thread overview]
Message-ID: <99B6B8BB-F155-4B15-95AF-C8DF3F5B4382@gmail.com> (raw)
In-Reply-To: <20100515005201.GH28198@tux>
Justin P. Mattock
On May 14, 2010, at 5:52 PM, "Luis R. Rodriguez"
<lrodriguez@atheros.com> wrote:
> On Fri, May 14, 2010 at 03:32:48PM -0700, Justin P. Mattock wrote:
>> ATH9K: cachelsz 256 rxbufsize 3904
>
> OK I see nothing odd with these values, and I do not see how
> these values can make ath_rxbuf_alloc() barf. I'd like to
> reproduce this myself at least once, I left iperf running over
> night with no rants from SLAB. I should note this should be
> reproducible with RX only if it is ath_rxbuf_alloc() to blame
> but without a concrete reproducible instructions it is hard
> to guess what to do and if this can only come up during RX.
>
> Can you describe a little more when you have seen this? What
> were you doing exactly, for how long? When was the last time
> you saw this, what were you doing then?
>
> Luis
This is hard to reproduce(reason for looking a kmemchek).
As for what I remember, walked into the las Vegas convention cntr
(Hilton),
Found the Internet hub, scanned for networks, wicd said it was
connected, opened firefox to see the prices, ended up seeing a blank
page(at this point didn't look at dmesg(could have already happened)),
then switched to another network(did this a few times),
Eventually opened firefox(saw the prices, said fuc*k this), then
started to read up on i8042.c(cause Linus was pull requesting and I
wanted to find out what was going on in that area), then
Checked dmesg, and voilà there the bug is.
After this rebooted, was hoping this was reproducable for a bisect,
but realized it's not the reproducable..
Justin P. Mattock
next prev parent reply other threads:[~2010-05-15 1:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 22:17 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
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 [this message]
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=99B6B8BB-F155-4B15-95AF-C8DF3F5B4382@gmail.com \
--to=justinmattock@gmail.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=br1@einfach.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=miles.lane@gmail.com \
/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
all inboxes | Powered by JetHome®