On Tue, 2011-03-08 at 17:54 +0000, Mathias BurÃn wrote: > On 8 March 2011 17:18, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > > On Tue, 2011-03-08 at 17:13 +0000, Mathias BurÃn wrote: > > > >> 1299604089.756872: WPS: UUID based on MAC address - hexdump(len=16): > >> cc fa a1 31 39 a7 5c 33 96 d8 eb 09 dd fe 7f 0f > >> 1299604089.768927: ssid - hexdump_ascii(len=11): > >> 55 62 75 6e 74 75 41 64 68 6f 63 UbuntuAdhoc > >> 1299604094.005785: ssid - hexdump_ascii(len=11): > >> 55 62 75 6e 74 75 41 64 68 6f 63 UbuntuAdhoc > >> > >> Anything else I can try/provide? > > > > Could you do the -dddt thing as explained on the link I had before? > > > > Obviously, we're now looking for the cause -- while the warning still > > shouldn't happen *even if userspace is misbehaving*. The trace will > > hopefully help me figure out why we get the warning, I'll look at it > > later. > > > > johannes > > > > > > I think the wpa_supplicant log file is generated correctly now, see: > http://www.2shared.com/file/QTkhZ1VC/wpa_supplicant.html Could you also grab /var/log/daemon.log or /var/log/NetworkManager.log, whichever one exists? And just to make sure, when this problem happens, there is only one wpa_supplicant running at the time, right? Is something like wicd also running? The logs there look like something external is telling the supplicant to disassociate, which could be NM or some other tool, but NM should not be exhibiting this behavior if NM itself was used to start the adhoc network. Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
