From: Justin P. Mattock <justinmattock@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] BUG kmalloc-8192: Poison overwritten
Date: Thu, 03 Dec 2009 21:22:28 -0800 [thread overview]
Message-ID: <4B189C94.4080404@gmail.com> (raw)
In-Reply-To: <43e72e890912031345m3f5adb9nca754e33a858c923@mail.gmail.com>
On 12/03/09 13:45, Luis R. Rodriguez wrote:
> I think waiting to be able to reproduce is best, and appreciate your
> patience on this. Maybe Miles Lanes also cannot reproduce easily and
> that may explain why he hasn't replied.
>
> Luis
>
o.k., did some more experimenting
but came up with something other than
what I was hoping for(something with s2ram),
Anyways the two patches applied clean,
I'll just run the system with these in,
and if somebody comes along with more expertise
on this I can try their advice(or if I somehow find
a way to reproduce this).
Justin P. Mattock
WARNING: multiple messages have this Message-ID (diff)
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Miles Lane <miles.lane@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ath9k-devel@lists.ath9k.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] BUG kmalloc-8192: Poison overwritten
Date: Thu, 03 Dec 2009 21:22:28 -0800 [thread overview]
Message-ID: <4B189C94.4080404@gmail.com> (raw)
In-Reply-To: <43e72e890912031345m3f5adb9nca754e33a858c923@mail.gmail.com>
On 12/03/09 13:45, Luis R. Rodriguez wrote:
> I think waiting to be able to reproduce is best, and appreciate your
> patience on this. Maybe Miles Lanes also cannot reproduce easily and
> that may explain why he hasn't replied.
>
> Luis
>
o.k., did some more experimenting
but came up with something other than
what I was hoping for(something with s2ram),
Anyways the two patches applied clean,
I'll just run the system with these in,
and if somebody comes along with more expertise
on this I can try their advice(or if I somehow find
a way to reproduce this).
Justin P. Mattock
WARNING: multiple messages have this Message-ID (diff)
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Miles Lane <miles.lane@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ath9k-devel@venema.h4ckr.net,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] BUG kmalloc-8192: Poison overwritten
Date: Thu, 03 Dec 2009 21:22:28 -0800 [thread overview]
Message-ID: <4B189C94.4080404@gmail.com> (raw)
In-Reply-To: <43e72e890912031345m3f5adb9nca754e33a858c923@mail.gmail.com>
On 12/03/09 13:45, Luis R. Rodriguez wrote:
> I think waiting to be able to reproduce is best, and appreciate your
> patience on this. Maybe Miles Lanes also cannot reproduce easily and
> that may explain why he hasn't replied.
>
> Luis
>
o.k., did some more experimenting
but came up with something other than
what I was hoping for(something with s2ram),
Anyways the two patches applied clean,
I'll just run the system with these in,
and if somebody comes along with more expertise
on this I can try their advice(or if I somehow find
a way to reproduce this).
Justin P. Mattock
next prev parent reply other threads:[~2009-12-04 5:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 22:27 [ath9k-devel] BUG kmalloc-8192: Poison overwritten Justin Mattock
2009-12-02 22:27 ` Justin Mattock
2009-12-02 23:16 ` [ath9k-devel] " Luis R. Rodriguez
2009-12-02 23:16 ` Luis R. Rodriguez
2009-12-02 23:28 ` Justin P. Mattock
2009-12-02 23:28 ` Justin P. Mattock
2009-12-03 21:36 ` Justin P. Mattock
2009-12-03 21:36 ` Justin P. Mattock
2009-12-03 21:45 ` Luis R. Rodriguez
2009-12-03 21:45 ` Luis R. Rodriguez
2009-12-03 21:45 ` Luis R. Rodriguez
2009-12-03 21:58 ` Justin P. Mattock
2009-12-03 21:58 ` Justin P. Mattock
2009-12-03 21:58 ` Justin P. Mattock
2009-12-04 5:22 ` Justin P. Mattock [this message]
2009-12-04 5:22 ` Justin P. Mattock
2009-12-04 5:22 ` Justin P. Mattock
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=4B189C94.4080404@gmail.com \
--to=justinmattock@gmail.com \
--cc=ath9k-devel@lists.ath9k.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 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.