From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 9 07:50:00 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 66A39CD9 for ; Sat, 9 Nov 2013 07:50:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1BF602F8F for ; Sat, 9 Nov 2013 07:50:00 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id i8so1603311qcq.2 for ; Fri, 08 Nov 2013 23:49:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ilAz2fOaUIwoI2DOCMqPT8aSPkrDTr8pz5ca9/LepOo=; b=eUhhjZs6B/T/FauJsTsOSYlle26bRH8UPK+leiykePoYnxftH9BWi8AQfX7qG8AmVS vgiCKWhApwDRL+5p2PVmnL/Okg0SLy1F8fOjIlseDxgNRcyNOJr5xm+5qRgU2aGt6I99 d0qJDowVHhXWs77aTltanlIdAGw4f9hEGD5cKSDgPnhhsI1lixTkl77vUaXL2I3q8O0G BTpyPpw51IwH/gcNL/Gw2uU2SZImN0T8tjcljHtNPDgPPHR+5dvvXHuIgb7yz5gAhJTD rx8W23dswbkYX8BQt84uEIdWdDsrOtYUAj4w/QuviHfTqdY0ikmHbVSajRKQtL7b8j2D MuIg== MIME-Version: 1.0 X-Received: by 10.49.19.101 with SMTP id d5mr28731806qee.78.1383983399360; Fri, 08 Nov 2013 23:49:59 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Fri, 8 Nov 2013 23:49:59 -0800 (PST) In-Reply-To: References: Date: Fri, 8 Nov 2013 23:49:59 -0800 X-Google-Sender-Auth: 3G4y9Q3FuAnMUHIAcP76NpxxYWA Message-ID: Subject: Re: AR9160 on HEAD - unstable? From: Adrian Chadd To: Sven Hazejager Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Nov 2013 07:50:00 -0000 Hi, the stuck beacon stuff is likely just the MAC getting angry at the power save aggressiveness that the iphone/ipad does. But it itself shouldn't lock things up. When you say you did a warm reboot, is that a 'reboot' where you typed reboot? is there a physical reset button on the ALIX you can short? -adrian On 8 November 2013 23:13, Sven Hazejager wrote: > Well, my original hypothesis was wrong: HEAD r250200 (around 3 May 2013) > fully lost its wifi on me this morning. My iPhone was on during the night, > which generated a long list of "stuck beacon" messages. The iPhone could not > get a connection and neither could any other stations. A warm reboot did not > help! I had to physically power down the ALIX box. > > So I guess I won't be testing on r250200 anymore, as my previous problems > were all resolvable by resetting the station, not the AP. Below is the > complete /var/log/messages. Any suggestions? > > Nov 7 21:54:23 algol newsyslog[1056]: logfile first created > Nov 7 21:54:23 algol syslogd: kernel boot file is /boot/kernel/kernel > Nov 7 21:54:23 algol kernel: Copyright (c) 1992-2013 The FreeBSD Project. > Nov 7 21:54:23 algol kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, > 1989, 1991, 1992, 1993, 1994 > Nov 7 21:54:23 algol kernel: The Regents of the University of California. > All rights reserved. > Nov 7 21:54:23 algol kernel: FreeBSD is a registered trademark of The > FreeBSD Foundation. > Nov 7 21:54:23 algol kernel: FreeBSD 10.0-CURRENT #0: Thu Nov 7 15:30:54 > CET 2013 > Nov 7 21:54:23 algol kernel: > root@vmbsd10:/usr/obj/nanobsd.alix/usr/src/sys/ALIX i386 > Nov 7 21:54:23 algol kernel: FreeBSD clang version 3.3 (trunk 178860) > 20130405 > Nov 7 21:54:23 algol kernel: CPU: Geode(TM) Integrated Processor by AMD PCS > (498.06-MHz 586-class CPU) > Nov 7 21:54:23 algol kernel: Origin = "AuthenticAMD" Id = 0x5a2 Family = > 0x5 Model = 0xa Stepping = 2 > Nov 7 21:54:23 algol kernel: > Features=0x88a93d > Nov 7 21:54:23 algol kernel: AMD Features=0xc0400000 > Nov 7 21:54:23 algol kernel: real memory = 268435456 (256 MB) > Nov 7 21:54:23 algol kernel: avail memory = 250781696 (239 MB) > Nov 7 21:54:23 algol kernel: pnpbios: Bad PnP BIOS data checksum > Nov 7 21:54:23 algol kernel: K6-family MTRR support enabled (2 registers) > Nov 7 21:54:23 algol kernel: cryptosoft0: on motherboard > Nov 7 21:54:23 algol kernel: pcib0 pcibus 0 on motherboard > Nov 7 21:54:23 algol kernel: pci0: on pcib0 > Nov 7 21:54:23 algol kernel: Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS > V1.4a (C)1997-2007 > Nov 7 21:54:23 algol kernel: glxsb0: (AES-128-CBC, RNG)> mem 0xefff4000-0xefff7fff irq 9 at device 1.2 on pci0 > Nov 7 21:54:23 algol kernel: vr0: port > 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0 > Nov 7 21:54:23 algol kernel: vr0: Quirks: 0x2 > Nov 7 21:54:23 algol kernel: vr0: Revision: 0x96 > Nov 7 21:54:23 algol kernel: miibus0: on vr0 > Nov 7 21:54:23 algol kernel: ukphy0: > PHY 1 on miibus0 > Nov 7 21:54:23 algol kernel: ukphy0: none, 10baseT, 10baseT-FDX, > 100baseTX, 100baseTX-FDX, auto, auto-flow > Nov 7 21:54:23 algol kernel: vr0: Ethernet address: 00:0d:b9:19:aa:94 > Nov 7 21:54:23 algol kernel: vr1: port > 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 15 at device 11.0 on pci0 > Nov 7 21:54:23 algol kernel: vr1: Quirks: 0x2 > Nov 7 21:54:23 algol kernel: vr1: Revision: 0x96 > Nov 7 21:54:23 algol kernel: miibus1: on vr1 > Nov 7 21:54:23 algol kernel: ukphy1: > PHY 1 on miibus1 > Nov 7 21:54:23 algol kernel: ukphy1: none, 10baseT, 10baseT-FDX, > 100baseTX, 100baseTX-FDX, auto, auto-flow > Nov 7 21:54:23 algol kernel: vr1: Ethernet address: 00:0d:b9:19:aa:95 > Nov 7 21:54:23 algol kernel: ath0: mem 0xe0080000-0xe008ffff > irq 9 at device 12.0 on pci0 > Nov 7 21:54:23 algol kernel: ath0: [HT] enabling HT modes > Nov 7 21:54:23 algol kernel: ath0: [HT] 2 RX streams; 2 TX streams > Nov 7 21:54:23 algol kernel: ath0: AR9160 mac 64.1 RF5133 phy 11.0 > Nov 7 21:54:23 algol kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > Nov 7 21:54:23 algol kernel: isab0: port > 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at > device 15.0 on pci0 > Nov 7 21:54:23 algol kernel: isa0: on isab0 > Nov 7 21:54:23 algol kernel: atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0 > Nov 7 21:54:23 algol kernel: ata0: at channel 0 on atapci0 > Nov 7 21:54:23 algol kernel: ata1: at channel 1 on atapci0 > Nov 7 21:54:23 algol kernel: ohci0: mem > 0xefffe000-0xefffefff irq 12 at device 15.4 on pci0 > Nov 7 21:54:23 algol kernel: usbus0 on ohci0 > Nov 7 21:54:23 algol kernel: ehci0: > mem 0xefffd000-0xefffdfff irq 12 at device 15.5 on pci0 > Nov 7 21:54:23 algol kernel: usbus1: EHCI version 1.0 > Nov 7 21:54:23 algol kernel: usbus1 on ehci0 > Nov 7 21:54:23 algol kernel: cpu0 on motherboard > Nov 7 21:54:23 algol kernel: orm0: at iomem > 0xe0000-0xea7ff pnpid ORM0000 on isa0 > Nov 7 21:54:23 algol kernel: atrtc0: at port 0x70 irq 8 > on isa0 > Nov 7 21:54:23 algol kernel: Event timer "RTC" frequency 32768 Hz quality 0 > Nov 7 21:54:23 algol kernel: attimer0: at port 0x40 on isa0 > Nov 7 21:54:23 algol kernel: Timecounter "i8254" frequency 1193182 Hz > quality 0 > Nov 7 21:54:23 algol kernel: Event timer "i8254" frequency 1193182 Hz > quality 100 > Nov 7 21:54:23 algol kernel: uart0: <16550 or compatible> at port > 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > Nov 7 21:54:23 algol kernel: uart0: console (57600,n,8,1) > Nov 7 21:54:23 algol kernel: uart1: <16550 or compatible> at port > 0x2f8-0x2ff irq 3 on isa0 > Nov 7 21:54:23 algol kernel: Timecounters tick every 1.000 msec > Nov 7 21:54:23 algol kernel: usbus0: 12Mbps Full Speed USB v1.0 > Nov 7 21:54:23 algol kernel: usbus1: 480Mbps High Speed USB v2.0 > Nov 7 21:54:23 algol kernel: ugen0.1: at usbus0 > Nov 7 21:54:23 algol kernel: uhub0: 1.00/1.00, addr 1> on usbus0 > Nov 7 21:54:23 algol kernel: ugen1.1: at usbus1 > Nov 7 21:54:23 algol kernel: uhub1: 2.00/1.00, addr 1> on usbus1 > Nov 7 21:54:23 algol kernel: ada0 at ata0 bus 0 scbus0 target 0 lun 0 > Nov 7 21:54:23 algol kernel: ada0: ATA-0 device > Nov 7 21:54:23 algol kernel: ada0: 100.000MB/s transfers (UDMA5, PIO > 512bytes) > Nov 7 21:54:23 algol kernel: ada0: 3831MB (7847280 512 byte sectors: 16H > 63S/T 7785C) > Nov 7 21:54:23 algol kernel: ada0: Previously was known as ad0 > Nov 7 21:54:23 algol kernel: Timecounter "TSC" frequency 498060911 Hz > quality 800 > Nov 7 21:54:23 algol kernel: Root mount waiting for: usbus1 usbus0 > Nov 7 21:54:23 algol kernel: uhub0: 4 ports with 4 removable, self powered > Nov 7 21:54:23 algol kernel: Root mount waiting for: usbus1 > Nov 7 21:54:23 algol kernel: uhub1: 4 ports with 4 removable, self powered > Nov 7 21:54:23 algol kernel: Trying to mount root from ufs:/dev/ada0s2a > [ro]... > Nov 7 21:54:23 algol kernel: bridge0: Ethernet address: 02:6e:c2:cf:62:00 > Nov 7 21:54:23 algol kernel: wlan0: Ethernet address: 00:0b:6b:b1:3a:e7 > Nov 7 21:54:25 algol root: /etc/rc: WARNING: failed precmd routine for > unbound > Nov 7 21:54:25 algol kernel: /etc/rc: WARNING: failed precmd routine for > unbound > Nov 7 21:54:26 algol ntpd[1183]: ntpd 4.2.4p5-a (1) > Nov 7 21:54:28 algol ftp-proxy[1268]: listening on 127.0.0.1 port 8021 > Nov 7 21:54:28 algol ntpd_initres[1187]: host name not found: > 0.nl.pool.ntp.org > Nov 7 21:54:28 algol ntpd_initres[1187]: host name not found: > 1.nl.pool.ntp.org > Nov 7 21:54:28 algol ntpd_initres[1187]: host name not found: > 2.nl.pool.ntp.org > Nov 7 21:54:28 algol ntpd_initres[1187]: host name not found: > 3.nl.pool.ntp.org > Nov 7 21:54:29 algol dhcpd: gigaset.home.lan: temporary name server failure > Nov 7 21:54:32 algol dhcpd: sven-iphone.home.lan: temporary name server > failure > Nov 7 21:54:46 algol su: sven to root on /dev/pts/0 > Nov 7 21:55:05 algol unbound: [1301:0] notice: init module 0: validator > Nov 7 21:55:05 algol unbound: [1301:0] notice: init module 1: iterator > Nov 7 21:55:37 algol ntpd[1184]: time reset -0.953825 s > Nov 7 21:59:21 algol su: sven to root on /dev/pts/0 > Nov 7 22:02:30 algol su: sven to root on /dev/pts/0 > Nov 7 22:31:50 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 7 22:31:51 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 7 22:44:15 algol kernel: ath0: ath_bar_response: huh? bar_tx=0, > bar_wait=0 > Nov 7 23:05:06 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 7 23:15:07 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 00:18:16 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 01:18:32 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 02:18:43 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 03:18:56 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 03:42:20 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 04:42:31 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 05:05:56 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 05:19:19 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 06:19:32 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 06:42:56 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 07:43:05 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 10:13:12 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 8 10:13:12 algol kernel: ar5416StopDmaReceive: dma failed to stop in > 10ms > Nov 8 10:13:12 algol kernel: AR_CR=0x00000024 > Nov 8 10:13:12 algol kernel: AR_DIAG_SW=0x42000020 > Nov 8 12:28:45 algol kernel: ath0: ath_tx_tid_drain_print: norm: node > 0xc3339000: bf=0xc254cd10: addbaw=0, dobaw=0, seqno=106, retry=0 > Nov 8 12:28:45 algol kernel: ath0: ath_tx_tid_drain_print: node 0xc3339000: > bf=0xc254cd10: txq[1] axq_depth=18, axq_aggr_depth=0 > Nov 8 12:28:45 algol kernel: ath0: ath_tx_tid_drain_print: node 0xc3339000: > bf=0xc254cd10: tid txq_depth=20 hwq_depth=18, bar_wait=0, isfiltered=0 > Nov 8 12:28:45 algol kernel: ath0: ath_tx_tid_drain_print: node 0xc3339000: > tid 0: sched=1, paused=0, incomp=0, baw_head=93, baw_tail=93 txa_start=3976, > ni_txseqs=4222 > Nov 8 12:28:45 algol kernel: FRDS > 02:6e:c2:cf:62:00->c4:85:08:56:df:74(00:0b:6b:b1:3a:e7) data QoS [TID 0] WEP > [IV 6d 40 00 00 00 00 KID 0] 0M > Nov 8 12:28:45 algol kernel: 8842 0000 c485 0856 df74 000b 6bb1 3ae7 026e > c2cf 6200 a006 0000 0000 6d40 0020 0000 0000 aaaa 0300 0000 0800 > Nov 8 15:58:37 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 8 15:58:37 algol kernel: ar5416StopDmaReceive: dma failed to stop in > 10ms > Nov 8 15:58:37 algol kernel: AR_CR=0x00000024 > Nov 8 15:58:37 algol kernel: AR_DIAG_SW=0x42000020 > Nov 8 15:58:37 algol kernel: stray irq7 > Nov 8 16:37:43 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 16:37:44 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 17:07:50 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 18:08:23 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 18:30:49 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 18:43:43 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 18:50:26 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 19:11:01 algol kernel: ath0: ath_bar_response: huh? bar_tx=0, > bar_wait=0 > Nov 8 19:21:09 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 20:27:23 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 20:27:40 algol last message repeated 4 times > Nov 8 21:08:53 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 21:19:01 algol last message repeated 2 times > Nov 8 21:29:01 algol last message repeated 8 times > Nov 8 21:38:59 algol last message repeated 19 times > Nov 8 21:48:56 algol last message repeated 19 times > Nov 8 21:52:19 algol last message repeated 4 times > Nov 8 22:22:19 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 22:35:29 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 22:42:12 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 8 22:48:55 algol last message repeated 2 times > Nov 8 23:49:17 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 00:12:46 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 00:23:20 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 00:36:15 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 00:46:21 algol last message repeated 2 times > Nov 9 00:56:25 algol last message repeated 18 times > Nov 9 00:56:29 algol last message repeated 2 times > Nov 9 00:59:47 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 01:00:12 algol last message repeated 5 times > Nov 9 01:03:07 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 01:13:11 algol last message repeated 10 times > Nov 9 01:23:14 algol last message repeated 26 times > Nov 9 01:33:19 algol last message repeated 13 times > Nov 9 01:43:23 algol last message repeated 17 times > Nov 9 01:53:27 algol last message repeated 15 times > Nov 9 02:03:29 algol last message repeated 13 times > Nov 9 02:10:16 algol last message repeated 11 times > Nov 9 02:21:40 algol last message repeated 18 times > Nov 9 02:30:27 algol last message repeated 13 times > Nov 9 02:40:49 algol last message repeated 13 times > Nov 9 02:50:29 algol last message repeated 11 times > Nov 9 03:00:56 algol last message repeated 12 times > Nov 9 03:07:32 algol last message repeated 10 times > Nov 9 03:58:05 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 04:08:09 algol last message repeated 3 times > Nov 9 04:18:14 algol last message repeated 13 times > Nov 9 04:28:19 algol last message repeated 24 times > Nov 9 04:38:22 algol last message repeated 20 times > Nov 9 04:48:26 algol last message repeated 11 times > Nov 9 04:48:34 algol last message repeated 4 times > Nov 9 05:19:05 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 05:32:31 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 05:39:14 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 05:52:33 algol last message repeated 29 times > Nov 9 06:02:29 algol last message repeated 13 times > Nov 9 06:12:28 algol last message repeated 12 times > Nov 9 06:19:09 algol last message repeated 6 times > Nov 9 06:20:06 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:22:29 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:22:33 algol last message repeated 2 times > Nov 9 06:25:48 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:25:53 algol last message repeated 2 times > Nov 9 06:26:43 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:28:06 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:29:10 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:29:19 algol last message repeated 3 times > Nov 9 06:31:16 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:32:32 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:32:36 algol last message repeated 2 times > Nov 9 06:34:00 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:35:55 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:35:59 algol last message repeated 2 times > Nov 9 06:39:09 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:39:15 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:39:18 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:42:37 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:42:41 algol last message repeated 2 times > Nov 9 06:42:41 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:42:46 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:43:02 algol last message repeated 2 times > Nov 9 06:45:57 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:46:02 algol last message repeated 4 times > Nov 9 06:46:38 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:48:54 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:49:20 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:49:28 algol last message repeated 3 times > Nov 9 06:50:32 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 06:52:39 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 06:52:43 algol last message repeated 2 times > Nov 9 06:56:03 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 07:03:10 algol last message repeated 11 times > Nov 9 07:11:49 algol last message repeated 15 times > Nov 9 07:14:04 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 07:14:34 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 07:14:52 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 07:15:19 algol last message repeated 5 times > Nov 9 07:17:28 algol last message repeated 9 times > Nov 9 07:23:40 algol last message repeated 35 times > Nov 9 07:25:25 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 07:26:58 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 07:26:59 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 07:34:28 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 07:47:28 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 07:50:32 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 07:57:36 algol last message repeated 2 times > Nov 9 07:58:24 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 08:00:11 algol su: sven to root on /dev/pts/0 > Nov 9 08:00:26 algol kernel: ar5416PerCalibrationN: NF calibration didn't > finish; delaying CCA > Nov 9 08:00:26 algol dhcpd: uid lease 192.168.2.33 for client > 18:af:61:21:ae:28 is duplicate on 192.168.2.0/24 > Nov 9 08:00:35 algol last message repeated 3 times > Nov 9 08:01:16 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > Nov 9 08:02:51 algol kernel: ath0: stuck beacon; resetting (bmiss count 4) > > > On 4 November 2013 16:25, Adrian Chadd wrote: >> >> So, May is ok, october isn't? >> >> can you switch back and verify? >> >> Those are data dumps of frames that are being freed out of the >> software staging queue when the wireless node associated has gone away >> (or is being "flushed.") The "bf_next not NULL!" is a worry. > > >