From: "Arend van Spriel" <arend@broadcom.com>
To: "Nico Schottelius" <nico-linux-20111201@schottelius.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, b43-dev@lists.infradead.org,
"Greg KH" <gregkh@suse.de>
Subject: Re: BCM43224 hanging [3.2.0-rc4-00248-gb835c0f]
Date: Thu, 8 Dec 2011 18:34:03 +0100 [thread overview]
Message-ID: <4EE0F50B.5040407@broadcom.com> (raw)
In-Reply-To: <20111207190821.GA1775@schottelius.org>
On 12/07/2011 08:08 PM, Nico Schottelius wrote:
> Update:
>
> The hang situation always happens, when the nic does *not* have
> a connection. And it still covers all network processes (i.e.
> including sudo, wpa_supplicant, postfix, etc.).
>
> Starting up the computer, having wpa_supplicant connect successfully,
> everything works fine.
>
> Until the connection is lost or I issue "select_network 4", which
> changes to another network.
>
> The problem also exists, if I startup wpa_supplicant and there
> is no network connection available.
>
> Verified that this bug exists in my pathced 3.1.0-rc6-g443452b
> as well as in 3.2.0-rc4-00248-gb835c0f.
>
> This is rather nasty, because it forces me to reboot as soon as
> I've started up wlan by accident.
>
> Is there a workaround available somewhere (besides using USB-LAN)?
>
> Attached are output of 3.1.0-rc6-g443452b, which is the same for
> all failing versions.
>
> Cheers,
>
> Nico
Could you try and see what happens when you kill wpa_supplicant.
Gr. AvS
next prev parent reply other threads:[~2011-12-08 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 22:48 BCM43224: 00:00:00:00:00:00 address (3.2.0-rc3-00099-g883381d) Nico Schottelius
2011-12-02 11:27 ` Arend van Spriel
2011-12-02 15:01 ` Nico Schottelius
2011-12-07 19:08 ` BCM43224 hanging [3.2.0-rc4-00248-gb835c0f] (was: BCM43224: 00:00:00:00:00:00 address (3.2.0-rc3-00099-g883381d)) Nico Schottelius
2011-12-08 17:34 ` Arend van Spriel [this message]
2011-12-09 18:00 ` BCM43224 hanging [3.2.0-rc4-00248-gb835c0f] Nico Schottelius
2011-12-12 18:16 ` BCM43224 hanging [3.2.0-rc4-00248-gb835c0f] (was: BCM43224: 00:00:00:00:00:00 address (3.2.0-rc3-00099-g883381d)) Nico Schottelius
2011-12-14 11:21 ` BCM43224 hanging [3.2.0-rc5] (was: [3.2.0-rc4-00248-gb835c0f] ...) Nico Schottelius
2011-12-22 10:24 ` Nico Schottelius
2011-12-22 13:19 ` BCM43224 hanging [3.2.0-rc5] Arend van Spriel
2011-12-31 11:48 ` 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=4EE0F50B.5040407@broadcom.com \
--to=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico-linux-20111201@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.