NTOS: Timer fired even though it was canceled

[Paul B Mahol]

On Sun, Feb 14, 2010 at 8:35 AM, Eitan Adler <eitanadlerlist at gmail.com> wrote:
> On Sun, Feb 14, 2010 at 2:53 AM, Paul B Mahol <onemda at gmail.com> wrote:
>> On 2/13/10, Eitan Adler <eitanadlerlist at gmail.com> wrote:
>>> On Sun, Feb 14, 2010 at 12:31 AM, Paul B Mahol <onemda at gmail.com> wrote:
>>>> On 2/13/10, Eitan Adler <eitanadlerlist at gmail.com> wrote:
>>>>> On Fri, Feb 12, 2010 at 1:12 PM, Paul B Mahol <onemda at gmail.com> wrote:
>>>>>> On 2/11/10, Eitan Adler <eitanadlerlist at gmail.com> 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)?