From owner-freebsd-current@FreeBSD.ORG Thu Oct 30 16:12:02 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1983C1065670; Thu, 30 Oct 2008 16:12:02 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id E22018FC27; Thu, 30 Oct 2008 16:12:01 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m9UGC15W052134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Oct 2008 09:12:01 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <4909DCD1.1060806@freebsd.org> Date: Thu, 30 Oct 2008 09:12:01 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: "Paul B. Mahol" 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> In-Reply-To: <3a142e750810300732x774dc3d5lb4ebe6bc1eb85689@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: iwn no-link with latest kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2008 16:12:02 -0000 Paul B. Mahol wrote: > On 10/29/08, Paul B. Mahol wrote: > >> On 10/29/08, Paul B. Mahol wrote: >> >>> On 10/29/08, Sam Leffler 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. Sam