Search Linux Wireless

Re: Commit 741b4fbc44 (mac80211: fix TX sequence numbers) breaks rtl8187

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 23, 2008 at 7:43 AM, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote:
> Johannes,
>
> In the current wireless-testing (v2.6.26-rc9-14207-ga520bdb), rtl8187 is
> broken. In most cases, it is unable to complete a connection. Occasionally,
> it will authenticate and even get an IP using DHCP; however, only a few
> pings get through to the AP before the connection fails completely.
>
> Using bisection, this problem was traced to:
>
> ==================================================
> commit 741b4fbc441dba885cc8f97a10e87f2acd04c5f2
> Author: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
> Date:   Thu Jul 10 11:21:26 2008 +0200
>
>    mac80211: fix TX sequence numbers
>
>    This patch makes mac80211 assign proper sequence numbers to
>    QoS-data frames. It also removes the old sequence number code
>    because we noticed that only the driver or hardware can assign
>    sequence numbers to non-QoS-data and especially management
>    frames in a race-free manner because beacons aren't passed
>    through mac80211's TX path.
> ===============================================================
>
> The validity of the bisection was confirmed by reverse application of the
> patch. The resulting driver worked.
>
> The appears that rtl8187 needs some kind of modification such as b43,
> b43legacy, and rt2x00 got in the original patch. I'll be studying the
> changes to the other drivers to see if I can find the problem, but I will
> appreciate your help when you get a chance. Perhaps after your trip to
> Canada is over.
>
> Thanks,
>
> Larry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

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.

-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux