summaryrefslogtreecommitdiffstats
path: root/drivers/bcma
diff options
context:
space:
mode:
authorArend van Spriel <arend@broadcom.com>2013-01-22 22:47:40 +0100
committerJohn W. Linville <linville@tuxdriver.com>2013-01-28 14:48:52 -0500
commit0e33e48ddc4402e890aaeeeacc95f730bf522098 (patch)
treee82d3c86f83bc771ceb078460bdcf18ba5755329 /drivers/bcma
parent006da9ebba4f958812289c9f4df69d6c12a79eaf (diff)
downloadop-kernel-dev-0e33e48ddc4402e890aaeeeacc95f730bf522098.zip
op-kernel-dev-0e33e48ddc4402e890aaeeeacc95f730bf522098.tar.gz
brcmsmac: fix tx status processing
This issue was reported on the wireless list (see [1]) in which brcmsmac ran into a fatal error: [ 588.284074] brcmsmac bcma0:0: frameid != txh->TxFrameID [ 588.284098] brcmsmac bcma0:0: MI_TFS: fatal [ 588.284103] brcmsmac bcma0:0: wl0: fatal error, reinitializing [ 588.286208] ieee80211 phy0: Hardware restart was requested The tx status feedback is processed in a loop limiting the number of frames processed in one run. The code terminate processing when the limit is reached regardless the txstatus value read from the device register. When that status is is flagged as being valid it must be processed as the hardware will clear it after is has been read. Bisecting was done by Seth Forshee and showed following commit as the culprit: commit 57fe504817ccec9b6ac23e973d2925343bf1e3b6 Author: Piotr Haber <phaber@broadcom.com> Date: Wed Nov 28 21:44:07 2012 +0100 brcmsmac: fix bounds checking in tx/rx [1] http://www.spinics.net/lists/linux-wireless/msg101293.html Reported-by: Linus Torvalds <torvalds@linux-foundation.org> Tested-by: Seth Forshee <seth.forshee@canonical.com> Reviewed-by: Hante Meuleman <meuleman@broadcom.com> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com> Signed-off-by: Arend van Spriel <arend@broadcom.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/bcma')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud