From: Christian Lamparter <chunkeey@web.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Memory errors from p54usb
Date: Wed, 17 Dec 2008 15:20:40 +0100 [thread overview]
Message-ID: <200812171520.40104.chunkeey@web.de> (raw)
In-Reply-To: <49487038.5090404@lwfinger.net>
On Wednesday 17 December 2008 04:21:28 Larry Finger wrote:
> Christian Lamparter wrote:
> > well, looks like TKIP countermeasures after all....
> >
> > The question is how to "debug" it...
> >
> > jm, are you aware of any compatibility problems or
> > regression between broadcom APs and wpa_supplicant
> > with WPA TKIP?
>
> Unfortunately (?) the problem still occurs with an unencrypted network. I hauled
> out my 801.11b AP/router, and the same problem occurs even when wpa_supplicant
> is not in the equation.
>
Ohh, it always gets better. ;)
Anyway, I'll see what I can do tomorrow.
In the meantime, I remembered that I put a heat sink on my chip a while ago,
but I'm not sure if this had any effect here... But back in the summer, it allowed me
fix the iperf stalls I had, but that was after days with 60Gb traffic...
Regards,
Chr
next prev parent reply other threads:[~2008-12-17 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 14:53 Memory errors from p54usb Larry Finger
2008-12-15 19:51 ` Christian Lamparter
2008-12-16 4:17 ` Larry Finger
2008-12-16 13:31 ` Christian Lamparter
2008-12-16 16:55 ` Larry Finger
2008-12-16 17:13 ` Christian Lamparter
2008-12-16 17:50 ` Larry Finger
2008-12-16 18:29 ` Christian Lamparter
[not found] ` <200812162029.22491.chunkeey@web.de>
[not found] ` <49481CCC.1030903@lwfinger.net>
2008-12-16 21:56 ` Christian Lamparter
2008-12-17 3:21 ` Larry Finger
2008-12-17 14:20 ` Christian Lamparter [this message]
2008-12-17 16:01 ` Larry Finger
2008-12-17 16:36 ` Christian Lamparter
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=200812171520.40104.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--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;
as well as URLs for NNTP newsgroup(s).