From: Jiri Slaby <jirislaby@gmail.com>
To: me@bobcopeland.com
Cc: Pedro Francisco <pedrogfrancisco@gmail.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
mickflemm@gmail.com
Subject: Re: ath5k misbehaving affecting other kernel parts unrelated?
Date: Sun, 25 Apr 2010 22:29:45 +0200 [thread overview]
Message-ID: <4BD4A639.8000703@gmail.com> (raw)
In-Reply-To: <20100425192242.GA27921@hash.localnet>
On 04/25/2010 09:22 PM, me@bobcopeland.com wrote:
> On Sat, Apr 24, 2010 at 06:28:36PM +0100, Pedro Francisco wrote:
>> =============================================================================
>> [ 2658.663424] BUG kmalloc-4096: Poison overwritten
>> [ 2658.663483]
>
> Ok there are 4 messages here, two of them are definitely 802.11 beacons,
> which would point the finger squarely at ath5k. We had reports of this
> some time ago but a few things got rewritten around that time. I'd guess
> the rx DMA code is still subtly broken.
>
>> 6b 6b kkkkkkkkkkkkkkkk
>> [ 2658.664816] Object 0xed3db0c0: c4 00 84 00 00 22 43 89 42 69 4e 12 ca 6f
>> 6f 6f �...."C.BiN.�ooo
>> [ 4689.945547] Object 0xed3d9080: c4 00 70 00 00 22 43 89 42 69 fe 08 eb 14
>> 14 14 �.p.."C.Bi�.�...
>
> Offhand, I'm not sure what pattern these are.
These are CTS frames. So I think ath5k is to blame too :/.
regards,
--
js
next prev parent reply other threads:[~2010-04-25 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201004230806.13628.pedrogfrancisco@gmail.com>
2010-04-23 13:48 ` ath5k misbehaving affecting other kernel parts unrelated? John W. Linville
2010-04-23 16:37 ` me
2010-04-23 16:43 ` Maciej Żenczykowski
2010-04-24 8:59 ` Pedro Francisco
2010-04-24 8:56 ` Pedro Francisco
2010-04-24 12:05 ` me
2010-04-24 12:09 ` Vegard Nossum
2010-04-24 17:28 ` Pedro Francisco
2010-04-25 19:22 ` me
2010-04-25 20:29 ` Jiri Slaby [this message]
2010-04-25 21:24 ` Pedro Francisco
2010-04-27 11:04 ` Pedro Francisco
2010-04-28 21:52 ` Pedro Francisco
2010-04-29 7:17 ` Vegard Nossum
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=4BD4A639.8000703@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
--cc=pedrogfrancisco@gmail.com \
--cc=vegard.nossum@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;
as well as URLs for NNTP newsgroup(s).