ndis0 interrrupt storm

Chris Whitehouse cwhiteh at onetel.com
Wed May 20 21:46:29 UTC 2009


Chris Whitehouse wrote:
> Paul B. Mahol wrote:
>> On 5/13/09, Chris Whitehouse <cwhiteh at onetel.com> wrote:
>>> Paul B. Mahol wrote:
>>>> On 5/12/09, Chris Whitehouse <cwhiteh at onetel.com> wrote:
>>>>> Paul B. Mahol wrote:
>>>>>> Just typing bt on db prompt for now should be enough.
>>>>> panic: sleeping thread
>>>>> cpuid = 0
>>>>> KDB: enter: panic
>>>>> [thread pid 1497 tid 100073 ]
>>>>> Stopped at    kdb_enter+0x3a: movl    $0,kdb_why
>>>>> db> bt
>>>>> Tracing pid 1497 tid 100073 td 0xc356c900
>>>>> kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d4001b68,0,...) at kdb_enter+0x3a
>>>>> panic(c0c42726,ffffffff,0,cc,4,...) at panic+0x136
>>>>> propagate_priority(c0d9df84,0,c0c4249e,2e1,c356d180,...) at
>>>>> propagate_priority+0x18c
>>>>> turnstile_wait(c356d180,c37b2240,0,18d,c34fc06c,...) at
>>>>> turnstile_wait+0x44d
>>>>> _mtx_lock_sleep(c34fc06c,c356c900,0,c38de072,6b4,...) at
>>>>> mtx_lock_sleep+0x18e
>>>>> _mtx_lock_flags(c34fc06c,0,c38de072,6b4,c089dc98,...) at
>>>>> mtx_lock_flags+0xf7
>>>>> ndis_ticktask(c3821700,c34fc000,c37e8e3c,c3916bd0,c38fc6e0,...) at
>>>>> ndis_ticktask+0x3a
>>>>> _end(c37e8e3c,d4001d38,c0c39438,333,c37ab548,...) at _end+0x321d
>>>>> fork_exit(c38fc600,c37e8e3c,d4001d38) at fork_exit+0xb8
>>>>> fork_trampoline() at fork_trampoline+0x8
>>>>> --- trap 0, eip = 0 esp = 0xd4001d70, ebp = 0 ---
>>>>>
>>>>>
>>>>> Typed by hand but I'm pretty sure it is correct.
>>>>>
>>>>> Don't know if it is significant but repeating the panic gave quite 
>>>>> a few
>>>>> different values.
>>>> Post them too. If only numbers are different and stack is same that
>>>> could help even more.
>>> Is photos ok or do you need text?
>>
>> Whatever, just let it be complete.
> 
> http://www.fishercroft.plus.com/ndis.panic.bt.1
> http://www.fishercroft.plus.com/ndis.panic.bt.2
> http://www.fishercroft.plus.com/ndis.panic.bt.3
> http://www.fishercroft.plus.com/ndis.panic.bt.4
> 
> 
> 
>>
>>>> This is on i386?
>>>>
>>> yes

has this died a death? Anything else I can do? Should I file a PR?

I don't mind waiting if something is happening, just don't want to get 
stuck in /dev/void.

Chris


More information about the freebsd-questions mailing list