Re: NTOS: Timer fired even though it was canceled
> Can you explain what you did in detail and it have something to do with > ndis(4)? > Did you ever used ndisgen(8)? Last June I used ndisgen and my computer has been running fine since then. When I saw the NTOS warning I emailed this list. When I got your reply I removed if_bwi_ndis_load from /boot/loader.conf and the warning went away. When I readded to /boot/loader.conf the warning was *still* gone. Because this was the only change I made I assume that it was an intermittent problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
On Sun, Feb 14, 2010 at 8:35 AM, Eitan Adler wrote: > On Sun, Feb 14, 2010 at 2:53 AM, Paul B Mahol wrote: >> 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? >> > > No - I was trying to get if_bwi working but the device never shows up. > I removed it from /boot/loader.conf > Can you explain what you did in detail and it have something to do with ndis(4)? Did you ever used ndisgen(8)? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
On Sun, Feb 14, 2010 at 2:53 AM, Paul B Mahol wrote: > 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? > No - I was trying to get if_bwi working but the device never shows up. I removed it from /boot/loader.conf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
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 AddressSize Name >>> 81 0xc101c000 1ddb8if_bwi.ko >>> 91 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? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
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? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
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 AddressSize Name > 81 0xc101c000 1ddb8if_bwi.ko > 91 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. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
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 AddressSize Name 81 0xc101c000 1ddb8if_bwi.ko 91 0xc103a000 180ae4 if_bwi_ndis.ko 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
> 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NTOS: Timer fired even though it was canceled
On 2/11/10, Eitan Adler wrote:
> Running freeBSD 8.0-RELEASE I got
> NTOS: timer 0xc4817a08 timer fired even though canceled
>
> from
> http://fxr.watson.org/fxr/source/compat/ndis/subr_ntoskrnl.c?v=FREEBSD8
>
>/*
> * This should never happen, but complain
> * if it does.
> */
>
> if (timer->k_header.dh_inserted == FALSE) {
>mtx_unlock(&ntoskrnl_dispatchlock);
> printf("NTOS: timer %p fired even though "
> "it was canceled\n", timer);
> return;
> }
>
>
> What might have caused this and how could I fix it?
What miniport driver, what arch, how to reproduce it?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
