[hardy] [regression] iwl3945 doesn't associate on kernel 2.6.24-7

Bug #190968 reported by Vincenzo Ciancia
22
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-backports-modules-2.6.24 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

After upgrade from kernel 2.6.24-5 to 2.6.24-7, my wifi lan doesn't associate anymore. It always worked with ipw3945 in gutsy and iwl3945 in hardy.

#lspci -v
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
 Subsystem: Intel Corporation Unknown device 1041
 Flags: bus master, fast devsel, latency 0, IRQ 220
 Memory at ffaff000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [c8] Power Management version 2
 Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
 Capabilities: [e0] Express Legacy Endpoint IRQ 0

In the log I found:

[ 176.611892] wlan0_rename: AP denied association (code=18)
[ 176.634466] wlan0_rename: associate with AP 00:e0:98:4d:cd:52
[ 176.635312] wlan0_rename: invalid aid value 0; bits 15:14 not set
[ 176.635322] wlan0_rename: RX AssocResp from 00:e0:98:4d:cd:52 (capab=0x15 status=18 aid=0)

Tags: kj-expired
Revision history for this message
Pablo Martí (pmarti) wrote :

Same here! Downgrading to 2.6.24-5 while this is fixed

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Care to check which version of iwlwifi you have installed? 'sudo modinfo iwl3945' should tell you this information. The linux-ubuntu-modules package contains an updated version, 1.2.0. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Requested information follows. I can add that at office the association happens regularly. The problem manifests only with my home router (a d-link) which works with gutsy and worked with previous kernels.

vincenzo@frattaglia:~$ sudo modinfo iwl3945
[sudo] password for vincenzo:
filename: /lib/modules/2.6.24-7-generic/ubuntu/wireless/iwlwifi/iwlwifi/compatible/iwl3945.ko
license: GPL
author: Copyright(c) 2003-2007 Intel Corporation
version: 1.2.0
description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux
srcversion: 8E95C617988943846696F97
alias: pci:v00008086d00004227sv*sd*bc*sc*i*
alias: pci:v00008086d00004222sv*sd*bc*sc*i*
depends: iwlwifi_mac80211
vermagic: 2.6.24-7-generic SMP mod_unload 586
parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int)
parm: disable:manually disable the radio (default 0 [radio on]) (int)
parm: hwcrypto:using hardware crypto engine (default 0 [software])
 (int)
parm: debug:debug output mask (int)
parm: disable_hw_scan:disable hardware scanning (default 0) (int)
parm: queues_num:number of hw queues. (int)
parm: qos_enable:enable all QoS functionality (int)

Changed in linux:
status: Incomplete → New
Revision history for this message
Pablo Martí (pmarti) wrote :

This is my debug info, slightly different than Vincenzo's:

[ 102.792270] wlan0_rename: Initial auth_alg=0
[ 102.792282] wlan0_rename: authenticate with AP 00:02:72:43:aa:1b
[ 102.793707] wlan0_rename: RX authentication from 00:02:72:43:aa:1b (alg=0 transaction=2 status=0)
[ 102.793716] wlan0_rename: authenticated
[ 102.793721] wlan0_rename: associate with AP 00:02:72:43:aa:1b
[ 102.795897] wlan0_rename: RX AssocResp from 00:02:72:43:aa:1b (capab=0x11 status=12 aid=1)
[ 102.795905] wlan0_rename: AP denied association (code=12)
[ 102.989633] wlan0_rename: associate with AP 00:02:72:43:aa:1b
[ 102.991259] wlan0_rename: RX AssocResp from 00:02:72:43:aa:1b (capab=0x11 status=12 aid=1)
[ 102.991263] wlan0_rename: AP denied association (code=12)
[ 103.190542] wlan0_rename: associate with AP 00:02:72:43:aa:1b
[ 103.191980] wlan0_rename: RX AssocResp from 00:02:72:43:aa:1b (capab=0x11 status=12 aid=1)
[ 103.191984] wlan0_rename: AP denied association (code=12)
[ 103.390451] wlan0_rename: association with AP 00:02:72:43:aa:1b timed out
[ 115.639995] wlan0_rename: privacy configuration mismatch and mixed-cell disabled - disassociate

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Care to test 2.6.24-10 really quick and verify the issue still exists? Then per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux:
status: New → Incomplete
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Leann: I tested with 2.6.24-10 and the error was the same. Attaching requested information ASAP since I have booted the wrong kernel now and can't get the correct dmesg.

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Bug #176602 seems related.

