Date: Fri, 31 Oct 2008 01:19:47 +0100 From: "Paul B. Mahol" <onemda@gmail.com> To: "Sam Leffler" <sam@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: iwn no-link with latest kernel Message-ID: <3a142e750810301719h369fb89cmb9003e0e9e923532@mail.gmail.com> In-Reply-To: <4909DCD1.1060806@freebsd.org> References: <33615c8e0810290427g2dc73cd9p9bae3eaa15153d5e@mail.gmail.com> <3a142e750810290514k525d155ep5721b0480a82d63e@mail.gmail.com> <49087912.90404@freebsd.org> <3a142e750810290930l11da5981v7d0f09a4a42e940f@mail.gmail.com> <3a142e750810291403u65724d5eo7fccec254d07c984@mail.gmail.com> <3a142e750810300732x774dc3d5lb4ebe6bc1eb85689@mail.gmail.com> <4909DCD1.1060806@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/30/08, Sam Leffler <sam@freebsd.org> wrote: > Paul B. Mahol wrote: >> On 10/29/08, Paul B. Mahol <onemda@gmail.com> wrote: >> >>> On 10/29/08, Paul B. Mahol <onemda@gmail.com> wrote: >>> >>>> On 10/29/08, Sam Leffler <sam@freebsd.org> wrote: >>>> >>>>> Maybe you can file a PR or at least provide some details? >>>>> >>>> First I need to test my rum(4) cards, maybe it is only ndis problem. >>>> >>> rum driver still works. >>> >> >> reverting 184271 (and only 184271), fixed ndis problem. >> >> > > Then ndis is busted. This means it didn't setup an association id. I noticed several times that ndis always do something like this without real reason: associate->disassociate and than associate again. (in very short interval) dunno if this have anything to do with association id. It will take me some time to explore this ndis bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750810301719h369fb89cmb9003e0e9e923532>