Re: Kernel bug in bcm43xx-d80211

Re: Kernel bug in bcm43xx-d80211

[Pavel Roskin]

On Mon, 2007-02-19 at 23:12 +0100, Johannes Berg wrote:
> On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
> > 
> > Feb 19 16:17:42 boss kernel: [  377.359573] BUG: unable to handle kernel NULL pointer dereference
> > at virtual address 00000002
> 
> Probably caused by my recent changes that accidentally broke d80211
> pretty much completely. Patches are on the linux-wireless mailing list.

Johannes, would it be possible to commit patches faster, please?  Now
that I told Michael about git-update-server-info, his changes are
downloadable as soon as he makes a commit.  wireless-dev.git, on the
other hand, is a mess and has been for some time (since Friday, I
believe).

It is a problem for projects like DadWifi that recommend to use the top
of wireless-dev.git.  Yes, I know, breakage is unavoidable to a certain
degree, but it shouldn't come to the situation when the patches are
known, nobody objects, yet the repository stays broken and all newcomers
have to be told about the problem.

That's not to offend you or anyone.  It's just something that would help
a lot.

-- 
Regards,
Pavel Roskin

Re: Kernel bug in bcm43xx-d80211

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

On Mon, 2007-02-19 at 17:30 -0500, Pavel Roskin wrote:

> Johannes, would it be possible to commit patches faster, please?  Now
> that I told Michael about git-update-server-info, his changes are
> downloadable as soon as he makes a commit.  wireless-dev.git, on the
> other hand, is a mess and has been for some time (since Friday, I
> believe).

I don't commit to wireless-dev, John does. I'd love if the patches were
in already ;) And I think he even said he had committed them but they
didn't show up so something must have gone wrong (forgot to push out to
kernel.org maybe)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: Kernel bug in bcm43xx-d80211

[Alex Davis]

--- Pavel Roskin <proski@gnu.org> wrote:

> On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
> 
> Wireless topics moved from this list to linux-wireless@vger.kernel.org.
> Broadcom drivers are discussed in bcm43xx-dev@lists.berlios.de.
> wireless-dev is horribly broken, and the fixes haven't been merged yet.
> 
> The current Broadcom driver can be loaded from
> http://bu3sch.de/git/wireless-dev.git (please load it on top of
> wireless-dev.git to save bandwidth)
What command do I use to load Mike's tree on top of wireless-dev?

Thanks

I code, therefore I am


 
____________________________________________________________________________________
Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html

Re: Kernel bug in bcm43xx-d80211

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

On Mon, 2007-02-19 at 15:48 -0800, Alex Davis wrote:
> --- Pavel Roskin <proski@gnu.org> wrote:
> 
> > On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > > I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
> > 
> > Wireless topics moved from this list to linux-wireless@vger.kernel.org.
> > Broadcom drivers are discussed in bcm43xx-dev@lists.berlios.de.
> > wireless-dev is horribly broken, and the fixes haven't been merged yet.
> > 
> > The current Broadcom driver can be loaded from
> > http://bu3sch.de/git/wireless-dev.git (please load it on top of
> > wireless-dev.git to save bandwidth)

> What command do I use to load Mike's tree on top of wireless-dev?

actually, get Jiri's
(http://www.kernel.org/git/linux/kernel/git/jbenc/dscape.git), he's just
committed the fixes.

To merge it in, just git-pull it (and see the docs)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: Kernel bug in bcm43xx-d80211

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 254 bytes --]

On Tue, 2007-02-20 at 01:08 +0100, Johannes Berg wrote:

> actually, get Jiri's
> (http://www.kernel.org/git/linux/kernel/git/jbenc/dscape.git), he's just
> committed the fixes.

Well I thought so, but apparently it isn't there yet...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: Kernel bug in bcm43xx-d80211

[Larry Finger]

Alex Davis wrote:
> --- Pavel Roskin <proski@gnu.org> wrote:
> 
>> On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
>>> I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
>> Wireless topics moved from this list to linux-wireless@vger.kernel.org.
>> Broadcom drivers are discussed in bcm43xx-dev@lists.berlios.de.
>> wireless-dev is horribly broken, and the fixes haven't been merged yet.
>>
>> The current Broadcom driver can be loaded from
>> http://bu3sch.de/git/wireless-dev.git (please load it on top of
>> wireless-dev.git to save bandwidth)
> What command do I use to load Mike's tree on top of wireless-dev?

