From owner-freebsd-stable@FreeBSD.ORG Fri Apr 3 09:43:29 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14B40106566B; Fri, 3 Apr 2009 09:43:29 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id C5E498FC12; Fri, 3 Apr 2009 09:43:28 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [88.130.213.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 32F798A00D1; Fri, 3 Apr 2009 11:43:27 +0200 (CEST) Message-ID: <49D5DA33.4010800@bsdforen.de> Date: Fri, 03 Apr 2009 11:43:15 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.21 (X11/20090321) MIME-Version: 1.0 To: Alexander Motin References: <1238293386.00093672.1238281804@10.7.7.3> <49CF0803.1070505@FreeBSD.org> <49CF2F8D.6000905@bsdforen.de> <49CF4EB9.60108@FreeBSD.org> <49CF49F5.6010800@bsdforen.de> <49CF615A.6050304@FreeBSD.org> <49CF595A.30805@bsdforen.de> <49CF6B28.2080400@FreeBSD.org> <49CF60AB.4040709@bsdforen.de> <49CF6899.2060002@bsdforen.de> <49CF8E8D.1080604@bsdforen.de> <49CF9C19.3020509@FreeBSD.org> In-Reply-To: <49CF9C19.3020509@FreeBSD.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: powerd broken X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2009 09:43:29 -0000 Alexander Motin wrote: > Dominic Fandrey wrote: >> I can rule out drm0 as the cause, because uhci0 is the only common >> presence in all occurrences of this problem. > > You have other examples? If you mean "irq16: hdac0 uhci+" string, then > "+" there means "and some other devices", which in this case is probably > drm0. > > There were some drm related commits last time and there are also some > IRQ related problems were reported/patched in CURRENT recently. So I > would not ignore this possibility without additional testing. > Is there anything I can do, apart from turning off drm? This is really annoying (well, it eats a whole core while I'm compiling and it keeps the fans going, when the machine should be idle). Is there somehow I can generate useful information? Someone to send a kernel dump to?