From owner-freebsd-usb@FreeBSD.ORG Sat Aug 22 16:25:45 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C3A31065690 for ; Sat, 22 Aug 2009 16:25:45 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id E7A978FC0C for ; Sat, 22 Aug 2009 16:25:44 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=8kQB0OdkAAAA:8 a=gUeatJ46Z6QozRAR84kA:9 a=c4owS5YU31lNqNiyZvySrKElfh8A:4 a=9aOQ2cSd83gA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 243380233; Sat, 22 Aug 2009 18:25:43 +0200 From: Hans Petter Selasky To: Bruce Cran Date: Sat, 22 Aug 2009 18:25:55 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-BETA2; KDE/4.2.4; i386; ; ) References: <200908032127.32353.hselasky@c2i.net> <20090822154807.0cf17700@gluon.draftnet> In-Reply-To: <20090822154807.0cf17700@gluon.draftnet> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908221825.56855.hselasky@c2i.net> Cc: Alexander Best , freebsd-usb@freebsd.org Subject: Re: kernel debugger and usb keyboard X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Aug 2009 16:25:45 -0000 On Saturday 22 August 2009 16:48:07 Bruce Cran wrote: > On Mon, 3 Aug 2009 21:27:30 +0200 > > Hans Petter Selasky wrote: > > On Monday 03 August 2009 20:55:16 Alexander Best wrote: > > > just tried settings `sysctl debug.kdb.panic = 1`. if i use this way > > > to enter the kernel debugger my usb keyboard works. if i type > > > "continue" however the kernel panics and the kernel debugger gets > > > yet entered again, but without the keyboard working. > > > > The USB controller which the keyboard is hooked onto will not work > > after panic has been entered, due to some state not being cleaned up. > > > > To increase the chance of the keyboard working on a panic, connect > > the keyboard to a separate USB controller. > > > > > i don't know how to produce backtraces since the keyboard doesn't > > > work. > > > > Ok. > > > > > the other way of entering the debugger without my keyboard working > > > was to simple press "ctrl+ast+esc". > > > > Yes, because most likely the DDB is entered directly from the USB > > keyboard code, and the USB stack does not allow function recursion in > > that case! > > USB keyboard support is now working in the debugger, but it seems > the USB stack hangs up if you exit out of the debugger, if the system > hasn't crashed and can keep running - the keyboard doesn't respond, and > unplugging and re-plugging it doesn't help. > > If I press Ctrl-Alt-Esc followed by "c" to continue, the output scrolls > up the window as if the Enter key is being held down. This is going to get fixed in a coming USB patchset. Stay tuned. --HPS