While in the wireless-dev tree, issue the following:

git branch michael
git checkout michael
git pull http://bu3sch.de/git/wireless-dev.git master

To get back to the original wireless-dev tree, us a 'git checkout master' command.

Larry

Re: Kernel bug in bcm43xx-d80211

[Jiri Benc]

On Tue, 20 Feb 2007 01:14:16 +0100, Johannes Berg wrote:
> > actually, get Jiri's
> > (http://www.kernel.org/git/linux/kernel/git/jbenc/dscape.git), he's just
> > committed the fixes.
> 
> Well I thought so, but apparently it isn't there yet...

You need to pull the 'up' branch :-)

 Jiri

-- 
Jiri Benc
SUSE Labs

Re: Kernel bug in bcm43xx-d80211

[Pavel Roskin]

On Mon, 2007-02-19 at 15:48 -0800, Alex Davis wrote:
> --- Pavel Roskin <proski@gnu.org> wrote:
> 
> > On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > > I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
> > 
> > Wireless topics moved from this list to linux-wireless@vger.kernel.org.
> > Broadcom drivers are discussed in bcm43xx-dev@lists.berlios.de.
> > wireless-dev is horribly broken, and the fixes haven't been merged yet.
> > 
> > The current Broadcom driver can be loaded from
> > http://bu3sch.de/git/wireless-dev.git (please load it on top of
> > wireless-dev.git to save bandwidth)
> What command do I use to load Mike's tree on top of wireless-dev?

This should do it for you:

git-remote add bcm43xx http://bu3sch.de/git/wireless-dev.git
git-branch bcm43xx
git-config branch.bcm43xx.remote bcm43xx
git-config branch.bcm43xx.merge refs/heads/master
git-checkout bcm43xx
git-pull

Sorry, I didn't expect it to be so hairy.  Perhaps it should be
documented somewhere.

-- 
Regards,
Pavel Roskin

Re: Kernel bug in bcm43xx-d80211

[Alex Davis]

--- Pavel Roskin <proski@gnu.org> wrote:

> On Mon, 2007-02-19 at 15:48 -0800, Alex Davis wrote:
> > --- Pavel Roskin <proski@gnu.org> wrote:
> > 
> > > On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > > > I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
> > > 
> > > Wireless topics moved from this list to linux-wireless@vger.kernel.org.
> > > Broadcom drivers are discussed in bcm43xx-dev@lists.berlios.de.
> > > wireless-dev is horribly broken, and the fixes haven't been merged yet.
> > > 
> > > The current Broadcom driver can be loaded from
> > > http://bu3sch.de/git/wireless-dev.git (please load it on top of
> > > wireless-dev.git to save bandwidth)
> > What command do I use to load Mike's tree on top of wireless-dev?
> 
> This should do it for you:
> 
> git-remote add bcm43xx http://bu3sch.de/git/wireless-dev.git
> git-branch bcm43xx
> git-config branch.bcm43xx.remote bcm43xx
> git-config branch.bcm43xx.merge refs/heads/master
> git-checkout bcm43xx
> git-pull
> 
> Sorry, I didn't expect it to be so hairy.  Perhaps it should be
> documented somewhere.
> 
> -- 
> Regards,
> Pavel Roskin

I appreciate all the help, but now I'm confused. I got these instructions from Larry Finger:
git branch michael
git checkout michael
git pull http://bu3sch.de/git/wireless-dev.git master

And these instructions from Pavel Roskin:
git-remote add bcm43xx http://bu3sch.de/git/wireless-dev.git
git-branch bcm43xx
git-config branch.bcm43xx.remote bcm43xx
git-config branch.bcm43xx.merge refs/heads/master
git-checkout bcm43xx
git-pull

Which set of instructions do I use? Are either of these still applicable, seeing as I was asked
to pull from Jiri Benc's tree?

Thanks


I code, therefore I am


 
____________________________________________________________________________________
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121

Re: Kernel bug in bcm43xx-d80211

[Pavel Roskin]

On Mon, 2007-02-19 at 16:40 -0800, Alex Davis wrote:

> I appreciate all the help, but now I'm confused. I got these
> instructions from Larry Finger:
> git branch michael
> git checkout michael
> git pull http://bu3sch.de/git/wireless-dev.git master
> 
> And these instructions from Pavel Roskin:
> git-remote add bcm43xx http://bu3sch.de/git/wireless-dev.git
> git-branch bcm43xx
> git-config branch.bcm43xx.remote bcm43xx
> git-config branch.bcm43xx.merge refs/heads/master
> git-checkout bcm43xx
> git-pull
> 
> Which set of instructions do I use? Are either of these still
> applicable, seeing as I was asked
> to pull from Jiri Benc's tree?