Revision history for this message
David A Knight (david-ritter) wrote :

Same problem here for me with a belkin pre-n router, used to work fine prior to 2.6.24-7. Similar to vincenzo this seems to be router related as I have no problem connecting to my netgear router however. Both using WPA Personal

Revision history for this message
Id2ndR (id2ndr) wrote :

I can't connect to an open AP using iwl3945 in hardy (2.6.24-10), but it works with WPA protected AP. When trying to connect to an open network, it return error like :
RX deauthentication from 00:12:17:ae:73:fe (reason=7)
(look at https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/149214/comments/3 to see a similar behavior with iwl4965)

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
Jason Smith (jassmith) wrote :

I would like to chime in to say "me too". This error only occurs on 802.11b networks for me, g seems to work fine and I don't have an a network to test with.

Revision history for this message
skotti (jsk-priv) wrote :

Confirmed on Acer Aspire 5550 / Intel ICH7. Adding me to this bug.

Revision history for this message
dennis1200 (dennis-fiser) wrote :

Confirmed on Dell Inspiron 1525(n), currently at 2.6.24-12 on up-to-date Hardy Beta and iwl3945 version 1.2.0. Can't say anything about earlier 2.6.24 versions - my only other available kernel is 2.6.22-14. I followed instructions on https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy and on the Debian wiki: http://wiki.debian.org/iwlwifi. Hardy is a wonderful piece of work! Very much looking forward to the Final Release.

Similar dmesg output as Pablo's above:
[ 870.208557] wlan0: AP denied authentication (auth_alg=0 code=13)
[ 870.357469] wlan0: authenticate with AP 00:15:e9:69:1e:9e
[ 870.358753] wlan0: RX authentication from 00:15:e9:69:1e:9e (alg=0 transaction=2 status=13)
[ 870.358761] wlan0: AP denied authentication (auth_alg=0 code=13)
[ 870.435498] wlan0: authenticate with AP 00:15:e9:69:1e:9e
[ 870.437237] wlan0: RX authentication from 00:15:e9:69:1e:9e (alg=0 transaction=2 status=13)
[ 870.437246] wlan0: AP denied authentication (auth_alg=0 code=13)
[ 870.577527] wlan0: authentication with AP 00:15:e9:69:1e:9e timed out
[ 879.077384] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx
[ 880.789670] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 881.828715] sky2 eth0: disabling interface
[ 881.880284] sky2 eth0: enabling interface
[ 881.884603] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 882.847432] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx
[ 882.851970] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 890.509598] eth0: no IPv6 routers present

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

I tested today with fresh install of hardy beta (fully up-to-date) and fresh user account, bug is there and this means wifi is completely broken in new release.

Revision history for this message
Derek (bugs-m8y) wrote :
Download full text (8.8 KiB)

I'm assuming my problems are related. Going to try the kernel downgrade if I still have the sources...
Based on forum suggestion I attempted commenting out the udev rename of wlan0 to eth1 - didn't help.
Nor did noapic as was another suggestion.

# modinfo iwl3945
filename: /lib/modules/2.6.24-12-generic/ubuntu/wireless/iwlwifi/iwlwifi/compatible/iwl3945.ko
license: GPL
author: Copyright(c) 2003-2007 Intel Corporation
version: 1.2.0
description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux
srcversion: 8E95C617988943846696F97
alias: pci:v00008086d00004227sv*sd*bc*sc*i*
alias: pci:v00008086d00004222sv*sd*bc*sc*i*
depends: iwlwifi_mac80211
vermagic: 2.6.24-12-generic SMP mod_unload 586
parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int)
parm: disable:manually disable the radio (default 0 [radio on]) (int)
parm: hwcrypto:using hardware crypto engine (default 0 [software])
 (int)
parm: debug:debug output mask (int)
parm: disable_hw_scan:disable hardware scanning (default 0) (int)
parm: queues_num:number of hw queues. (int)
parm: qos_enable:enable all QoS functionality (int)

# ifup wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:18:de:1e:a4:12
Sending on LPF/wlan0/00:18:de:1e:a4:12
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Below is dmesg from the above ifup.

