From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-wireless@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: ath9k: BUG kmalloc-8192: Poison overwritten
Date: Thu, 13 May 2010 22:19:25 -0700 [thread overview]
Message-ID: <4BECDD5D.9010609@gmail.com> (raw)
In-Reply-To: <AANLkTimmctk1GWOTlW8Han7E3gJVgqJjUAMeqYnvyuHn@mail.gmail.com>
On 05/13/10 22:07, Luis R. Rodriguez wrote:
> On Thu, May 13, 2010 at 9:55 PM, Pekka Enberg<penberg@cs.helsinki.fi> wrote:
>> Hi Luis,
>>
>> On Fri, May 14, 2010 at 2:01 AM, Luis R. Rodriguez
>> <lrodriguez@atheros.com> wrote:
>>> On Thu, May 13, 2010 at 3:17 PM, Justin P. Mattock
>>> <justinmattock@gmail.com> wrote:
>>>> not sure what this is, but while at a convention
>>>> I was trying to access the internet and(below is
>>>> full dmesg) this showed up.
>>>>
>>>> After receiving this, I sat and tried to re-create
>>>> my steps to reproduce but had no luck(was even going
>>>> todo a bisect n the spot if I could re-create).
>>>
>>> OK this stuff is hard to reproduce it seems.. you have an Atheros
>>> AR5418 MAC/BB Rev:2 AR5133 RF Rev:81, what kconfig option do you use
>>> to get the poison stuff? I am just surprised we haven't seen it
>>> ourselves yet. Let me make sure all of us get this kconfig option
>>> enabled.
>>
>> CONFIG_SLUB_DEBUG and then either CONFIG_SLUB_DEBUG_ON or pass
>> 'slub_debug' as kernel parameter.
>
> Ah OK I had CONFIG_SLUB_DEBUG but not CONFIG_SLUB_DEBUG_ON, will
> enable it from here on.
>
> Luis
>
I enable these options as well..
(then see If I can(hopefully)re-create this
then I'll bisect it).
Justin P. Mattock
next prev parent reply other threads:[~2010-05-14 5:19 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
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 [this message]
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=4BECDD5D.9010609@gmail.com \
--to=justinmattock@gmail.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=penberg@cs.helsinki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.