All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Eric Dumazet" <eric.dumazet@gmail.com>
Cc: "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 14:58:22 +0200	[thread overview]
Message-ID: <4E9EC96E.8020303@broadcom.com> (raw)
In-Reply-To: <1319028563.8416.1.camel@edumazet-laptop>

On 10/19/2011 02:49 PM, Eric Dumazet wrote:
> Le mercredi 19 octobre 2011 à 14:36 +0200, Nico Schottelius a écrit :
>> Hello,
>>
>> I've
>>
>> Eric Dumazet [Tue, Oct 18, 2011 at 02:24:25PM +0200]:
>>> Must be a mutex_unlock(some_mltex) missing somewhere.
>>>
>>> Then later, a process holding RTNL is blocking on mutex_lock(some_mutex)
>>>
>>> Try a "CONFIG_LOCKDEP=y" enabled build
>>
>> Did so, attached is the dmesg output after 3x suspend.
>>
>> It also seems this bug gets more / only triggered when I loose the
>> connection to a wpa2-eap network that is defined like this:
>>
>> network={
>>    ssid="eth"
>>   id_str="eth-802.2x"
>>    key_mgmt=WPA-EAP
>>    proto=WPA2
>>    eap=TTLS
>>    pairwise=CCMP TKIP
>>    group=CCMP TKIP
>>    phase2="auth=MSCHAPV2"
>>    identity="MYNAME"
>>    password="forgottoremoveit"
>> }
>>
>> Hope the dmesg output helps and we can remove the problem soon
>> and making the mba finally almost completly usable :-)
>>
> 
> Sorry, no CONFIG_LOCKDEP in your config or dmesg. Maybe you sent a
> previous dmesg/config file ?
> 
> Note that you have "CONFIG_LOCKDEP_SUPPORT=y", not "CONFIG_LOCKDEP=y"
> 

Hi Eric,

Are there any configuration setting needed that CONFIG_LOCKDEP depends on?

Gr. AvS



  reply	other threads:[~2011-10-19 12:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 11:14 BUG: All network processes hang (brcmsmac/wpa_supplicant) Nico Schottelius
2011-10-18 12:24 ` Eric Dumazet
2011-10-19 12:36   ` Nico Schottelius
2011-10-19 12:36     ` Nico Schottelius
2011-10-19 12:49     ` Eric Dumazet
2011-10-19 12:58       ` Arend van Spriel [this message]
2011-10-19 13:05         ` Eric Dumazet
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: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-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 16:48               ` Arend van Spriel
2011-10-19 14:43           ` Arend van Spriel
2011-10-19 14:46           ` Eric Dumazet
2011-10-19 14:58             ` Nico Schottelius
2011-10-18 13:14 ` Arend van Spriel
2011-10-18 13:34   ` 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=4E9EC96E.8020303@broadcom.com \
    --to=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 \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.