[ 408.723429] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 409.072122] wlan0: Initial auth_alg=0
[ 409.072131] wlan0: authenticate with AP 00:19:e4:08:d7:59
[ 409.073244] wlan0: RX authentication from 00:19:e4:08:d7:59 (alg=0 transaction=2 status=0)
[ 409.073251] wlan0: authenticated
[ 409.073254] wlan0: associate with AP 00:19:e4:08:d7:59
[ 409.074710] wlan0: RX ReassocResp from 00:19:e4:08:d7:59 (capab=0x431 status=0 aid=1)
[ 409.074717] wlan0: associated
[ 409.078316] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 410.681677] wlan0: no IPv6 routers present
[ 410.745110] wlan0: disassociate(reason=3)
[ 411.217442] wlan0: RX deauthentication from 00:19:e4:08:d7:59 (reason=6)
[ 411.217449] wlan0: deauthenticated
[ 411.217457] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 411.217463] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 411.217468] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 411.217474] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 411.217480] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 411....

Read more...

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Vincenzo,

An updated version of the iwlwifi drivers (version 1.2.25) was pulled into linux-backports-modules-2.6.24. Care to try installing and see if the updated version helps? Thanks.

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Leann: with linux-backport-modules-2.6.24 my card associates to the AP, thank you very much.

Revision history for this message
Derek (bugs-m8y) wrote :

linux-backports-modules-2.6.24-15-generic - updated a few hours ago.
still no improvement.
some more traffic below.

[ 4217.389554] wlan0: RX deauthentication from 00:19:e4:08:d7:59 (reason=6)
[ 4217.389561] wlan0: deauthenticated
[ 4217.389566] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389571] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389626] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389630] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389634] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389638] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389642] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389645] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389649] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389653] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389656] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389660] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389664] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389668] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389671] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.389675] wlan0: authenticate with AP 00:19:e4:08:d7:59
[ 4217.392400] wlan0: Initial auth_alg=0
[ 4217.392404] wlan0: authenticate with AP 00:19:e4:08:d7:59
[ 4217.392414] wlan0: RX disassociation from 00:19:e4:08:d7:59 (reason=7)
[ 4217.392419] wlan0: RX authentication from 00:19:e4:08:d7:59 (alg=0 transaction=2 status=0)
[ 4217.392422] wlan0: authenticated
[ 4217.392426] wlan0: associate with AP 00:19:e4:08:d7:59
[ 4217.393566] wlan0: Initial auth_alg=0
[ 4217.393570] wlan0: authenticate with AP 00:19:e4:08:d7:59
[ 4217.399337] wlan0: RX authentication from 00:19:e4:08:d7:59 (alg=0 transaction=2 status=0)
[ 4217.399341] wlan0: authenticated
[ 4217.399343] wlan0: associate with AP 00:19:e4:08:d7:59
[ 4217.401904] wlan0: RX ReassocResp from 00:19:e4:08:d7:59 (capab=0x431 status=0 aid=1)
[ 4217.401909] wlan0: associated

Revision history for this message
Derek (bugs-m8y) wrote :

Wifi works fine in windows BTW (worked fine previously with ipw3945 too)

Tried restarting wireless network just in case that would have an impact - didn't.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Derek,

Care to open a new report as it seems you are experiencing a different bug than the original bug reporter. Vincenzo has commented that this issue was resolved with the updated iwlwifi available in linux-backports-modules-2.6.24. It is helpful to the development teams if bug reports target one specific issue otherwise it is difficult to sift through comments which do and don't apply to a bug. If would be great in your new bug report if you could include the debugging information outlined here: https://wiki.ubuntu.com/KernelTeamBugPolicies . I apologize for any inconvenience this may cause, but we appreciate your cooperation. Thanks.

Changed in linux-ubuntu-modules-2.6.24:
status: Triaged → Fix Released
Revision history for this message
Bart Heinsius (bheinsius) wrote :

linux-backports-modules-2.6.24-15-generic solved it for me.

Revision history for this message
Bart Heinsius (bheinsius) wrote :

sorry, that was linux-backports-modules-2.6.24-16-generic

Revision history for this message
Cláudio Silva (gphoenixpower) wrote :

I'm using the latest kernel with the latest linux-backports-modules and still can't connect to a wireless network that uses autentication.

Revision history for this message
Pipers (uriona) wrote :

Same problem here but for my wifi interface,

