[Bug 625265] Re: rtl8187: spontaneously disassociates

2010-12-21 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/625265

Title:
  rtl8187: spontaneously disassociates

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 625265] Re: rtl8187: spontaneously disassociates

2010-09-19 Thread Vince McIntyre
I omitted to remove the needs-upstream-testing tag, I'm not that
familiar with all the LP functions.

I noted in the bug I that tested with linux-image-2.6.35-020635rc1-generic.
That has the same problems.

I tested again, with 
linux-image-2.6.32-0206322109-generic_2.6.32-0206322109.201008271507_i386.deb
from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.21.9-lucid/
$ uname -a
Linux ubuntu 2.6.32-0206322109-generic #201008271507 SMP Fri Aug 27 16:10:51 
UTC 2010 i686 GNU/Linux

I tried this for a couple of days. The interface falls over after a few
minutes to a few hours.

Here's what dmesg says about the insertion (hot-plug) of the device
with that kernel:

[ 1212.644016] usb 1-2: new high speed USB device using ehci_hcd and address 4
[ 1212.783305] usb 1-2: configuration #1 chosen from 1 choice
[ 1213.131068] phy1: Selected rate control algorithm 'minstrel'
[ 1213.132204] phy1: hwaddr 00:1e:2a:d0:49:db, RTL8187BvE V0 + rtl8225z2, 
rfkill mask 2
[ 1213.153627] rtl8187: Customer ID is 0x00
[ 1213.155570] Registered led device: rtl8187-phy1::tx
[ 1213.156396] Registered led device: rtl8187-phy1::rx
[ 1213.157119] rtl8187: wireless switch is on
[ 1213.157397] usbcore: registered new interface driver rtl8187
[ 1213.197568] udev: renamed network interface wlan0 to wlan1
[ 1217.014780] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 1219.117222] wlan1: direct probe to AP 00:04:ed:b9:1c:d7 (try 1)
[ 1219.120218] wlan1: direct probe responded
[ 1219.120222] wlan1: authenticate with AP 00:04:ed:b9:1c:d7 (try 1)
[ 1219.121967] wlan1: authenticated
[ 1219.121984] wlan1: associate with AP 00:04:ed:b9:1c:d7 (try 1)
[ 1219.124965] wlan1: RX AssocResp from 00:04:ed:b9:1c:d7 (capab=0x431 status=0 
aid=4)
[ 1219.124968] wlan1: associated
[ 1219.130471] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready

And then I get only these items in dmesg:
[ 1986.324027] [drm] nouveau :01:00.0: Setting dpms mode 1 on vga encoder 
(output 1)
[ 7582.500014] No probe response from AP 00:04:ed:b9:1c:d7 after 500ms, 
disconnecting.

After bringing the interface up (again static IP config, WEP encryption)
iwconfig reports this
ubuntu$ sudo iwconfig wlan1
wlan1 IEEE 802.11bg  ESSID:My Net's home
  Mode:Managed  Frequency:2.412 GHz  Access Point: 00:04:ED:B9:1C:D7
  Bit Rate=1 Mb/s   Tx-Power=20 dBm
  Retry  long limit:7   RTS thr:off   Fragment thr:off
  Encryption key:F43E-D0B4-6B
  Power Management:off
  Link Quality=64/70  Signal level=-46 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0


While waiting for a response to the initial report I added a pci-based wireless
card to the system, which reports about -80 dBm vs -50 dBm from the netgear.
Not clear why the difference is so large, they are less than a metre apart,
(not too close, in case of interference).
The pci card antenna is connected fine, the system case is not metal (Dell).

I shut down this interface and started another test with just the netgear.
It failed in exactly the same way as before.

here's dmesg for when the interface comes up:
[90153.178570] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[90155.261318] wlan1: direct probe to AP 00:04:ed:b9:1c:d7 (try 1)
[90155.263699] wlan1: direct probe responded
[90155.263703] wlan1: authenticate with AP 00:04:ed:b9:1c:d7 (try 1)
[90155.267184] wlan1: authenticated
[90155.267201] wlan1: associate with AP 00:04:ed:b9:1c:d7 (try 1)
[90155.269187] wlan1: RX AssocResp from 00:04:ed:b9:1c:d7 (capab=0x431 status=0 
aid=4)
[90155.269191] wlan1: associated
[90155.274688] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready

later I find the interface in this state:
wlan1 IEEE 802.11bg  ESSID:off/any  
  Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
  Retry  long limit:7   RTS thr:off   Fragment thr:off
  Encryption key:F43E-D0B4-6B
  Power Management:off