The only difference is that I provided git-remote and git-config
commands that would change the configuration to make "git pull" work
every time without arguments on both branches, whereas if you follow
Larry's instructions, you'll need to provide the URL and the branch to
merge every time you are on the "michael" branch.

The name of the branch is different, but it's your choice.  "git-XXX" is
equivalent to "git XXX", but I prefer the former because bash will
complete the command.  Again, it doesn't really matter.

-- 
Regards,
Pavel Roskin

Re: Kernel bug in bcm43xx-d80211

[Jiri Benc]

On Mon, 19 Feb 2007 16:40:15 -0800 (PST), Alex Davis wrote:
> I appreciate all the help, but now I'm confused. I got these instructions from Larry Finger:
> git branch michael
> git checkout michael
> git pull http://bu3sch.de/git/wireless-dev.git master

This is easier for one-time pull.

> And these instructions from Pavel Roskin:
> git-remote add bcm43xx http://bu3sch.de/git/wireless-dev.git
> git-branch bcm43xx
> git-config branch.bcm43xx.remote bcm43xx
> git-config branch.bcm43xx.merge refs/heads/master
> git-checkout bcm43xx
> git-pull

This is useful if you want to pull regularly. But Larry's way can be used
even in that case - I'm pulling regularly from wireless-dev and never used
git-config :-)

Also, Larry's advice about getting back to the original wireless-dev tree
could be useful for you. It applies to both Larry's and Pavel's
instructions.

> Which set of instructions do I use? Are either of these still applicable, seeing as I was asked
> to pull from Jiri Benc's tree?

If you pull from my tree, you won't be able to compile any d80211 driver.
The wireless statistics fixes need to be committed by John first.

 Jiri

-- 
Jiri Benc
SUSE Labs

Re: Kernel bug in bcm43xx-d80211

[Alex Davis]

--- Pavel Roskin <proski@gnu.org> wrote:

> On Mon, 2007-02-19 at 15:48 -0800, Alex Davis wrote:
> > --- Pavel Roskin <proski@gnu.org> wrote:
> >=20
> > > On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > > > I go the following Oops with the latest wireless-dev git when s=
tarting wpa_supplicant:
> > >=20
> > > Wireless topics moved from this list to linux-wireless@vger.kerne=
l.org.
> > > Broadcom drivers are discussed in bcm43xx-dev@lists.berlios.de.
> > > wireless-dev is horribly broken, and the fixes haven't been merge=
d yet.
> > >=20
> > > The current Broadcom driver can be loaded from
> > > http://bu3sch.de/git/wireless-dev.git (please load it on top of
> > > wireless-dev.git to save bandwidth)
> > What command do I use to load Mike's tree on top of wireless-dev?
>=20
> This should do it for you:
>=20
> git-remote add bcm43xx http://bu3sch.de/git/wireless-dev.git
> git-branch bcm43xx
> git-config branch.bcm43xx.remote bcm43xx
> git-config branch.bcm43xx.merge refs/heads/master
> git-checkout bcm43xx
> git-pull
>=20
> Sorry, I didn't expect it to be so hairy.  Perhaps it should be
> documented somewhere.
>=20
I merged Michael's changes. It doesn't panic anymore, but I still can't=
 associate. Here's the
output from wpa_supplicant 0.4.9:

ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not support=
ed
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not support=
ed
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource bu=
sy
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not support=
ed
WEXT auth param 4 value 0x0 - Trying to associate with 00:0f:66:d9:25:9=
1 (SSID=3D'ace' freq=3D2437
MHz)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0f:66:d9:25:91 (SSID=3D'ace' freq=3D2437 MH=
z)
Association request to the driver failed
CTRL-EVENT-TERMINATING - signal 15 received