Just upgraded from Gutsy, and found a bug, it couldn't associate to a wpa secured network.
Trying to resolve it I removed network-manager from the system (didn't know it was a known bug) because I could associate and after some seconds the wifi automagically dissasociated... Thought there was a process changing my terminal settings
Then I found it was a known bug -> 190968 and reinstalled network-manager. Now my error message in network manager is:
"The interface does not exist Check that it is correctly typed and that it is correctly supported by your system.", another known bug -> 184711

#lspci -v
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
 Subsystem: Intel Corporation Unknown device 1001
 Flags: bus master, fast devsel, latency 0, IRQ 218
 Memory at fe0ff000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: <access denied>
#uname -a
Linux juriona 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
# lsmod |grep iw
iwl3945 89844 0
iwlwifi_mac80211 219108 1 iwl3945
cfg80211 15112 1 iwlwifi_mac80211

Revision history for this message
Bart Heinsius (bheinsius) wrote :

A new kernel (2.6.24-17) was available in the Proposed section, I upgraded to it and networking wireless isn't working anymore, like before. dpkg tells me I'm still running the 2.6.24-16 version of linux-backports-modules while apt tells me that 2.6.24-17 is available. Why isn't it telling me that?
Anyway, I will upgrade linux-backports-modules and see if it gives me my wireless networking back.

Revision history for this message
Bart Heinsius (bheinsius) wrote :

ok, linux-backports-modules-2.6.24-17 got my networking back but destroyed my restricted drivers settings.
hmm. I'll see if I can get support on the forums.

Revision history for this message
Bart Heinsius (bheinsius) wrote :

booted into 2.6.24-16, uninstalled linux-backports-modules-2.6.24-17.
booted into 2.6.24-17, no restricted drivers so 800x600 resolution.
installed linux-backports-modules-2.6.24-17.
rebooted and all was fixed (?).

Revision history for this message
Id2ndR (id2ndr) wrote :

I was wrong when I said that it doesn't work with new iwl3945 previously (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/190968/comments/13). In fact that was the AP that doesn't allow me to associate with it (mac address filtering) and this may be the explanation of "reason=7" error.

Revision history for this message
Bassjunkie (mark-skrzypczyk) wrote :

I also think I'm having this problem. I'm currently running a fully updated Hardy with 2.6.24-16 kernel. I can connect the the wireless network at my house (D-Link router, 802.11g with WPA-TKIP) but cannot connect at my parents house (D-Link, 802.11b, WEP 64bit HEX). I never had any problems before the update to Hardy. My other laptop can connect to this network fine, but uses a different wireless card. As it appears to be a problem with the encryption I'm tempted to upgrade the encryption used to at least WPA and then just change the settings on the other laptop that uses wireless :-)

If that doesn't work I'll try using the updated module from backports but I don't like enabling that one normally!

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

I don't know anymore where I found this information on the web, but it seems to me that in intrepid, if I use qos_enable=0 as a module argument for iwl3945, everything works just fine.

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Sorry, wrong bug!

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Why is this bug fix-released? In hardy fully up-to-date, even if the backports repository is enabled, it requires manual intervention to make the wireless work. It works in the livecd and is broken by the first upgrade, so why is it considered fixed at all?

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Ok, I have 12 years of linux experience, a Ph.D. in computer science, and still my only hope now is to reinstall from scratch. I followed your instructions and installed linux-backport-modules-hardy but now I don't have snd_hda_intel support anymore (the module does not exist). Can someone explain here how do you solve this problem so that other persons passing by will solve it too?

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

I just had installed linux-backports-modules-hardy-386 by mistake, this pulled down the corresponding -386 kernel where there is no snd-hda-intel support (wonder why but don't really want to know). However the bug remains in the mainline kernel, that iwl3945 is unsupported and this is a regression from gutsy. This bug should perhaps be reassigned to the main kernel.

Revision history for this message
TomekPaczkowski (oinopion) wrote :

I too confirm this bug. I'm using 2.6.24-19, have Intel 3945ABG wireless and linksys WRT54G. It works on some other router of this type.

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

If nobody objects, Tomek could you confirm the bug in linux-ubuntu-modules-2.6.24?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Can anyone confirm if this is still an issue with the more recent Intrepid Ibex 8.10 release that was released last month - http://www.ubuntu.com/getubuntu/download . You should be able to test using a LiveCD. For now I'm going to move this to be against the actively developed "linux" kernel package. Thanks.

Changed in linux-ubuntu-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Bart Heinsius (bheinsius) wrote :

I can confirm that there still is _an_ issue with iwl3945, I'd have to confirm if its _this_ issue. Upgrade from hardy to intrepid broke my wireless networking again. hmm

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.