I think we should make a very short list of what does/doesnt resolv and / or get us more close to the solution, (so 30 people with the same S/W-spec don't have to try out the same thing).
I have noticed that sometimes, when I'm very active on the computer (browsing the web) the WLAN seems to stay up. This after I disabled all the power-saving features - that is, System->Preferences->Power Management (Uncheck "Dim When Idle"). I am not saying that this is the solution - The WLAN still goes down - but it actually doesn't go down on the same short notice as it did before. It also seems that if there are many connections (e.g. rTorrent or similar), the NIC goes down. I also noticed something interresting a couple of days ago. I was browsing the web with FireFox and hit 'ping google.com' in bash. the nic suddenly started to go down to 0b/s(i measure traffic with netspeed). By this time, 'ping google.com' was dead quiet, unitil I quickly closed firefox. The wlan suddenly seemed to work again, since 'ping google.com' started to ping, and the netspee-applet suddenly started showing traffic flow again. This same thing did not only happen with Firefox, but also with RTorrent (I tried it later). My thought is: could this have something to do with some kind of virtual lockfile? I am (as I may have stated before) absolutely no ubuntu-expert, but I'd really like to help solving this problem, not only for my own sake, but for the ubuntu community. :-) On, and I am running the BCM STA-driver. Joakim On Thu, Apr 9, 2009 at 11:53 AM, Ben McCann <[email protected]> wrote: > > I tweaked /etc/apt/sources.list and added the intrepid package repository so > I could force a downgrade of the HAL packages. I downgraded hal, libhal1, and > libhal-storage from version 0.5.12-rc1+git20090403 to version 0.5.11-4ubuntu4 > (i.e. intrepid's version). I hoped to show that this bug was introduced in > the HAL subsystem. > > Unfortunately, downgrading these packages prevents X from starting. The > screen comes up but then the laptop freezes so I can't say whether the > wireless networking disconnects have improved. > > I reverted that change, apt-get updated and upgraded this morning > (4/9/09), and restored Jaunty to working order. Unfortunately, the > wireless disconnect problem is still (as you would expect) present. > Wireless goes down 5 or so minutes after rebooting. > > I'm trying here folks but I'm not sufficiently familiar with HAL to see > where to go next to demonstrate whether this is a HAL bug or some other > user space application. Andrew Aylett has already shown that reverting > back to the Intrepid kernel doesn't fix the problem. I verified weeks > ago that the B43 firmware hasn't changed. > > So, what can I do to help troubleshoot this bug? It's not going away by > itself. > > -- > [HP 2133 MiniNote laptop] Unexpected and unrecoverable wireless disconnect > with B43 driver > https://bugs.launchpad.net/bugs/331952 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” source package in Ubuntu: Triaged > > Bug description: > Wireless with the BCM4312 adapter connects, runs several minutes, and > disconnects unexpectedly with Ubuntu Jaunty (9.04) Alpha 4 on an HP 2133 > MiniNote laptop. The same laptop runs wireless flawlessly under Ubuntu > Intrepid (8.10). I only have wireless issues under Jaunty. Once it has > disconnected, I'm unable to reestablish a connection w/o rebooting. > > Note that the laptop is configured to dual boot between Intrepid and Jaunty > so its easy to run A/B experiments between the two releases. > > All this takes to reproduce is to boot Jaunty with the B43 driver, bring up > wireless, and then wait 5 or 10 minutes. I've hit this at home, with WEP > encryption, and at work on an open guest network so its not the AP. The > wireless works fine for several minutes, disconnects, and then won't reconnect > > I'm running the latest Jaunty (Xubuntu) packages as of this morning (2/20/09) > and the problem still occurs. I don't know if this is a network-manager issue > or a driver problem. Here are some chunks of data to start the triage > > Uname: > > Linux version 2.6.28-7-generic (bui...@palmer) (gcc version 4.3.3 (Ubuntu > 4.3.3-3ubuntu2) ) #20-Ubuntu SMP Mon Feb 9 15:43:21 UTC 2009 (Ubuntu > 2.6.28-7.20-generic) > > > lspci on the BCM4312: > > 02:00.0 0280: 14e4:4312 (rev 02) > Subsystem: 103c:1370 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- > <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 32 bytes > Interrupt: pin A routed to IRQ 24 > Region 0: Memory at fdffc000 (64-bit, non-prefetchable) [size=16K] > Capabilities: <access denied> > Kernel driver in use: b43-pci-bridge > Kernel modules: wl, ssb > > > kern.log: > > Feb 17 08:18:23 Polaris kernel: [ 2233.000045] b43-phy0: Radio hardware > status changed to DISABLED > Feb 17 08:18:27 Polaris kernel: [ 2237.756070] wlan0: No ProbeResp from > current AP 00:1f:90:e0:19:75 - assume out of range > Feb 17 08:18:27 Polaris kernel: [ 2237.904035] b43-phy0: Radio turned on by > software > Feb 17 08:18:27 Polaris kernel: [ 2237.904047] b43-phy0: The hardware RF-kill > button still turns the radio physically off. Press the button to turn it on. > Feb 17 08:18:28 Polaris kernel: [ 2238.677784] wlan0: direct probe to AP > 00:1f:90:e0:19:75 try 1 > Feb 17 08:18:28 Polaris kernel: [ 2238.677879] wlan0: direct probe to AP > 00:1f:90:e0:19:75 try 1 > Feb 17 08:18:28 Polaris kernel: [ 2238.876059] wlan0: direct probe to AP > 00:1f:90:e0:19:75 try 2 > Feb 17 08:18:28 Polaris kernel: [ 2239.076064] wlan0: direct probe to AP > 00:1f:90:e0:19:75 try 3 > Feb 17 08:18:29 Polaris kernel: [ 2239.276063] wlan0: direct probe to AP > 00:1f:90:e0:19:75 timed out > Feb 17 08:22:56 Polaris kernel: [ 2507.004202] b43-phy0 ERROR: DMA RX reset > timed out > Feb 17 08:22:57 Polaris kernel: [ 2507.164055] b43-phy0 ERROR: DMA TX reset > timed out > Feb 17 08:22:57 Polaris kernel: [ 2507.324077] b43-phy0 ERROR: DMA TX reset > timed out > Feb 17 08:22:57 Polaris kernel: [ 2507.484076] b43-phy0 ERROR: DMA TX reset > timed out > Feb 17 08:22:57 Polaris kernel: [ 2507.644225] b43-phy0 ERROR: DMA TX reset > timed out > Feb 17 08:22:57 Polaris kernel: [ 2507.804079] b43-phy0 ERROR: DMA TX reset > timed out > Feb 17 08:22:57 Polaris kernel: [ 2507.804776] ssb: Failed to switch to core 0 > Feb 17 08:23:08 Polaris kernel: [ 2518.277353] input: b43-phy0 as > /devices/virtual/input/input13 > Feb 17 08:23:08 Polaris kernel: [ 2518.328060] ssb: Backplane Revision > 0xF0000000 > Feb 17 08:23:08 Polaris kernel: [ 2518.328127] ------------[ cut here > ]------------ > Feb 17 08:23:08 Polaris kernel: [ 2518.328139] WARNING: at > /build/buildd/linux-2.6.28/drivers/ssb/main.c:1042 > ssb_tmslow_reject_bitmask+0x59/0x90 [ssb]() > Feb 17 08:23:08 Polaris kernel: [ 2518.328152] Modules linked in: usbhid > rfkill_input via drm bridge stp bnep e_powersaver ppdev parport_pc lp parport > joydev snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy > snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq psmouse > pcspkr snd_timer snd_seq_device serio_raw snd i2c_viapro soundcore > snd_page_alloc uvcvideo compat_ioctl32 videodev v4l1_compat arc4 ecb > leds_hp_disk video output b43 lis3lv02d mac80211 cfg80211 led_class > input_polldev shpchp via_agp agpgart tg3 ehci_hcd uhci_hcd ssb fbcon tileblit > font bitblit softcursor fuse > Feb 17 08:23:08 Polaris kernel: [ 2518.328314] Pid: 3227, comm: > NetworkManager Not tainted 2.6.28-7-generic #20-Ubuntu > Feb 17 08:23:08 Polaris kernel: [ 2518.328324] Call Trace: > Feb 17 08:23:08 Polaris kernel: [ 2518.328346] [<c04e2911>] ? > printk+0x18/0x1f > Feb 17 08:23:08 Polaris kernel: [ 2518.328363] [<c0133a64>] > warn_on_slowpath+0x54/0x80 > Feb 17 08:23:08 Polaris kernel: [ 2518.328399] [<f7cafef9>] > ssb_tmslow_reject_bitmask+0x59/0x90 [ssb] > Feb 17 08:23:08 Polaris kernel: [ 2518.328431] [<f7caff44>] > ssb_device_is_enabled+0x14/0x40 [ssb] > Feb 17 08:23:08 Polaris kernel: [ 2518.328475] [<f7ffd387>] > b43_wireless_core_init+0x37/0x520 [b43] > Feb 17 08:23:08 Polaris kernel: [ 2518.328520] [<f800e9a2>] ? > b43_rfkill_init+0x142/0x1d0 [b43] > Feb 17 08:23:08 Polaris kernel: [ 2518.328559] [<f7ffea17>] > b43_op_start+0x147/0x1a0 [b43] > Feb 17 08:23:08 Polaris kernel: [ 2518.328630] [<f7e3f10a>] > ieee80211_open+0x32a/0x830 [mac80211] > Feb 17 08:23:08 Polaris kernel: [ 2518.328651] [<c014c88a>] ? > hrtimer_try_to_cancel+0x3a/0x90 > Feb 17 08:23:08 Polaris kernel: [ 2518.328669] [<c04e3c99>] ? > schedule_hrtimeout_range+0xe9/0x150 > Feb 17 08:23:08 Polaris kernel: [ 2518.328687] [<c0417312>] > dev_open+0xa2/0xe0 > Feb 17 08:23:08 Polaris kernel: [ 2518.328702] [<c04e4d31>] ? > _spin_unlock_bh+0x11/0x20 > Feb 17 08:23:08 Polaris kernel: [ 2518.328716] [<c041674a>] ? > dev_set_rx_mode+0x2a/0x40 > Feb 17 08:23:08 Polaris kernel: [ 2518.328730] [<c04169c1>] > dev_change_flags+0x131/0x1c0 > Feb 17 08:23:08 Polaris kernel: [ 2518.328749] [<c041f80d>] > do_setlink+0x1ed/0x3a0 > Feb 17 08:23:08 Polaris kernel: [ 2518.328766] [<c0431103>] ? > nla_reserve+0x43/0x60 > Feb 17 08:23:08 Polaris kernel: [ 2518.328781] [<c041f10f>] ? > rtnl_fill_ifinfo+0x2cf/0x3b0 > Feb 17 08:23:08 Polaris kernel: [ 2518.328797] [<c041faa1>] > rtnl_setlink+0xe1/0x120 > Feb 17 08:23:08 Polaris kernel: [ 2518.328813] [<c0430270>] ? > netlink_dump_start+0x130/0x170 > Feb 17 08:23:08 Polaris kernel: [ 2518.328828] [<c041f9c0>] ? > rtnl_setlink+0x0/0x120 > Feb 17 08:23:08 Polaris kernel: [ 2518.328843] [<c041ebf5>] > rtnetlink_rcv_msg+0x165/0x200 > Feb 17 08:23:08 Polaris kernel: [ 2518.328858] [<c041f1f0>] ? > rtnl_dump_ifinfo+0x0/0xa0 > Feb 17 08:23:08 Polaris kernel: [ 2518.328874] [<c041ea90>] ? > rtnetlink_rcv_msg+0x0/0x200 > Feb 17 08:23:08 Polaris kernel: [ 2518.328888] [<c0430116>] > netlink_rcv_skb+0x76/0xa0 > Feb 17 08:23:08 Polaris kernel: [ 2518.328903] [<c041ea7c>] > rtnetlink_rcv+0x1c/0x30 > Feb 17 08:23:08 Polaris kernel: [ 2518.328916] [<c042f89d>] > netlink_unicast+0x25d/0x290 > Feb 17 08:23:08 Polaris kernel: [ 2518.328931] [<c043091b>] > netlink_sendmsg+0x1cb/0x2b0 > Feb 17 08:23:08 Polaris kernel: [ 2518.328946] [<c040921a>] > sock_sendmsg+0xea/0x110 > Feb 17 08:23:08 Polaris kernel: [ 2518.328964] [<c0298b40>] ? > apparmor_socket_recvmsg+0x10/0x20 > Feb 17 08:23:08 Polaris kernel: [ 2518.328981] [<c0148bf0>] ? > autoremove_wake_function+0x0/0x50 > Feb 17 08:23:08 Polaris kernel: [ 2518.328996] [<c0148bf0>] ? > autoremove_wake_function+0x0/0x50 > Feb 17 08:23:08 Polaris kernel: [ 2518.329013] [<c02bdb65>] ? > copy_from_user+0x35/0x130 > Feb 17 08:23:08 Polaris kernel: [ 2518.329031] [<c04106f0>] ? > verify_iovec+0x30/0xb0 > Feb 17 08:23:08 Polaris kernel: [ 2518.329044] [<c0409351>] > sys_sendmsg+0x111/0x230 > Feb 17 08:23:08 Polaris kernel: [ 2518.329057] [<c0409574>] ? > sys_sendto+0xb4/0xd0 > Feb 17 08:23:08 Polaris kernel: [ 2518.329070] [<c041518d>] ? > __dev_get_by_name+0x7d/0xa0 > Feb 17 08:23:08 Polaris kernel: [ 2518.329084] [<c02bdc96>] ? > copy_to_user+0x36/0x120 > Feb 17 08:23:08 Polaris kernel: [ 2518.329103] [<c0407410>] ? > sock_destroy_inode+0x10/0x20 > Feb 17 08:23:08 Polaris kernel: [ 2518.329122] [<c01c985a>] ? > destroy_inode+0x2a/0x50 > Feb 17 08:23:08 Polaris kernel: [ 2518.329137] [<c01ca192>] ? > generic_forget_inode+0x152/0x170 > Feb 17 08:23:08 Polaris kernel: [ 2518.329152] [<c0409b05>] > sys_socketcall+0xd5/0x2b0 > Feb 17 08:23:08 Polaris kernel: [ 2518.329173] [<c01b50a9>] ? > filp_close+0x49/0x70 > Feb 17 08:23:08 Polaris kernel: [ 2518.329188] [<c01b514a>] ? > sys_close+0x7a/0xc0 > Feb 17 08:23:08 Polaris kernel: [ 2518.329203] [<c0103f6b>] > sysenter_do_call+0x12/0x2f > Feb 17 08:23:08 Polaris kernel: [ 2518.329214] ---[ end trace > 81079ab9ec490f87 ]--- > Feb 17 08:23:09 Polaris kernel: [ 2519.508098] b43-phy0 ERROR: Microcode not > responding > Feb 17 08:23:09 Polaris kernel: [ 2519.508117] b43-phy0 ERROR: You must go to > http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the > latest firmware (version 4). > > I considered loading a different version of the B43 firmware as suggested but > the firmware stored under /lib/firmware/b43 is identical between Ubuntu > Intrepid and Jaunty. (I binary compared all the files and verified each uses > the same firmware version (broadcom-wl-4.150.10.5.tar.bz2). The > install_bcm43xx_firmware.sh scripts in Intrepid and Jaunty are also identical. > > So, I don't think this is a firmware issue despite the fact the driver wants > new firmware. This firmware is fine in Intrepid. I think something else in > the b43, wl, or ssb driver has regressed. Or, perhaps there's been a > regression in network-manager. > > > I'm happy to help any way necessary to find this bug. > > -Ben McCann > > == Regression details == > Discovered in version: Jaunty Alpha 4 > Last known good version: Intrepid 8.10 > -- [HP 2133 MiniNote laptop] Unexpected and unrecoverable wireless disconnect with B43 driver https://bugs.launchpad.net/bugs/331952 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
