From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 7 09:01:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C88F16A40F for ; Sat, 7 Oct 2006 09:01:55 +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 A98C143D4C for ; Sat, 7 Oct 2006 09:01:54 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== X-Cloudmark-Score: 0.000000 [] Received: from [193.217.132.251] (HELO [10.0.0.249]) by mailfe01.swip.net (CommuniGate Pro SMTP 5.0.8) with ESMTP id 275199564 for freebsd-hackers@freebsd.org; Sat, 07 Oct 2006 11:01:52 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Sat, 7 Oct 2006 11:02:12 +0200 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610071102.13467.hselasky@c2i.net> Subject: Keyboard system and Giant X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2006 09:01:55 -0000 Hi, Does someone here have the overview over the keyboard system? I see that at least printf calls into the keyboard system without holding Giant, which did cause a panic in the new USB keyboard driver. This happens when the kernel prints text to the screen in text-mode, and printf wants to turn off the scroll lock led. Now I have found a second place where the keyboard system is called without Giant, and this happens when I switch from X11 to text-mode using CTRL+ALT+F1 for example. Then I get a panic, but I cannot see where. Does someone here understand that process? What should I do? Should I just lock Giant in ukbd if it is not locked already? This might cause locking order reversals. The obvious solution to me is to get the keyboard layer out of Giant. Is anyone working on that? --HPS