https://bugzilla.novell.com/show_bug.cgi?id=435767 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435767#c1 --- Comment #1 from Jiri Slaby 2008-10-16 04:05:44 MDT --- Could you post dmesg after the disconnection? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435767 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435767#c3 --- Comment #3 from Jiri Slaby 2008-11-10 08:54:33 MST --- Could you try factory kernel? There are few fixes for similar malfunction. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435767 User luc.levain@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=435767#c5 Luc Levain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luc.levain@yahoo.co.uk --- Comment #5 from Luc Levain 2008-11-14 17:19:11 MST --- I can confirm that the bug still persists using openSUSE 11.1 Beta 5, running kernel 2.6.27.5-2-pae. I'm attaching the dmesg output from "rcnetwork start" to the point where I'm disconnected below. Basically, what happens is that after some time the kernel receives a "b43-phy1 ERROR: PHY transmission error" error and disconnects; it tries to reconnect several times, but fails, and finally gives up. Reconnecting manually doesn't help. Restartig the network service, and then reconnecting, works, until the bug hits again after some time. Googling for "ERROR: PHY transmission error" reveals quite a few bug reports in different distros, so quite possibly this is a bug in the kernel module. The card works just fine with ndiswrapper. Ouput: # rcnetwork restart Shutting down the NetworkManager done Shutting down network interfaces: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev10) done wlan0 name: Broadcom BCM4311 [AirForce 54g] 802.11a/b/g PCI Express Transceiver done Shutting down service network . . . . . done Starting the NetworkManager done # dmesg eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready input: b43-phy1 as /devices/virtual/input/input15 b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10) Registered led device: b43-phy1::tx Registered led device: b43-phy1::rx Registered led device: b43-phy1::radio ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticated wlan0: associate with AP 00:0e:2e:91:b1:7d wlan0: RX AssocResp from 00:0e:2e:91:b1:7d (capab=0x411 status=0 aid=1) wlan0: invalid aid value 1; bits 15:14 not set wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready martian source 255.255.255.255 from 192.168.0.254, on dev wlan0 ll header: ff:ff:ff:ff:ff:ff:00:0e:2e:91:b1:7d:08:00 martian source 255.255.255.255 from 192.168.0.254, on dev wlan0 ll header: ff:ff:ff:ff:ff:ff:00:0e:2e:91:b1:7d:08:00 wlan0: no IPv6 routers present b43-phy1 ERROR: PHY transmission error wlan0: No ProbeResp from current AP 00:0e:2e:91:b1:7d - assume out of range wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authentication with AP 00:0e:2e:91:b1:7d timed out wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticated wlan0: associate with AP 00:0e:2e:91:b1:7d wlan0: RX ReassocResp from 00:0e:2e:91:b1:7d (capab=0x411 status=0 aid=1) wlan0: invalid aid value 1; bits 15:14 not set wlan0: associated wlan0: No ProbeResp from current AP 00:0e:2e:91:b1:7d - assume out of range wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticate with AP 00:0e:2e:91:b1:7d wlan0: authenticated wlan0: associate with AP 00:0e:2e:91:b1:7d wlan0: associate with AP 00:0e:2e:91:b1:7d wlan0: associate with AP 00:0e:2e:91:b1:7d wlan0: association with AP 00:0e:2e:91:b1:7d timed out -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435767 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435767#c7 --- Comment #7 from Jiri Slaby 2008-11-22 09:12:38 MST --- (In reply to comment #5 from Luc Levain)

I can confirm that the bug still persists using openSUSE 11.1 Beta 5, running kernel 2.6.27.5-2-pae.

I'm not sure this is the same bug.

Googling for "ERROR: PHY transmission error" reveals quite a few bug reports in different distros, so quite possibly this is a bug in the kernel module.

Anyway I don't know what could cause this, you would better report this directly to the b43 people (with me in CC): http://linuxwireless.org/en/users/Drivers/b43#bugreporting Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435767 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435767#c8 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|fisiu82@gmail.com | Resolution| |NORESPONSE --- Comment #8 from Jiri Slaby 2009-01-02 04:47:46 MST --- Any updates on this issue? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.