From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id D316A21F5DF; Sat, 16 Aug 2014 16:53:36 -0700 (PDT) Received: by mail-wi0-f169.google.com with SMTP id n3so2273941wiv.0 for ; Sat, 16 Aug 2014 16:53:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=2OFfwg5fWVSpEuW2SohEZTWYuP4urbfeQms1WPAET4A=; b=sShu3gho8sKEjtayRp8z9++fStYltdlHhYlo0p4ztG37FYRzQ5lsFKxLasEIFqudO7 37vz4IeJ6HP9dTMos/EG9dU8gRW3naPNjVmraLkmjaIqlllyNXaQmfxwBsact4egPh9x /nohVpRsWMmJRex8uDXBXL2EnhAddMpB08r244ex1ya4nSG3pb7yCDSoLX4v+NZQcDok 21z/FS09Z7p8B1ybNJ79U5fDb1VuDdknuHPm6abKU7oF5esCDAKmgUJ1wtPaBRjevRyw f9A/yBPFBpD0Nwm/74XcJGhra18V17YaOaSd1l/dfyBh1pI9wtheLRnR7ymMuL2sOX2K zJSA== X-Received: by 10.180.83.8 with SMTP id m8mr64389128wiy.8.1408233214885; Sat, 16 Aug 2014 16:53:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.50.140 with HTTP; Sat, 16 Aug 2014 16:53:14 -0700 (PDT) In-Reply-To: References: From: "R." Date: Sat, 16 Aug 2014 19:53:14 -0400 Message-ID: To: Sebastian Moeller Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: cerowrt@lists.bufferbloat.net, cerowrt-devel Subject: Re: [Cerowrt-devel] [Bug #442] status? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Aug 2014 23:53:37 -0000 Hello Sebastian, I will try to keep an eye and report back. You know what would be really useful? A breakdown of all the useful logs that one would need to provide when reporting on a bug. Even more user-friendly would be a script that generates all relevant information/logs to debugging. Perhaps one day? :) On Sat, Aug 16, 2014 at 6:32 PM, Sebastian Moeller wrote: > Hi R. > > what is the output of: > cat sys/kernel/debug/ieee80211/phy0/ath9k/queues > > and > cat sys/kernel/debug/ieee80211/phy1/ath9k/queues > > when it gets stuck? I wonder whether you see the actual same bug as #442 = or some other bug. (I think the current theory is that a number of bugs con= tributed to the symptoms we described as #442 and now we have to tease them= apart one by one). > > Best Regards > Sebastian > > > > On Aug 16, 2014, at 21:07 , R. wrote: > >> Had to move my client devices from WPA2 to open AP, as I was getting dai= ly failures. I did not experience the stability that you talk of. :( >> >> Manually rebooting at least once a week also happens as dhcp server fail= s. >> >> On Aug 16, 2014 2:55 PM, "Daniel Ezell" wrote: >> No drops here since installing. Looks great to me. >> Daniel >> >> On Aug 16, 2014 11:23 AM, "Dave Taht" wrote: >> I am told that several sites that had severe problems with wifi >> hanging have now been up, >> for over 2 weeks, without problems, with the 3.10.50-1 release of cerowr= t. >> >> How is everyone else doing? >> >> Are we allowed to feel joy and relief at finally having a reasonably >> stable release yet? >> >> -- >> Dave T=C3=A4ht >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >> >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >> >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >