netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Ray Lee <ray-gmail-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>,
	"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: Bcm43xx softMac Driver in 2.6.18
Date: Sat, 23 Sep 2006 13:00:36 -0500	[thread overview]
Message-ID: <45157644.9020305@lwfinger.net> (raw)
In-Reply-To: <45156612.2080906-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>

Ray Lee wrote:
> Rafael J. Wysocki wrote:
>>> 2.6.18 vanilla and 2.6.18 with your patch both lock my system hard
>>> with bcm43xx. I've got an HP/Compaq nx6125 laptop. Symptoms are that
>>> it will associate fine on its own and send traffic to/fro upon ifup,
>>> but when I do an iwconfig, ifdown, ifup to change the access point,
>>> the system locks (somewhat randomly) during one of those operations.
>>> Well, the iwconfig or the ifup, actually.
>> I have observed similar symptoms on HPC nx6325, although I haven't managed
>> to get the adapter associate with an AP.
> 
> Yeah, I'm having the same troubles. Carefully watching the iwconfig
> results showed me that only half of the time did my `iwconfig eth1 essid
> AccessPointName` actually take. (It listed the essid of the ap I told it
> to associate with, but then showed "Access Point: Invalid" or words to
> that effect, until I issued the exact same iwconfig again.)
> 
> So, try it twice, double check the iwconfig output, then try bringing up
> the interface. Though that seems awfully difficult to do as well (DHCP
> is just sending out stuff with nothing coming back).
> 
> When I switch consoles while DHCP is plaintively asking for an IP, and
> issue *another* iwconfig with the same essid, then it seems to kick
> something in the driver and DHCP immediately associates. Happened twice
> for me so far, though that could merely be a coincidence.
> 

I don't know about the problems associating, and/or with changing APs - I have only one and it
associates and authenticates with WPA-PSK without any trouble.

As to the lockups that you are seeing, I have generated a diff between vanilla 2.6.18 and
wireless-2.6 with some essential patches added. At the moment, I'm compiling and testing it. There
are more problems with locking than I realized. If the patch works here, I'll post it to you and to
the bcm43xx list. The hard part may be getting stable to accept it for 2.6.18.1.

Thanks for the bug reports.

Larry

  parent reply	other threads:[~2006-09-23 18:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 13:20 Bcm43xx softMac Driver in 2.6.18 Larry Finger
2006-09-22 13:53 ` Erik Mouw
2006-09-22 14:31   ` Larry Finger
2006-09-23  6:03 ` Ray Lee
2006-09-23  9:41   ` Rafael J. Wysocki
2006-09-23 16:51     ` Ray Lee
     [not found]       ` <45156612.2080906-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>
2006-09-23 18:00         ` Larry Finger [this message]
2006-09-23 20:21         ` Larry Finger
2006-09-29 21:23           ` Ray Lee

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=45157644.9020305@lwfinger.net \
    --to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
    --cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ray-gmail-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org \
    --cc=rjw-KKrjLPT3xs0@public.gmane.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).