and this in dmesg:
[90767.052019] [drm] nouveau :01:00.0: Setting dpms mode 1 on vga encoder 
(output 1)
[91104.500017] No probe response from AP 00:04:ed:b9:1c:d7 after 500ms, 
disconnecting.


Reporting on this is being complicated by something strange happening
with logging using this kernel.
dmesg is updating, but I am not getting kernel messages in the other logs.
Every time I restart rsyslogd I get in /var/log/kern.log:
  Sep 17 21:17:11 ubuntu kernel: imklog: Cannot read proc file system, 1.

I see syslog messages for cron jobs etc but not kernel-related things.
Not sure if there is anything I can do about this, please advise.


** Tags removed: needs-upstream-testing

-- 
rtl8187: spontaneously disassociates
https://bugs.launchpad.net/bugs/625265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 625265] Re: rtl8187: spontaneously disassociates

2010-09-16 Thread Jeremy Foshee
Hi Vince,

If you could also please test the latest upstream kernel available that would 
be great.  It will allow additional upstream developers to examine the issue.  
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .  Once you've tested the 
upstream kernel, please remove the 'needs-upstream-testing' tag.  This can be 
done by clicking on the yellow pencil icon next to the tag located at the 
bottom of the bug description and deleting the 'needs-upstream-testing' text.  
Please let us know your results.

Thanks in advance.

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


** Tags added: kj-triage

** Changed in: linux (Ubuntu)
   Status: New = Incomplete

-- 
rtl8187: spontaneously disassociates
https://bugs.launchpad.net/bugs/625265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 625265] Re: rtl8187: spontaneously disassociates

2010-09-02 Thread Vince McIntyre
Went back to 2.6.32-22-generic, since that fixed other issues
(LP:459732).

I installed linux-image-2.6.32-22-generic (version 2.6.32-22.36) and 
linux-backports-modules-wireless-2.6.32-33-generic (version 2.6.32-22.13) and 
rebooted, then selected
this kernel from the grub list.

The same failure occurs, with the same error message.
However I don't see the message about the bogus regulatory domain on this 
kernel.
So something has changed there. I haven't messed about with 'wireless-crda', the
version installed is 1.12, installed 2010-04-16.


Here's the timeline of associations and disassociations with
2.6.32-22-generic:

system boot
Aug 31 22:43:03 ubuntu kernel: [   25.199388] wlan1: associated

cron job restarts interface
Sep  1 00:55:01 ubuntu kernel: [ 7943.304273] wlan1: deauthenticating from 
00:04:ed:00:00:00 by local choice (reason=3)
...
Sep  1 00:55:20 ubuntu kernel: [ 7962.289140] wlan1: associated

failure
Sep  1 12:10:37 ubuntu kernel: [48479.500014] No probe response from AP 
00:04:ed:00:00:00 after 500ms, disconnecting.

cron job
Sep  2 00:55:19 ubuntu kernel: [94361.630495] ADDRCONF(NETDEV_UP): wlan1: link 
is not ready
...
Sep  2 00:55:19 ubuntu kernel: [94361.704978] wlan1: associated
Sep  2 00:55:20 ubuntu kernel: [94361.710490] ADDRCONF(NETDEV_CHANGE): wlan1: 
link becomes ready

failure
Sep  2 06:44:59 ubuntu kernel: [115343.500012] No probe response from AP 
00:04:ed:00:00:00 after 500ms, disconnecting.


As I was poking at this, I got  a faster failure, within a few minutes.

Here's the link being established:
Sep  2 21:57:21 ubuntu kernel: [170085.954566] ADDRCONF(NETDEV_UP): wlan1: link 
is not ready
Sep  2 21:57:21 ubuntu kernel: [170086.021295] wlan1: direct probe to AP 
00:04:ed:00:00:00 (try 1)
Sep  2 21:57:21 ubuntu kernel: [170086.023801] wlan1: direct probe responded
Sep  2 21:57:21 ubuntu kernel: [170086.023805] wlan1: authenticate with AP 
00:04:ed:00:00:00 (try 1)
Sep  2 21:57:21 ubuntu kernel: [170086.026038] wlan1: authenticated
Sep  2 21:57:21 ubuntu kernel: [170086.026061] wlan1: associate with AP 
00:04:ed:00:00:00 (try 1)
Sep  2 21:57:21 ubuntu kernel: [170086.028671] wlan1: RX AssocResp from 
00:04:ed:00:00:00 (capab=0x431 status=0 aid=4)
Sep  2 21:57:21 ubuntu kernel: [170086.028674] wlan1: associated
Sep  2 21:57:21 ubuntu kernel: [170086.034310] ADDRCONF(NETDEV_CHANGE): wlan1: 
link becomes ready

