From: Nico Schottelius <nico-linux-20111017@schottelius.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Arend van Spriel <arend@broadcom.com>,
Nico Schottelius <nico-linux-20111017@schottelius.org>,
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 15:09:23 +0200 [thread overview]
Message-ID: <20111019130923.GA5382@schottelius.org> (raw)
In-Reply-To: <1319029529.8416.3.camel@edumazet-laptop>
Eric Dumazet [Wed, Oct 19, 2011 at 03:05:29PM +0200]:
> [...]
> make menuconfig
> -> Kernel hacking
> -> Lock debugging: prove locking correctness
Alright, rebuilding.
Nico
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
next prev parent reply other threads:[~2011-10-19 13:09 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 [this message]
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
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=20111019130923.GA5382@schottelius.org \
--to=nico-linux-20111017@schottelius.org \
--cc=arend@broadcom.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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).