From: Larry Finger <Larry.Finger@lwfinger.net>
To: Miles Lane <miles.lane@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
linville@tuxdriver.com
Subject: Re: 2.6.18-rc5-mm1 -- bcm43xx: Out of DMA descriptor slots!
Date: Sun, 03 Sep 2006 09:00:43 -0500 [thread overview]
Message-ID: <44FAE00B.6030701@lwfinger.net> (raw)
In-Reply-To: <200609031433.49658.mb@bu3sch.de>
Michael Buesch wrote:
> On Sunday 03 September 2006 11:18, Miles Lane wrote:
>> Michael, I think this is related to your code (bcm43xx_dma.c). It is
>> quite possible that the bug isn't in your code, but rather in the
>> general management of DMA.
>
> Please try latest wireless-2.6 tree. I think it has a bugfix for this.
There is a fix (commit 653d5b55c0125dca97a420b9a5e77fad7adbf3f0) for mac_suspended assertions in the
latest wireless-2.6. If you just want that fix, use the following:
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
===================================================================
--- wireless-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c
+++ wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
@@ -3349,6 +3349,8 @@
memset(bcm->dma_reason, 0, sizeof(bcm->dma_reason));
bcm->irq_savedstate = BCM43xx_IRQ_INITIAL;
+ bcm->mac_suspended = 1;
+
/* Noise calculation context */
memset(&bcm->noisecalc, 0, sizeof(bcm->noisecalc));
If this patch is already in your code, and you are still getting the assertions, please let me know.
Larry
--
VGER BF report: H 0.427049
next prev parent reply other threads:[~2006-09-03 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 9:18 2.6.18-rc5-mm1 -- bcm43xx: Out of DMA descriptor slots! Miles Lane
2006-09-03 12:33 ` Michael Buesch
2006-09-03 14:00 ` Larry Finger [this message]
2006-09-03 16:55 ` Miles Lane
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=44FAE00B.6030701@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=miles.lane@gmail.com \
/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