The patch titled
orinoco: fix BAP0 offset error after several days of operation
has been removed from the -mm tree. Its filename is
orinoco-fix-bap0-offset-error-after-several-days-of-operation.patch
This patch was probably dropped from -mm because
it has now been merged into a subsystem tree or
into Linus's tree, or because it was folded into
its parent patch in the -mm tree.
From: Jiri Benc <jbenc@xxxxxxx>
After several days of operation of Netgear MA311 card, the card becomes to
seek improperly and needs reset. This patch tries to reset the card when this
situation occurs.
Mar 9 06:45:16 berkeley kernel: wlan0: Error -5 writing packet to BAP
Mar 9 06:45:16 berkeley kernel: hermes @ f992a000: BAP0 offset error: reg=0x4044 id=0x128 offset=0x44
Mar 9 06:45:16 berkeley kernel: wlan0: Error -5 writing packet to BAP
Mar 9 06:45:16 berkeley kernel: hermes @ f992a000: BAP0 offset error: reg=0x4044 id=0x128 offset=0x44
(etc.)
A more detailed description of the problem can be found at
https://bugzilla.novell.com/show_bug.cgi?id=154773 The same problem with
different card is reported at
http://sourceforge.net/mailarchive/message.php?msg_id=14597046
Signed-off-by: Jiri Benc <jbenc@xxxxxxx>
Signed-off-by: Pavel Roskin <proski@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/net/wireless/orinoco.c | 2 ++
1 files changed, 2 insertions(+)
diff -puN drivers/net/wireless/orinoco.c~orinoco-fix-bap0-offset-error-after-several-days-of-operation drivers/net/wireless/orinoco.c
--- 25/drivers/net/wireless/orinoco.c~orinoco-fix-bap0-offset-error-after-several-days-of-operation Fri Apr 7 15:37:36 2006
+++ 25-akpm/drivers/net/wireless/orinoco.c Fri Apr 7 15:37:36 2006
@@ -536,6 +536,8 @@ static int orinoco_xmit(struct sk_buff *
return NETDEV_TX_OK;
busy:
+ if (err == -EIO)
+ schedule_work(&priv->reset_work);
orinoco_unlock(priv, &flags);
return NETDEV_TX_BUSY;
}
_
Patches currently in -mm which might be from jbenc@xxxxxxx are
git-wireless.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
