From: Eric Dumazet <eric.dumazet@gmail.com>
To: Nico Schottelius <nico-linux-20111017@schottelius.org>
Cc: Arend van Spriel <arend@broadcom.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: BUG: All network processes hang (brcmsmac/wpa_supplicant)
Date: Wed, 19 Oct 2011 16:46:24 +0200 [thread overview]
Message-ID: <1319035584.8416.34.camel@edumazet-laptop> (raw)
In-Reply-To: <20111019142837.GA1414@schottelius.org>
Le mercredi 19 octobre 2011 à 16:28 +0200, Nico Schottelius a écrit :
> Triggered it!
>
> And also got the traceback!
>
> Dmesg + log attached, let me know when I can pull the fix from
> somewhere.
>
Sorry, I cant see same messages in your dmesg, no mention of stuck
processes (blocked for more than 120 seconds.)
By the way, please update to latest 3.1.rc10
next prev parent reply other threads:[~2011-10-19 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111018111422.GA1979@schottelius.org>
2011-10-18 12:24 ` BUG: All network processes hang (brcmsmac/wpa_supplicant) Eric Dumazet
2011-10-19 12:36 ` Nico Schottelius
2011-10-19 12:49 ` Eric Dumazet
2011-10-19 12:58 ` Arend van Spriel
[not found] ` <4E9EC96E.8020303-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
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
[not found] ` <20111019142837.GA1414@schottelius.org>
2011-10-19 14:43 ` Arend van Spriel
2011-10-19 14:46 ` Eric Dumazet [this message]
2011-10-19 14:58 ` Nico Schottelius
[not found] ` <4E9EE20F.1030403@broadcom.com>
2011-10-19 14:55 ` Nico Schottelius
2011-10-19 16:48 ` Arend van Spriel
[not found] ` <4E9EFF51.6000104@broadcom.com>
2011-10-19 21:42 ` Nico Schottelius
2011-10-20 6:28 ` Arend van Spriel
[not found] ` <4E9FBFA7.4040502@broadcom.com>
2011-10-22 1:59 ` Nico Schottelius
[not found] <20111018133408.GA16341@schottelius.org>
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=1319035584.8416.34.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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