From: "Arend van Spriel" <arend@broadcom.com>
To: "Nico Schottelius" <nico-linux-20111017@schottelius.org>
Cc: "Eric Dumazet" <eric.dumazet@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BUG: All network processes hang (brcmsmac/wpa_supplicant)
Date: Mon, 24 Oct 2011 14:50:27 +0200 [thread overview]
Message-ID: <4EA55F13.5020300@broadcom.com> (raw)
In-Reply-To: <20111023194823.GB2489@schottelius.org>
On 10/23/2011 09:48 PM, Nico Schottelius wrote:
> Update, just triggered it after a suspend/resume cycle:
>
> This changes every some seconds right now, because the connection
> is established/shutdown and thus dhcpcd retries to get the ip address
> every few seconds.
>
> I've restarted the AP, but the situation stays the same.
>
> The other devices in the network work fine, so it's really my system
> that behaves "funny".
>
> After that I've reloaded brcmsmac at 84262.797365, after which
> the connection time lasted longer, but was also interrupted some
> time later.
>
> dmesg attached again.
>
> Cheers,
>
> Nico
>
I tried to make sense of the dmesg log you sent me. Not sure what is
happening so could do the following:
1. Determine wpa_supplicant version using -v option.
2. Add '-ddt' option in DBus service file:
wpa_supplicant >= 0.7: fi.w1.wpa_supplicant1.service
wpa_supplicant < 0.7: fi.epitest.hostap.WPASupplicant.service
(located in /usr/share/dbus-1/system-services/).
3. Reproduce the problem and sent /var/log/syslog.
Thanks
AvS
next prev parent reply other threads:[~2011-10-24 12:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111018111422.GA1979@schottelius.org>
2011-10-18 13:14 ` BUG: All network processes hang (brcmsmac/wpa_supplicant) Arend van Spriel
2011-10-18 13:34 ` Nico Schottelius
[not found] ` <1318940665.2657.60.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
2011-10-19 12:36 ` Nico Schottelius
2011-10-19 12:49 ` Eric Dumazet
2011-10-19 12:58 ` Arend van Spriel
2011-10-19 13:05 ` Eric Dumazet
2011-10-19 13:09 ` Nico Schottelius
2011-10-19 13:07 ` Nico Schottelius
2011-10-19 14:28 ` Nico Schottelius
2011-10-19 14:43 ` Arend van Spriel
2011-10-19 14:55 ` Nico Schottelius
2011-10-19 16:48 ` Arend van Spriel
2011-10-19 21:42 ` Nico Schottelius
2011-10-20 6:28 ` Arend van Spriel
2011-10-22 1:59 ` Nico Schottelius
2011-10-22 8:13 ` Arend Van Spriel
2011-10-22 8:30 ` Greg KH
2011-10-22 8:44 ` Arend van Spriel
2011-10-23 10:04 ` Arend van Spriel
2011-10-23 10:53 ` Nico Schottelius
2011-10-23 19:48 ` Nico Schottelius
2011-10-24 12:50 ` Arend van Spriel [this message]
2011-10-25 6:41 ` Nico Schottelius
2011-10-19 14:46 ` Eric Dumazet
2011-10-19 14:58 ` Nico Schottelius
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=4EA55F13.5020300@broadcom.com \
--to=arend@broadcom.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nico-linux-20111017@schottelius.org \
/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).