Here's the dmesg when the driver is loaded:
[   65.113061] ssb: Sonics Silicon Backplane found on PCI device 0000:0=
2:03.0
[   65.116542] bcm43xx_d80211: Broadcom 4306 WLAN found
[   65.261596] wmaster0: Selected rate control algorithm 'simple'
[   65.344671] bcm43xx_d80211: Adding Interface type 2
[   65.446213] bcm43xx_d80211: Found PHY: Analog 2, Type 2, Revision 2
[   65.446235] bcm43xx_d80211: Found Radio: Manuf 0x17F, Version 0x2050=
, Revision 2
[   65.568141] bcm43xx_d80211: Loading firmware version 371.1122 (2006-=
11-08 22:02:13)
[   65.576305] bcm43xx_d80211: Radio turned on
[   65.576310] bcm43xx_d80211: Radio enabled by hardware
[   65.696296] bcm43xx_d80211: Chip initialized
[   65.696466] bcm43xx_d80211: 30-bit DMA initialized
[   65.712733] bcm43xx_d80211: Wireless interface started
[   65.712755] wmaster0: Does not support passive scan, disabled
[   75.700550] wlan0: no IPv6 routers present

Here's trying to associante via wpa_supplicant:
[ 3555.573064] wlan0: starting scan
[ 3556.458869] wlan0: scan completed
[ 3556.459048] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3556.467250] wlan0: Initial auth_alg=3D0
[ 3556.467254] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3556.670310] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3556.869811] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3557.069311] wlan0: authentication with AP 00:0f:66:d9:25:91 timed ou=
t
[ 3561.458416] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3561.458478] wlan0: starting scan
[ 3562.344163] wlan0: scan completed
[ 3562.344287] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3567.333708] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3567.333769] wlan0: starting scan
[ 3568.219441] wlan0: scan completed
[ 3568.219571] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3573.209003] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3573.209065] wlan0: starting scan
[ 3574.094760] wlan0: scan completed
[ 3574.094882] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3579.084302] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3579.084363] wlan0: starting scan
[ 3579.970041] wlan0: scan completed
[ 3580.021891] bcm43xx_d80211: Removing Interface type 2
[ 3580.021910] bcm43xx_d80211: Wireless interface stopped
[ 3580.021915] bcm43xx_d80211: DMA-32 0x0200 (RX) max used slots: 1/64
[ 3580.021950] bcm43xx_d80211: DMA-32 0x02A0 (TX) max used slots: 0/128
[ 3580.022257] bcm43xx_d80211: DMA-32 0x0280 (TX) max used slots: 0/128
[ 3580.022564] bcm43xx_d80211: DMA-32 0x0260 (TX) max used slots: 0/128
[ 3580.022870] bcm43xx_d80211: DMA-32 0x0240 (TX) max used slots: 0/128
[ 3580.023176] bcm43xx_d80211: DMA-32 0x0220 (TX) max used slots: 0/128
[ 3580.023483] bcm43xx_d80211: DMA-32 0x0200 (TX) max used slots: 0/128
[ 3580.023792] bcm43xx_d80211: Radio turned off
[ 3680.040344] bcm43xx_d80211: Adding Interface type 2
[ 3680.141356] bcm43xx_d80211: Found PHY: Analog 2, Type 2, Revision 2
[ 3680.141378] bcm43xx_d80211: Found Radio: Manuf 0x17F, Version 0x2050=
, Revision 2
[ 3680.200510] bcm43xx_d80211: Loading firmware version 371.1122 (2006-=
11-08 22:02:13)
[ 3680.208672] bcm43xx_d80211: Radio turned on
[ 3680.208677] bcm43xx_d80211: Radio enabled by hardware
[ 3680.329891] bcm43xx_d80211: Chip initialized
[ 3680.330074] bcm43xx_d80211: 30-bit DMA initialized
[ 3680.346356] bcm43xx_d80211: Wireless interface started
[ 3680.346374] wmaster0: Does not support passive scan, disabled
[ 3680.520414] wlan0: starting scan
[ 3681.396239] wlan0: scan completed
[ 3681.396476] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3681.396676] wlan0: Initial auth_alg=3D0
[ 3681.396679] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3681.597712] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3681.797212] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3681.996713] wlan0: authentication with AP 00:0f:66:d9:25:91 timed ou=
t
[ 3686.385815] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3686.385868] wlan0: starting scan
[ 3687.271537] wlan0: scan completed
[ 3687.271713] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3691.103921] wlan0: no IPv6 routers present
[ 3692.261104] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3692.261162] wlan0: starting scan
[ 3693.146836] wlan0: scan completed
[ 3693.146987] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3697.006343] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3697.059037] bcm43xx_d80211: Removing Interface type 2
[ 3697.059055] bcm43xx_d80211: Wireless interface stopped
[ 3697.059060] bcm43xx_d80211: DMA-32 0x0200 (RX) max used slots: 1/64
[ 3697.059086] bcm43xx_d80211: DMA-32 0x02A0 (TX) max used slots: 0/128
[ 3697.059392] bcm43xx_d80211: DMA-32 0x0280 (TX) max used slots: 0/128
[ 3697.059699] bcm43xx_d80211: DMA-32 0x0260 (TX) max used slots: 0/128
[ 3697.060005] bcm43xx_d80211: DMA-32 0x0240 (TX) max used slots: 0/128
[ 3697.060311] bcm43xx_d80211: DMA-32 0x0220 (TX) max used slots: 0/128
[ 3697.060617] bcm43xx_d80211: DMA-32 0x0200 (TX) max used slots: 0/128
[ 3697.060926] bcm43xx_d80211: Radio turned off
[ 3723.125212] bcm43xx_d80211: Adding Interface type 2
[ 3723.223555] bcm43xx_d80211: Found PHY: Analog 2, Type 2, Revision 2
[ 3723.223576] bcm43xx_d80211: Found Radio: Manuf 0x17F, Version 0x2050=
, Revision 2
[ 3723.282700] bcm43xx_d80211: Loading firmware version 371.1122 (2006-=
11-08 22:02:13)
[ 3723.290858] bcm43xx_d80211: Radio turned on
[ 3723.290863] bcm43xx_d80211: Radio enabled by hardware
[ 3723.407607] bcm43xx_d80211: Chip initialized
[ 3723.407783] bcm43xx_d80211: 30-bit DMA initialized
[ 3723.424049] bcm43xx_d80211: Wireless interface started
[ 3723.424067] wmaster0: Does not support passive scan, disabled
[ 3723.632545] wlan0: starting scan
[ 3724.518336] wlan0: scan completed
[ 3724.518468] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3724.518572] wlan0: Initial auth_alg=3D0
[ 3724.518577] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3724.719810] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3724.919310] wlan0: authenticate with AP 00:0f:66:d9:25:91
[ 3725.118811] wlan0: authentication with AP 00:0f:66:d9:25:91 timed ou=
t
[ 3729.507850] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3729.507926] wlan0: starting scan
[ 3730.393635] wlan0: scan completed
[ 3730.393728] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3733.517793] wlan0: no IPv6 routers present
[ 3735.383154] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3735.383211] wlan0: starting scan
[ 3736.268934] wlan0: scan completed
[ 3736.269050] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3741.258474] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3741.258530] wlan0: starting scan
[ 3742.144233] wlan0: scan completed
[ 3742.144330] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3747.133744] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3747.133795] wlan0: starting scan
[ 3748.019530] wlan0: scan completed
[ 3748.019616] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3753.009047] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3753.009101] wlan0: starting scan
[ 3753.894829] wlan0: scan completed
[ 3753.894933] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3758.884346] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3758.884400] wlan0: starting scan
[ 3759.770133] wlan0: scan completed
[ 3759.770275] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3764.759642] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3764.759695] wlan0: starting scan
[ 3765.645427] wlan0: scan completed
[ 3765.645517] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3770.634948] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3770.635004] wlan0: starting scan
[ 3771.520733] wlan0: scan completed
[ 3771.520832] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3776.510239] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3776.510305] wlan0: starting scan
[ 3777.396023] wlan0: scan completed
[ 3777.396111] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3782.385534] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3782.385585] wlan0: starting scan
[ 3783.271322] wlan0: scan completed
[ 3783.271408] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3788.260835] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3788.260886] wlan0: starting scan
[ 3789.136645] wlan0: scan completed
[ 3789.136731] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3794.126162] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3794.126214] wlan0: starting scan
[ 3795.011945] wlan0: scan completed
[ 3795.012042] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3799.213881] bcm43xx_d80211: Using hardware based encryption for keyi=
dx: 0, mac:
ff:ff:ff:ff:ff:ff
[ 3799.273272] bcm43xx_d80211: Removing Interface type 2
[ 3799.273290] bcm43xx_d80211: Wireless interface stopped
[ 3799.273294] bcm43xx_d80211: DMA-32 0x0200 (RX) max used slots: 1/64
[ 3799.273320] bcm43xx_d80211: DMA-32 0x02A0 (TX) max used slots: 0/128
[ 3799.273625] bcm43xx_d80211: DMA-32 0x0280 (TX) max used slots: 0/128
[ 3799.273928] bcm43xx_d80211: DMA-32 0x0260 (TX) max used slots: 0/128
[ 3799.274232] bcm43xx_d80211: DMA-32 0x0240 (TX) max used slots: 0/128
[ 3799.274535] bcm43xx_d80211: DMA-32 0x0220 (TX) max used slots: 0/128
[ 3799.274839] bcm43xx_d80211: DMA-32 0x0200 (TX) max used slots: 0/128
[ 3799.275145] bcm43xx_d80211: Radio turned off