and failing
Sep  2 22:00:37 ubuntu kernel: [170284.500014] No probe response from AP 
00:04:ed:00:00:00 after 500ms, disconnecting.


With regard to the regulatory domain, for 2.6.32-22-generic
I see this in 'grep cfg80211 /var/log/kern.log':
 Aug 31 22:43:01 ubuntu kernel: [   16.169152] cfg80211: Calling CRDA to update 
world regulatory domain
 Aug 31 22:43:01 ubuntu kernel: [   16.673469] cfg80211: World regulatory 
domain updated:

then nothing further for three days.

With later kernels, I see a lot more chatter. 
Here's the output of  'grep cfg80211 /var/log/kern.log' for 2.6.32-24-generic, 
annotated.

cron job
Aug 30 00:55:01 ubuntu kernel: [186302.842327] cfg80211: All devices are 
disconnected, going to restore regulatory settings
Aug 30 00:55:01 ubuntu kernel: [186302.842333] cfg80211: Restoring regulatory 
settings
Aug 30 00:55:01 ubuntu kernel: [186302.842336] cfg80211: Calling CRDA to update 
world regulatory domain
Aug 30 00:55:01 ubuntu kernel: [186302.846620] cfg80211: World regulatory 
domain updated:
Aug 30 00:55:20 ubuntu kernel: [186321.879945] cfg80211: Ignoring bogus country 
IE

failure
Aug 30 08:43:33 ubuntu kernel: [214414.573252] cfg80211: All devices are 
disconnected, going to restore regulatory settings
Aug 30 08:43:33 ubuntu kernel: [214414.573258] cfg80211: Restoring regulatory 
settings
Aug 30 08:43:33 ubuntu kernel: [214414.573261] cfg80211: Calling CRDA to update 
world regulatory domain
Aug 30 08:43:33 ubuntu kernel: [214414.576633] cfg80211: World regulatory 
domain updated:

cron job
Aug 31 00:55:20 ubuntu kernel: [272721.460713] cfg80211: Ignoring bogus country 
IE
(nothing futher, which is odd)

manual ifdown
Aug 31 22:25:52 ubuntu kernel: [350144.398418] cfg80211: All devices are 
disconnected, going to restore regulatory settings
Aug 31 22:25:52 ubuntu kernel: [350144.398424] cfg80211: Restoring regulatory 
settings
Aug 31 22:25:52 ubuntu kernel: [350144.398427] cfg80211: Calling CRDA to update 
world regulatory domain
Aug 31 22:25:52 ubuntu kernel: [350144.402698] cfg80211: World regulatory 
domain updated:

manual ifup
Aug 31 22:26:01 ubuntu kernel: [350153.140755] cfg80211: Ignoring bogus country 
IE

-- 
rtl8187: spontaneously disassociates
https://bugs.launchpad.net/bugs/625265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 625265] Re: rtl8187: spontaneously disassociates

2010-08-27 Thread Vince McIntyre

** Attachment added: AlsaDevices.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522758/+files/AlsaDevices.txt

** Attachment added: AplayDevices.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522759/+files/AplayDevices.txt

** Attachment added: ArecordDevices.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522760/+files/ArecordDevices.txt

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522761/+files/BootDmesg.txt

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/625265/+attachment/1522762/+files/CRDA.txt

** Attachment added: Card0.Amixer.values.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522763/+files/Card0.Amixer.values.txt

** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522764/+files/Card0.Codecs.codec97.0.ac97.0.0.txt

** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522765/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522766/+files/CurrentDmesg.txt

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522767/+files/Dependencies.txt

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522768/+files/IwConfig.txt

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/625265/+attachment/1522769/+files/Lspci.txt

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/625265/+attachment/1522770/+files/Lsusb.txt

** Attachment added: PciMultimedia.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522771/+files/PciMultimedia.txt

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522772/+files/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522773/+files/ProcInterrupts.txt

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522774/+files/ProcModules.txt

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/625265/+attachment/1522775/+files/UdevDb.txt

** Attachment added: UdevLog.txt
   https://bugs.launchpad.net/bugs/625265/+attachment/1522776/+files/UdevLog.txt

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/625265/+attachment/1522777/+files/WifiSyslog.txt

-- 
rtl8187: spontaneously disassociates
https://bugs.launchpad.net/bugs/625265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs