From: Johannes Berg <johannes@sipsolutions.net>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
Hin-Tak Leung <hintak.leung@gmail.com>,
Pavel Roskin <proski@gnu.org>,
linux-wireless@vger.kernel.org
Subject: Re: Commit 741b4fbc44 (mac80211: fix TX sequence numbers) breaks rtl8187
Date: Thu, 24 Jul 2008 16:22:08 +0200 [thread overview]
Message-ID: <1216909328.13587.67.camel@johannes.berg> (raw)
In-Reply-To: <69e28c910807230555s2040f507oe6c9e516ef8c0685@mail.gmail.com> (sfid-20080723_145507_239503_2FC0E55E)
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Wed, 2008-07-23 at 14:55 +0200, Stefanik Gábor wrote:
> Zd1211rw also appears to be affected, though not as seriously as with
> rtl8187: it scans, associates and gets DHCP, but it consistently
> disconnects after about 2~5 minutes, either with "No ProbeResp" in
> dmesg, or sometimes with no error message, just "Removed STA" and
> "Destroyed STA". I don't know if this is the same bug, as I haven't
> bisected, but it appeared when I switched from a 2.6.26-rc8-wl kernel
> to a 2.6.26-wl one that contained the above patch.
zd1211rw works fine here, been connected for about 15 minutes now.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-07-24 14:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 15:02 [RFC/RFT] rtl8187: Improve wireless statistics for RTL8187B Larry Finger
2008-07-19 0:42 ` Herton Ronaldo Krzesinski
2008-07-19 4:14 ` Larry Finger
2008-07-20 0:39 ` Hin-Tak Leung
2008-07-20 2:55 ` Larry Finger
2008-07-22 19:13 ` Herton Ronaldo Krzesinski
2008-07-22 22:25 ` Hin-Tak Leung
2008-07-22 22:40 ` Herton Ronaldo Krzesinski
2008-07-23 3:49 ` Larry Finger
2008-07-23 5:43 ` Commit 741b4fbc44 (mac80211: fix TX sequence numbers) breaks rtl8187 Larry Finger
2008-07-23 12:55 ` Stefanik Gábor
2008-07-24 14:22 ` Johannes Berg [this message]
2008-07-23 14:55 ` Johannes Berg
2008-07-23 15:32 ` Larry Finger
2008-07-23 16:27 ` Johannes Berg
2008-07-23 18:03 ` Larry Finger
2008-07-23 19:03 ` Johannes Berg
2008-07-24 3:28 ` Hin-Tak Leung
2008-07-24 5:40 ` Larry Finger
2008-07-24 8:05 ` Hin-Tak Leung
2008-07-24 11:34 ` Johannes Berg
2008-07-25 3:42 ` Hin-Tak Leung
2008-07-24 16:37 ` Herton Ronaldo Krzesinski
2008-07-25 1:28 ` Hin-Tak Leung
2008-07-29 2:39 ` Hin-Tak Leung
2008-07-29 3:15 ` Larry Finger
2008-07-29 3:29 ` Herton Ronaldo Krzesinski
2008-07-29 3:40 ` Larry Finger
2008-07-29 3:21 ` Herton Ronaldo Krzesinski
2008-07-29 6:53 ` Johannes Berg
2008-07-29 8:23 ` Tomas Winkler
2008-07-29 8:28 ` Johannes Berg
2008-07-29 8:38 ` Tomas Winkler
2008-07-29 9:16 ` Johannes Berg
2008-07-29 9:26 ` Tomas Winkler
2008-07-29 9:29 ` Johannes Berg
2008-07-29 11:16 ` Tomas Winkler
2008-07-29 11:18 ` Johannes Berg
2008-07-29 21:44 ` Kalle Valo
2008-07-29 21:40 ` Kalle Valo
2008-07-29 21:26 ` Kalle Valo
2008-07-29 21:19 ` Kalle Valo
2008-07-30 1:01 ` Hin-Tak Leung
2008-07-29 21:17 ` Kalle Valo
2008-07-29 21:12 ` Kalle Valo
2008-07-30 3:37 ` Herton Ronaldo Krzesinski
2008-07-30 8:54 ` Kalle Valo
2008-07-30 9:52 ` Johannes Berg
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=1216909328.13587.67.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=proski@gnu.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).