I'm reposting the following for the bcm43xx mailing list.

lspci
02:03.0 Network controller: Broadcom Corporation BCM4309 802.11a/b/g (r=
ev 03)
        Subsystem: Dell Truemobile 1450 MiniPCI
        Flags: bus master, fast devsel, latency 32, IRQ 18
        Memory at faff6000 (32-bit, non-prefetchable) [size=3D8K]

Relevant part of .config
CONFIG_BCM43XX=3Dm
CONFIG_BCM43XX_DEBUG=3Dy
CONFIG_BCM43XX_DMA=3Dy
CONFIG_BCM43XX_PIO=3Dy
CONFIG_BCM43XX_DMA_AND_PIO_MODE=3Dy
# CONFIG_BCM43XX_DMA_MODE is not set
# CONFIG_BCM43XX_PIO_MODE is not set
# CONFIG_ZD1211RW is not set
CONFIG_BCM43XX_D80211=3Dm
CONFIG_BCM43XX_D80211_PCI=3Dy
CONFIG_BCM43XX_D80211_PCMCIA=3Dy
CONFIG_BCM43XX_D80211_DEBUG=3Dy
CONFIG_BCM43XX_D80211_DMA=3Dy
CONFIG_BCM43XX_D80211_PIO=3Dy
CONFIG_BCM43XX_D80211_DMA_AND_PIO_MODE=3Dy
# CONFIG_BCM43XX_D80211_DMA_MODE is not set
# CONFIG_BCM43XX_D80211_PIO_MODE is not set
# CONFIG_RT2X00 is not set
# CONFIG_ADM8211 is not set
# CONFIG_P54_COMMON is not set
# CONFIG_ZD1211RW_D80211 is not set
CONFIG_NET_WIRELESS=3Dy


