On Tue, Aug 6, 2013 at 3:54 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2013-08-06 at 15:51 +0200, Sedat Dilek wrote: >> OK, I did not try with debugging enabled and/or w/o Network-Manager. >> >> If you know of an issue, please let me know. > > No, but the dmesg looks like security problems - check wpa_supplicant > log > I start a debug-session like this: # stop network-manager # kill -9 $(pidof wpa_supplicant) # /sbin/wpa_supplicant -B -P /run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant -t -ddd # start network-manager # tail -f /var/log/syslog # egrep 'warn|fail|error' /root/syslog_for-johill.txt Aug 6 16:29:00 fambox wpa_supplicant[1150]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Aug 6 16:29:07 fambox wpa_supplicant[1150]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Aug 6 16:29:13 fambox NetworkManager[1064]: <warn> quit request received, terminating... Aug 6 16:30:21 fambox NetworkManager[2541]: <warn> (wlan0): driver supports Access Point (AP) mode Aug 6 16:30:21 fambox NetworkManager[2541]: <warn> failed to allocate link cache: (-10) Operation not supported Aug 6 16:30:21 fambox NetworkManager[2541]: <warn> Trying to remove a non-existant call id. Aug 6 16:30:21 fambox wpa_supplicant[2533]: nl80211: Scan trigger failed: ret=-16 (Device or resource busy) Aug 6 16:30:27 fambox wpa_supplicant[2533]: EAPOL: External notification - EAP fail=0 Aug 6 16:30:34 fambox wpa_supplicant[2533]: EAPOL: External notification - EAP fail=0 Aug 6 16:30:42 fambox wpa_supplicant[2533]: EAPOL: External notification - EAP fail=0 Aug 6 16:30:48 fambox wpa_supplicant[2533]: EAPOL: External notification - EAP fail=0 Aug 6 16:31:04 fambox NetworkManager[2541]: <warn> quit request received, terminating... I send you the full syslog.txt to your sipsolutions email-address (not sure if it contains sensitive data). - Sedat - > johannes > -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
