Date: Tue, 2 Nov 2010 08:44:00 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: Alexander Best <arundel@freebsd.org> Cc: Alexander Motin <mav@freebsd.org>, freebsd-current@freebsd.org, freebsd-usb@freebsd.org Subject: Re: serious issue caused by usb device, stalling almost all operations Message-ID: <201011020844.00600.hselasky@c2i.net> In-Reply-To: <20101101143838.GA64120@freebsd.org> References: <20101020153040.GA3184@freebsd.org> <4CC529CF.8000304@FreeBSD.org> <20101101143838.GA64120@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 01 November 2010 15:38:38 Alexander Best wrote: > On Mon Oct 25 10, Alexander Motin wrote: > > Hans Petter Selasky wrote: > > > On Wednesday 20 October 2010 17:30:40 Alexander Best wrote: > > >> hi there, > > >> > > >> i'm running HEAD (r213495; amd64). i stumbled upon this severe > > >> problem: > > >> > > >> after attaching my mobile phone, it simply resets without doing mount > > >> or anything. however after letting the device come up again it won't > > >> show up in the console. after detaching it the usb subsystem seemed > > >> to have completely crashed. but that's not all. the following > > >> programs now simply hang without producing any output C-C won't do > > >> anything: > > >> > > >> - dmesg > > >> - top > > >> - ps > > >> - killall > > >> - camcontrol devlist > > >> - usbconfig > > > > > > That's most likely because USB's umass driver is waiting for cam to > > > drain. Possibly some refcounting is not correct. I suspect this is not > > > a USB problem. Try to enter into the debugger, and look for backtrace > > > for function stuck in umass_detach. > > i set debug.kdb.panic=1, but didn't work, because writing the core dump > stalled and watchdog came up. > Maybe you could manually run: bt all And look for "cam" and "usb" keywords. And write down the backtraces. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011020844.00600.hselasky>