From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 12 09:08:42 2003 Return-Path: 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 6C50316A4CE for ; Wed, 12 Nov 2003 09:08:42 -0800 (PST) Received: from mail.speakeasy.net (mail8.speakeasy.net [216.254.0.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4353B43FE0 for ; Wed, 12 Nov 2003 09:08:41 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 2172 invoked from network); 12 Nov 2003 17:08:40 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 12 Nov 2003 17:08:40 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id hACH8Ece026145; Wed, 12 Nov 2003 12:08:14 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20031112104458.GA94744@nm.ruhr-uni-bochum.de> Date: Wed, 12 Nov 2003 12:08:12 -0500 (EST) From: John Baldwin To: Andre Grosse Bley X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-hackers@FreeBSD.org Subject: Re: 4.9-RELEASE, ACPI and DELL Latitude D600 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2003 17:08:42 -0000 On 12-Nov-2003 Andre Grosse Bley wrote: >> > Ah, the problem is that ACPI tries to sleep from a task, which is not safe >> > to do. This is not easy to fix. :( >> >> Actually, it may not be too hard. In current, ACPI uses its own thread >> to run the tasks in, so stable would need the same sort of thing. >> Basically, ACPI needs to start up a kproc and needs to have its own >> taskqueue again that uses this kproc for its execution context. > > So - as I am not a experienced kernel hacker - there is no easy solution > for me to 'fix' this panic? Should I open a PR? A PR might be a good idea. The basic details are that ACPI in 4.x needs to create a kernel process to service it's private taskqueue and then use this taskqueue instead of the system taskqueue to service events. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/