Upstream thinks this is a Ubuntu problem. Once given the authentication request, the kernel goes right ahead and connects with no retries, they see no problem on their end. See below.
So the question is, why does Ubuntu take so long between these next two lines in dmesg? What is Ubuntu waiting for? [ 54.117720] EXT3-fs (sdb2): mounted filesystem with ordered data mode [ 185.982020] wlan0: authenticate with 00:0f:b3:b0:d6:3c In some cases, I've waited 5 minutes for the authentication request from Ubuntu, never came, so I did manual connect. Excerpt from syslog showing big gap between 14:01:51 and 14:02:29 approximate time as the gap in dmesg with similar messages. Syslog has two additional lines about not being able to open /etc/crypttab and mounting a udisk: Jul 9 14:01:51 Aspire1 kernel: [ 53.184095] EXT3-fs (sdb7): mounted filesystem with ordered data mode Jul 9 14:01:51 Aspire1 udisksd[1570]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or d irectory (g-file-error-quark, 4) Jul 9 14:01:51 Aspire1 udisksd[1570]: Mounted /dev/sdb7 at /run/media/jerry/LiveB7 on behalf of uid 1000 Jul 9 14:02:05 Aspire1 goa[1719]: goa-daemon version 3.5.3 starting [main.c:112, main()] Jul 9 14:02:29 Aspire1 NetworkManager[950]: <info> Auto-activating connection 'LAUREL'. Jul 9 14:02:29 Aspire1 NetworkManager[950]: <info> Activation (wlan0) starting connection 'LAUREL' Upstream's comment: --- Comment #10 from John W. Linville <linvi...@tuxdriver.com> 2012-07-09 17:37:49 --- I'm sorry, but I don't see any evidence of a kernel problem here. The kernel has no concept of an "automatic connection". Something in userland (probably NetworkManager in your case) has to tell the kernel what AP to use. In every case above, the authentication happens on the first try, followed immediately by the association on the first try. I don't see any significant delay being introduced by the kernel, and there are not even any retries. At worst, the kernel could be taking a while to scan -- but I don't see any evidence of an abnormally long scan either. Thanks for any ideas. Jerry ** Attachment added: "syslog showing failure to open /etc/crypttab" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1019083/+attachment/3217792/+files/syslog38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019083 Title: Quantal A2 failed to automatically connect Centrino Wireless N To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1019083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