I'm using Wireless Tools v28

Another thing I've noticed: the output from iwconfig is corrupted:
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     v=B2#=C0=FC=B0=BFwlan0  ESSID:"ace" [176]  Nickname:"bos"
          Channel=3D-inf  Access Point: 23:C0:F0:1A:B0:BF   Bit Rate=3D=
-1.0714e+06 kb/s
          RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:90/100  Signal level:-38 dBm  Noise level:-96 dB=
m
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


Thanks for any info.


I code, therefore I am


=20
_______________________________________________________________________=
_____________
It's here! Your new message! =20
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel bug in bcm43xx-d80211

[Pavel Roskin]

Quoting Alex Davis <alex14641@yahoo.com>:

> I merged Michael's changes. It doesn't panic anymore, but I still can't
> associate. Here's the
> output from wpa_supplicant 0.4.9:

I'm sorry!  I didn't realize git would be merging two branches.  I did try my
commands, but I didn't notice the message about merging.

If you merge two branches, you are pulling the bugs from wireless.dev into the
bcm43xx branch.

You need to remove the merge by resetting the local branch to the remote branch.
 Please use this command:

git-reset --hard remotes/bcm43xx/master

bcm43xx is the name you used in the git-remote command.  Perhaps we need some
kind of git wrapper to deal with all that complexity of having multiple remotes
in one repository.  I'll ask in the git list.  It doesn't look like an exotic
case anymore.

Once you have reverted the branch, disable CONFIG_CFG80211 in .config - it's not
ready yet.  This would fix the iwconfig output.

As for association timeout, it's probably unrelated, bit it would be helpful if
you recheck it on clean sources.  It's possible wpa_supplicant doesn't get the
AP MAC address properly.

--
Regards,
Pavel Roskin

Re: Kernel bug in bcm43xx-d80211

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 439 bytes --]

On Mon, 2007-02-19 at 22:54 -0500, Pavel Roskin wrote:

> Once you have reverted the branch, disable CONFIG_CFG80211 in .config - it's not
> ready yet.  This would fix the iwconfig output.

I don't think that's actually true, the iwconfig output typo bug is
present in that part of the code that is always enabled whether you have
CFG80211 or not. You're just assuming that it would fix it because it
did weeks ago ;)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]