From owner-freebsd-stable@FreeBSD.ORG Sun Mar 29 16:04:46 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 7B35C1065715 for ; Sun, 29 Mar 2009 16:04:46 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id F09CC8FC0A for ; Sun, 29 Mar 2009 16:04:45 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 238771292; Sun, 29 Mar 2009 19:04:45 +0300 Message-ID: <49CF9C19.3020509@FreeBSD.org> Date: Sun, 29 Mar 2009 19:04:41 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.19 (X11/20090118) MIME-Version: 1.0 To: Dominic Fandrey 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> In-Reply-To: <49CF8E8D.1080604@bsdforen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Sun, 29 Mar 2009 16:04:47 -0000 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. -- Alexander Motin