From: "Roland Vossen" <rvossen@broadcom.com>
To: "Dan Williams" <dcbw@redhat.com>
Cc: Camaleón <noelamac@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"Brett Rudley" <brudley@broadcom.com>,
"Henry Ptasinski" <henryp@broadcom.com>,
"Arend Van Spriel" <arend@broadcom.com>,
"networkmanager-list@gnome.org" <networkmanager-list@gnome.org>
Subject: Re: brcmsmac driver only works when sitting next to the AP
Date: Wed, 17 Aug 2011 12:39:01 +0200 [thread overview]
Message-ID: <4E4B9A45.5090507@broadcom.com> (raw)
In-Reply-To: <1313509211.2065.36.camel@dcbw.foobar.com>
>> 'Aug 14 13:39:02 stt300 NetworkManager[1181]:
>> supplicant_interface_acquire: assertion `mgr_state ==
>> NM_SUPPLICANT_MANAGER_STATE_IDLE' failed'
>>
>> I also see many 'wpa_supplicant[1204]: Failed to initiate AP scan' messages.
>>
>> There are no 'Failed to initiate AP scan' messages before the 'assertion
>> failed' message. I do not know if the 2nd message is a byproduct of the
>> 1st result. Regardless, a failed assertion is serious. I cc'ed the
>> network manager mailing list.
> Yeah, the scanning issues are almost certainly what's causing stuff to
> fail; which obviously seems like a driver issue at this point.
Well, the 1st sign that something goes wrong is the assert message in
NetworkManager. After that, the scans are the next things that go wrong.
So I don't understand why you think that this is a driver problem, I
would rather say this is a Network manager problem. Could you explain ?
Thanks, Roland.
next prev parent reply other threads:[~2011-08-17 10:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 12:16 brcmsmac driver only works when sitting next to the AP Camaleón
2011-08-16 11:36 ` Roland Vossen
2011-08-16 15:40 ` Dan Williams
2011-08-17 10:39 ` Roland Vossen [this message]
2011-08-18 8:07 ` Roland Vossen
2011-08-19 14:32 ` Roland Vossen
2011-08-19 15:21 ` Camaleón
2011-08-21 21:43 ` Camaleón
2011-08-22 10:03 ` Roland Vossen
2011-08-22 11:27 ` Camaleón
2011-08-22 12:57 ` Roland Vossen
2011-08-22 13:28 ` Camaleón
2011-08-22 13:55 ` Roland Vossen
2011-08-22 14:27 ` Camaleón
2011-08-23 8:41 ` Roland Vossen
2011-08-23 8:59 ` Camaleón
2011-08-23 9:27 ` Roland Vossen
2011-08-23 9:53 ` Camaleón
2011-08-23 10:38 ` Roland Vossen
2011-08-23 10:53 ` Camaleón
2011-08-23 11:23 ` Roland Vossen
2011-08-23 14:06 ` Camaleón
2011-08-23 14:18 ` Roland Vossen
2011-08-23 14:48 ` Camaleón
2011-08-23 14:58 ` Roland Vossen
2011-08-23 15:27 ` Camaleón
2011-08-23 17:37 ` Roland Vossen
2011-08-23 18:01 ` Camaleón
2011-08-22 14:15 ` Roland Vossen
2011-08-22 14:28 ` Camaleón
2011-08-22 16:37 ` Dan Williams
2011-08-19 20:47 ` Dan Williams
2011-08-22 6:52 ` Roland Vossen
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=4E4B9A45.5090507@broadcom.com \
--to=rvossen@broadcom.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=dcbw@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=networkmanager-list@gnome.org \
--cc=noelamac@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;
as well as URLs for NNTP newsgroup(s).