Date: Sun, 16 Nov 2014 16:34:38 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Hans Petter Selasky <hps@selasky.org> Cc: Dag-Erling Sm?rgrav <des@freebsd.org>, freebsd-current <freebsd-current@freebsd.org>, Ian Lepore <ian@freebsd.org>, Steve Kargl <sgk@troutmask.apl.washington.edu> Subject: Re: USB locks up system -- WAS Re: shutdown or acpi problem Message-ID: <CAJ-Vmo=vc43wqpFr%2BzFB8ivHWQqeRQ8Fj0TPU9ZvP_HZDO_g%2Bg@mail.gmail.com> In-Reply-To: <5468FBFB.1090208@selasky.org> References: <20141116175102.GA35649@troutmask.apl.washington.edu> <D5925789-834A-42C8-9854-2E055592DA46@FreeBSD.org> <1416162070.4781.186.camel@revolution.hippie.lan> <F0B9570C-BADD-4843-AE91-66CAB0B5DE85@FreeBSD.org> <1416162718.4781.192.camel@revolution.hippie.lan> <4F3B4E02-0ADD-46EB-BB90-BF360E810585@FreeBSD.org> <20141116185141.GB36021@troutmask.apl.washington.edu> <4443FEFB-17F1-4516-959F-4C70AB2A4382@FreeBSD.org> <20141116190344.GC36021@troutmask.apl.washington.edu> <5468F814.6010702@selasky.org> <20141116192959.GB36339@troutmask.apl.washington.edu> <5468FBFB.1090208@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
... or since you can ssh into the thing, try as root: procstat -ka -adrian On 16 November 2014 11:33, Hans Petter Selasky <hps@selasky.org> wrote: > On 11/16/14 20:29, Steve Kargl wrote: >> >> On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote: >>> >>> On 11/16/14 20:03, Steve Kargl wrote: >>>> >>>> On Sun, Nov 16, 2014 at 06:55:53PM +0000, Mark R V Murray wrote: >>>>> >>>>> >>>>>> On 16 Nov 2014, at 18:51, Steve Kargl >>>>>> <sgk@troutmask.apl.washington.edu> wrote: >>>>>> >>>>>> If you have not read the entire thread, once the laptop keyboard and >>>>>> video output lock up, I can ssh into the laptop. If I run usbconfig, >>>>>> it hangs, ^T tells me it is stuck in SX Lock, and the /dev/da0* >>>>>> devices >>>>>> have not been destroyed. >>>>> >>>>> >>>>> Weirder and weirder :-(. >>>>> >>>>> Something with SX locks? Hmm. I do use those for attach and detach for >>>>> RNG sources. Could it be that that stick of yours is somehow getting >>>>> involved in the RNG source locks? >>>>> >>>> >>>> It's not limited to a single usb device. Plugging in/Unplugging >>>> a logitech mouse dongle, the memstick, a Western Digital MY Passport >>>> external usb hard drive, all lead to the locked keyboard and video. >>>> >>>> I tried adding both RANDOM_DEBUG and USBDEBUG to the kernel, but the >>>> mount of output is mind numbing. >>>> >>> >>> >>> Can you enter kgdb when the usbconfig is froozen, and backtrace all >>> kernel threads. You should see exactly what locks are the problem. >>> >>> Maybe some lock didn't get properly unlocked! >>> >> >> I haven't tried kgdb. I did try to attach gdb to the usbconfig >> process via its pid, but gdb dumped core. >> >> I haven't looked at locks in kgdb, what command or commands should >> I try. >> >> > > Hi, > > You enter: > > thread apply all bt > > That will give you the backtrace of all threads. Grep for usbconfig, and > figure out which line is causing the problem in the kernel. Then look at the > USB explore threads and see where they are stuck in the detach of umass! > > --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=vc43wqpFr%2BzFB8ivHWQqeRQ8Fj0TPU9ZvP_HZDO_g%2Bg>