From: "Michael Büsch" <mb@bu3sch.de>
To: Simon Richter <sjr@debian.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Ben Hutchings <ben@decadent.org.uk>,
Stefano Brivio <stefano.brivio@polimi.it>,
linux-wireless@vger.kernel.org, 588196@bugs.debian.org
Subject: Re: Bug#588196: b43: does not join multicast groups
Date: Tue, 13 Jul 2010 16:05:10 +0200 [thread overview]
Message-ID: <4C3C7296.3070700@bu3sch.de> (raw)
In-Reply-To: <20100713130614.GB25565@richter> (sfid-20100713_150638_259090_128768E3)
On 07/13/2010 03:06 PM, Simon Richter wrote:
> Hi,
>
> On Tue, Jul 13, 2010 at 03:00:00PM +0200, Michael Büsch wrote:
>
>> But I wanna say again that this all is expected behavior. The PIO
>> fallback workaround randomly drops packets when switching modes.
>> So it is expected that certain handshaking packages may be lost.
>
> So if the handshake to join a MC group is lost for whatever reason, it
> is lost forever, or is that just in the "shit happened, reset
> everything" code path?
It's not entirely possible to answer that question from a b43 point of view.
What happens in b43 is:
It tries to transmit through DMA. If that fails, it drops all queued
packets (but does not tell any upper layer about that) and resets the
hardware to PIO mode and waits for further work.
So it is up to the upper layer to detect the failure. I don't think
it's possible to automatically detect such incidents for multicast
transmissions. So the mechanism fails here.
>>> I was also having some suspend related issues, I'm going to give it a
>>> few days now to see whether they also disappear now.
>
>> Please open a new bug for this. Thanks.
>
> If they keep appearing; this may also be related to lost packets.
I'm pretty sure that any suspend issue is not related to the PIO
fallback mechanism.
--
Greetings Michael.
next prev parent reply other threads:[~2010-07-13 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100706021937.11147.78230.reportbug@debian.hogyros.de>
2010-07-11 22:25 ` Bug#588196: b43: does not join multicast groups Ben Hutchings
2010-07-11 22:57 ` Larry Finger
2010-07-13 5:14 ` Simon Richter
2010-07-13 5:37 ` Larry Finger
2010-07-13 7:37 ` Simon Richter
2010-07-13 13:00 ` Michael Büsch
2010-07-13 13:06 ` Simon Richter
2010-07-13 14:05 ` Michael Büsch [this message]
2010-07-14 7:50 ` Simon Richter
2010-07-14 12:41 ` Michael Büsch
2010-07-15 8:51 ` Simon Richter
2010-07-15 13:45 ` Michael Büsch
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=4C3C7296.3070700@bu3sch.de \
--to=mb@bu3sch.de \
--cc=588196@bugs.debian.org \
--cc=Larry.Finger@lwfinger.net \
--cc=ben@decadent.org.uk \
--cc=linux-wireless@vger.kernel.org \
--cc=sjr@debian.org \
--cc=stefano.brivio@polimi.it \
/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).