Date: Thu, 3 Nov 2011 21:04:23 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-current@freebsd.org Cc: Jan Henrik Sylvester <me@janh.de> Subject: Re: USB3 express card panics on 9.0-RC1 Message-ID: <201111032104.23332.hselasky@c2i.net> In-Reply-To: <201111031942.30498.hselasky@c2i.net> References: <4EB1602C.6030807@janh.de> <4EB2895B.3080104@janh.de> <201111031942.30498.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 03 November 2011 19:42:30 Hans Petter Selasky wrote: > On Thursday 03 November 2011 13:30:19 Jan Henrik Sylvester wrote: > > After reading http://www.unixguide.net/freebsd/faq/18.13.shtml , I found > > that ffffffff806e8040 t usb_process is the last symbol before > > instruction pointer = 0x20:0xffffffff806e80aa. Does this help? > > Try add: > > options KDB # Enable kernel debugger support. > options DDB # Support DDB. > Hi, Looks like it panics at: mtx_lock(up->up_mtx); In "usb_process()" which is created by the "xhci0" instance. I would really like to see a dump of "up" and "up_mtx" because I cannot see how this can happen. Have you seen any USB errors in the dmesg up to the point of this panic? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201111032104.23332.hselasky>