netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: bcm43xx driver unstable behaviour (and linux wireless is junk btw)
Date: Sun, 24 Sep 2006 12:43:18 +1000	[thread overview]
Message-ID: <1159065798.5924.8.camel@localhost.localdomain> (raw)

Hi folks !

So this is 2.6.18 + Larry "fix" (though I've seen this problem before,
it seems using WPA just make it happen more often).

This is also a 4318, so the link is pretty weak due to the Tx Power
problem and I suspects it makes the driver problems more visible...

So basically, I "lose" the link every few minutes for a minute or so, I
suspect it's related to wpa_supplicant vs. the ack losses due to the
4318 Tx Power problems. That alone would be ok though, if the driver
wasn't totally stuck after a while. (Similar problem to after
sleep/wakeup, looks like nothign goes through).

When it goes bunk, it looks like that in the logs:

Sep 24 12:24:18 localhost kernel: [  285.686826] SoftMAC: Sent Authentication Request to 00:0f:66:52:4b:60.
Sep 24 12:24:18 localhost kernel: [  285.686976] SoftMAC: generic IE set to <....>
Sep 24 12:24:18 localhost kernel: [  285.686999] SoftMAC: Already associating or associated to 00:0f:66:52:4b:60
Sep 24 12:24:28 localhost kernel: [  295.687229] SoftMAC: Start scanning with channel: 1
Sep 24 12:24:28 localhost kernel: [  295.687240] SoftMAC: Scanning 14 channels
Sep 24 12:24:29 localhost kernel: [  296.027053] SoftMAC: Scanning finished
Sep 24 12:24:29 localhost kernel: [  296.035267] SoftMAC: generic IE set to <....>
Sep 24 12:24:29 localhost kernel: [  296.035310] SoftMAC: Already associating or associated to 00:0f:66:52:4b:60
Sep 24 12:24:31 localhost kernel: [  297.690969] SoftMAC: Sent Authentication Request to 00:0f:66:52:4b:60.
Sep 24 12:24:39 localhost kernel: [  306.039210] SoftMAC: Start scanning with channel: 1
Sep 24 12:24:39 localhost kernel: [  306.039222] SoftMAC: Scanning 14 channels
Sep 24 12:24:39 localhost kernel: [  306.375046] SoftMAC: Scanning finished
Sep 24 12:24:39 localhost kernel: [  306.383018] SoftMAC: generic IE set to <....>
Sep 24 12:24:39 localhost kernel: [  306.383075] SoftMAC: Already associating or associated to 00:0f:66:52:4b:60
Sep 24 12:24:42 localhost kernel: [  309.695021] SoftMAC: Sent Authentication Request to 00:0f:66:52:4b:60.
Sep 24 12:24:49 localhost kernel: [  316.387211] SoftMAC: Start scanning with channel: 1

 etc...

Then, if you rmmod, you get back a prompt, and about a second later, the kernel blows up. At this point,
I've always been in X and it's too dead to dump anything into the disk logs so I don't know what
the precise crash is, but it looks to me like the driver is not properly removing some timer
or something there.

Note that it also goes "bunk" on sleep/wakeup, and sometimes ifdown/ifup... in general, it's fragile and
just 'loses it' in which case the only way to get it back is to rmmod/insmod.

Doesn't help me to have my prism54 not working with WPA (apparently, the driver looks like it handles hostap
ioctls but it doesn't agree on the ioctl numbers, among others, with whatever wpa_supplicant sends when
configured to wpa mode... somebody knows if that driver is maintained ?)

So at this point I have a choice between two wireless devices that don't work (and none of them is less than
a couple years old). Looks like the linux wireless situation isn't getting any better since last KS.

Oh and I don't care about "it works in dscape stack" sort of crap I regulary get. I want something that
works with upstream kernels. That isn't that much to ask... or is it ?

Ben, back to ethernet cables.

             reply	other threads:[~2006-09-24  2:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24  2:43 Benjamin Herrenschmidt [this message]
     [not found] ` <1159065798.5924.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24  3:45   ` bcm43xx driver unstable behaviour (and linux wireless is junk btw) Daniel Drake
     [not found]     ` <4515FF5D.4080602-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2006-09-24  6:18       ` Benjamin Herrenschmidt
     [not found]         ` <1159078683.5924.16.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24  8:05           ` Michael Buesch
     [not found]             ` <200609241005.02024.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-09-24  8:12               ` Benjamin Herrenschmidt
2006-09-24  8:43                 ` Michael Buesch
2006-09-24  8:47                   ` Benjamin Herrenschmidt
2006-09-24 15:34                   ` Daniel Drake
2006-09-24 16:38                     ` Michael Buesch
2006-09-25  9:02           ` Johannes Berg
2006-09-25  9:58             ` Benjamin Herrenschmidt
2006-09-25 10:00               ` Johannes Berg
2006-09-24  3:50 ` Dan Williams
     [not found]   ` <1159069857.2748.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24  6:13     ` Benjamin Herrenschmidt
2006-09-24 16:02       ` Dan Williams

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=1159065798.5924.8.camel@localhost.localdomain \
    --to=benh-xvmvhmargas8u2djnn8i7kb+6bgklq7r@public.gmane.org \
    --cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@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).