All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-linux-20111017@schottelius.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Nico Schottelius <nico-linux-20111017@schottelius.org>,
	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:58:00 +0200	[thread overview]
Message-ID: <20111019145800.GC1414@schottelius.org> (raw)
In-Reply-To: <1319035584.8416.34.camel@edumazet-laptop>

Eric Dumazet [Wed, Oct 19, 2011 at 04:46:24PM +0200]:
> 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
 
I can rebuild Linus' tree if you want, but only use it temporarily due
to the other errors mentioned in the previous message.

If you've a tree somewhere that merges on top of Keith+Jiri,
I'd try to merge that one as well, to make the mba more usable.

Cheers,

Nico

-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

  reply	other threads:[~2011-10-19 14: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
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 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-20  6:28                   ` 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 [this message]
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=20111019145800.GC1414@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 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.