Return-path: Received: from casper.infradead.org ([85.118.1.10]:59814 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754099Ab0LUJZy (ORCPT ); Tue, 21 Dec 2010 04:25:54 -0500 Subject: Re: b43 N PHY status report From: David Woodhouse To: Johannes Berg Cc: =?ISO-8859-1?Q?G=E1bor?= Stefanik , wireless , b43-dev , Larry Finger In-Reply-To: <1292008120.3531.5.camel@jlt3.sipsolutions.net> References: <1291755360-21570-1-git-send-email-zajec5@gmail.com> <4CFFA112.7030800@lwfinger.net> <885729A3-72D4-4EFC-AAFE-D2B573E00ED9@ing.unibs.it> <1292006874.3531.4.camel@jlt3.sipsolutions.net> <4D02793E.2050004@lwfinger.net> <1292008120.3531.5.camel@jlt3.sipsolutions.net> Content-Type: text/plain; charset="UTF-8" Date: Tue, 21 Dec 2010 09:25:26 +0000 Message-ID: <1292923526.2577.53.camel@macbook.infradead.org> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, 2010-12-10 at 20:08 +0100, Johannes Berg wrote: > On Fri, 2010-12-10 at 20:04 +0100, Gábor Stefanik wrote: > > On Fri, Dec 10, 2010 at 8:02 PM, Larry Finger wrote: > > > On 12/10/2010 12:47 PM, Johannes Berg wrote: > > >> On Fri, 2010-12-10 at 19:30 +0100, Francesco Gringoli wrote: > > >> > > >>> [ 1117.516031] unregister_netdevice: waiting for wlan1 to become free. Usage count = 1 > > >>> > > >>> and the device is never release (by who?). I have to reboot. > > >> > > >> That's a bug in the ipv6 code, upgrade your kernel :-) > > > > > > I would not have seen that as IPv6 is disabled in my kernels. > > > > Are you serious? Disabling ipv6 with ipv4 exhaustion expected in January? > > Can we stop this thread right here and go on-topic again please? On-topic: Anyone working on or testing network device drivers should be using IPv6. IPv6 will exercise code paths and network behaviour that Legacy IP rarely does, in particular using multicast to do neighbour discovery. And on wireless networks when multicast will be handled differently by the AP, that makes more difference than on wired where it's mostly the MAC filters that get neglected. I've seen a number of broken drivers because their authors were only testing with Legacy IP and not IPv6. It's not hard to set up IPv6. Larry, if you need any pointers I'd be more than happy to help. -- dwmw2