From owner-freebsd-questions@FreeBSD.ORG Wed May 13 20:25:27 2009 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 C201D106564A for ; Wed, 13 May 2009 20:25:27 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from april.london.02.net (april.london.02.net [87.194.255.143]) by mx1.freebsd.org (Postfix) with ESMTP id 5870E8FC0C for ; Wed, 13 May 2009 20:25:27 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from [192.168.1.75] (93.97.24.219) by april.london.02.net (8.5.016.1) id 49D3A09001A4E22C; Wed, 13 May 2009 21:25:25 +0100 Message-ID: <4A0B2CB4.2020407@onetel.com> Date: Wed, 13 May 2009 21:25:24 +0100 From: Chris Whitehouse User-Agent: Thunderbird 2.0.0.21 (X11/20090321) MIME-Version: 1.0 To: "Paul B. Mahol" References: <49F78DD0.70007@onetel.com> <3a142e750905011711pc9c77f7p67e883e96fac7170@mail.gmail.com> <4A03528F.7070405@onetel.com> <3a142e750905080326q2c21e669xc08aaafbf0fbf36@mail.gmail.com> <4A04968E.5060203@onetel.com> <3a142e750905090742i4bf80d45n323a81d3e18223a@mail.gmail.com> <4A089A87.8040800@onetel.com> <3a142e750905120322h2eb984a6q786ad99287ae2cbb@mail.gmail.com> <4A09D206.7030305@onetel.com> <3a142e750905130536t44129963ie3b191ffea47bbeb@mail.gmail.com> In-Reply-To: <3a142e750905130536t44129963ie3b191ffea47bbeb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: User Questions Subject: Re: ndis0 interrrupt storm 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: Wed, 13 May 2009 20:25:28 -0000 Paul B. Mahol wrote: > On 5/12/09, Chris Whitehouse 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? > This is on i386? > yes