From owner-freebsd-questions@FreeBSD.ORG Sun Feb 14 00:53:43 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2420C106566B for ; Sun, 14 Feb 2010 00:53:43 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id AACEF8FC14 for ; Sun, 14 Feb 2010 00:53:42 +0000 (UTC) Received: by ewy3 with SMTP id 3so3934161ewy.13 for ; Sat, 13 Feb 2010 16:53:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=bbPT1sBp7N1xCbSU+QP0Zpe/2zGXyDVoJELg5pVvY0o=; b=YfCxzDslcgf8UjT/A1NRfbY+OC+PZjir78mHgsN+mUD8ptBlZTA/i8ql2qTog6HhPC 6ILKpwBjm52rUm20NA4z9G+J+UCi2GNnyy2L0PFdTD4rOFbVgCOzmqGKcqUFd+Re9RPg rMzf3SfQ2v/aegyDWpcg0GV0eS8I5nuQfpjws= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Q6NkLi1CfFz3Jq7eQNJyyXAa3i+kY+RkU2V7Pig+kYmdBHF1Etra4YIV9PxftHpWhp WTyiRhnMmzgukqtxhAM9aZVb2RX6R7TxmFf7H9ogandhav3h4URdjUAetsrRHJu5EZBj P6uA3/GfnWrMTpEaq3rMICKfF7Kq4Qr6bXBWI= MIME-Version: 1.0 Received: by 10.213.96.68 with SMTP id g4mr1387411ebn.77.1266108821491; Sat, 13 Feb 2010 16:53:41 -0800 (PST) In-Reply-To: References: <3a142e751002111052p3ef55575q8baca1af8ab27a17@mail.gmail.com> <3a142e751002120312s3cb778a0l1d856b7376a280fa@mail.gmail.com> <3a142e751002131431i488c1fb1rc67545411091c5c5@mail.gmail.com> Date: Sun, 14 Feb 2010 00:53:41 +0000 Message-ID: <3a142e751002131653t182ac795t2412c8d32949f99b@mail.gmail.com> From: Paul B Mahol To: Eitan Adler Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@freebsd.org Subject: Re: NTOS: Timer fired even though it was canceled X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Feb 2010 00:53:43 -0000 On 2/13/10, Eitan Adler wrote: > On Sun, Feb 14, 2010 at 12:31 AM, Paul B Mahol wrote: >> On 2/13/10, Eitan Adler wrote: >>> On Fri, Feb 12, 2010 at 1:12 PM, Paul B Mahol wrote: >>>> On 2/11/10, Eitan Adler wrote: >>>>>> What miniport driver, what arch, how to reproduce it? >>>>> a) no idea >>>>> b) Sorry for leaving that out: 8.0-RELEASE-p2 i386 >>>>> c) Boot the computer and watch tty0 >>>> >>>> Does it happens also if you load module (bcmwl5_sys.ko) after boot via >>>> kldload instead via /boot/loader.conf >>>> >>> Is this what you mean? >>> >>> Id Refs Address Size Name >>> 8 1 0xc101c000 1ddb8 if_bwi.ko >>> 9 1 0xc103a000 180ae4 if_bwi_ndis.ko >> >> if_bwi is unrelated to NDIS. >> >> I'm asking about module you created with ndisgen. >> >>> >>> If you meant loading these via kldload instead of at boot time then >>> No, >>> But when I put it back in I also no longer see the warning. >>> >> > > I didn't recognize what you meant with "bcmwl5_sys.ko". > Either way the answer applies: I no longer see the warning regardless > of whether it is in /boot/loader.conf or not. Perhaps it was an > intermittent problem? If so what could it mean? Are you using bwi(4) and ndis(4) at same time for same device?