Date: Mon, 28 Jun 2010 09:39:45 -0400 From: John Baldwin <jhb@freebsd.org> To: "KGB" <e01630112a@yahoo.com.cn> Cc: freebsd-drivers <freebsd-drivers@freebsd.org> Subject: Re: Kernel panic of "spin lock held too long" Message-ID: <201006280939.45977.jhb@freebsd.org> In-Reply-To: <tencent_3A4DB631233A41EB25D4D201@qq.com>
index | next in thread | previous in thread | raw e-mail
On Sunday 27 June 2010 1:53:56 am KGB wrote: > Hi John Baldwin: > Thank you for your reply! > Yes,I use an interrupt handler in my driver module and use a filter function. In the filter function,I call the __zt_transmit_chunk function which defined in the zaptel module(name zaptel.ko). Try using a regular interrupt handler without a filter instead. > ------------------ Original ------------------ > From: "John Baldwin"<jhb@freebsd.org>; > Date: Fri, Jun 25, 2010 11:09 PM > To: "KGB"<e01630112a@yahoo.com.cn>; > Cc: "freebsd-drivers"<freebsd-drivers@freebsd.org>; > Subject: Re: Kernel panic of "spin lock held too long" > > > On Friday 25 June 2010 9:56:13 am KGB wrote: > > I met the kernel dump again.The message is below. > > Do you use any interrupt handlers? If so, are you using a filter function? > > Also, you can use the 'tid' command in kgdb to switch to a thread via a tid to > avoid having to search for a 'tid' in info threads. > > -- > John Baldwin -- John Baldwinhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201006280939.45977.jhb>